Hello
We are developing a Linux-based software for a custom board based on OMAP3503. I flashed the MLO, u-boot and the kernel to NAND (on a custom board) using the following script
"initnand=echo Copying from mmc to nand ...; " \
"mmc init; " \
"mw.b 0x81600000 0xff 0x20000;nand erase 0 20000;fatload mmc 0 0x81600000 MLO;nandecc hw; nand write.i 0x81600000 0 20000;" \
"mw.b 0x81600000 0xff 0x40000;nand erase 80000 40000;fatload mmc 0 0x81600000 u-boot.bin;nandecc sw; nand write.i 0x81600000 80000 40000;" \
"mw.b 0x81600000 0xff 0x1400000;nand erase 280000 300000;fatload mmc 0 0x81600000 uImage;nandecc sw; nand write.i 0x81600000 280000 300000\0" \
I shortcut the pins on OMAP so that sys_boot[5]=0 and sys_boot [4:0]=01111 so the boot order should be
NAND USB UART3 MMC1 (according to p. 3361 OMAP35 TRM)
If it is so the MLO fails to boot at ALL!!!
If I remove the wire to set sys_boot[5]=1 and, similarily, sys_boot [4:0]=01111 everything boots OK
The same thing happens with OMAP35 EVM too:
if I flash MLO and u-boot from 0.9.7 SDK to NAND and set SW4 to (from 1 to 8): OFF ON OFF ON OFF ON OFF OFF()
(according to http://processors.wiki.ti.com/index.php/GSG:_OMAP35x_DVEVM_Hardware_Setup the boot order is Flash/UART) - nothing boots!!!!
If I switch the SW6 to OFF to change the order to UART/Flash the MLO and u-boot starts off well.
It seems to me that if NAND is the first device in boot sequence, it can not boot!!!
Please help with this one
Best regards,
Andrey Ulanov,
Navis Company