I have been following this forum for some time and have been using the SATA boot version of 2013.10 U-Boot for OXNAS on my AKiTio MyCloud Mini.
However, the AKiTio MyCloud Mini cannot boot with a kernel newer than Linux-4.4.189-oxnas-tld-1.
Additionally, after searching past forum posts, I found out that the NAND boot version of 2015.10 U-Boot also does not boot properly on the AKiTio MyCloud Mini.
To investigate whether the issue with the kernel not booting properly is due to the SATA version of U-Boot, I needed to make the NAND version of U-Boot bootable.
Recently, I set up a cross-compiler environment using gcc 6.5.0 and performed U-Boot debugging, which revealed the cause of the NAND version of 2015.10 U-Boot not booting on the AKiTio MyCloud Mini.
According to the data sheet for the NAND HY27UF082G2B, 5 cycles are required for address specification, but since the U-Boot option ‘CONFIG_SYS_NAND_5_ADDR_CYCLE’ was not specified, the correct NAND memory address could not be accessed.
After flashing the U-Boot with ‘CONFIG_SYS_NAND_5_ADDR_CYCLE’ enabled, the NAND version of the 2015.10 U-Boot now boots successfully.
Not yet tested whether kernels newer than 4.4.189 boot normally, but since the NAND boot issue has been resolved, we are posting this update.
However, the AKiTio MyCloud Mini cannot boot with a kernel newer than Linux-4.4.189-oxnas-tld-1.
Additionally, after searching past forum posts, I found out that the NAND boot version of 2015.10 U-Boot also does not boot properly on the AKiTio MyCloud Mini.
To investigate whether the issue with the kernel not booting properly is due to the SATA version of U-Boot, I needed to make the NAND version of U-Boot bootable.
Recently, I set up a cross-compiler environment using gcc 6.5.0 and performed U-Boot debugging, which revealed the cause of the NAND version of 2015.10 U-Boot not booting on the AKiTio MyCloud Mini.
According to the data sheet for the NAND HY27UF082G2B, 5 cycles are required for address specification, but since the U-Boot option ‘CONFIG_SYS_NAND_5_ADDR_CYCLE’ was not specified, the correct NAND memory address could not be accessed.
After flashing the U-Boot with ‘CONFIG_SYS_NAND_5_ADDR_CYCLE’ enabled, the NAND version of the 2015.10 U-Boot now boots successfully.
Not yet tested whether kernels newer than 4.4.189 boot normally, but since the NAND boot issue has been resolved, we are posting this update.
