OMAP3530DCUS not working NAND Booting

SUN MYUNG PARK

Prodigy 30 points

my system has OMAP3530DCUS + micron NAND (29F4G16ABCWC).

first, MMC booting, then program to NAND (xloader & u-boot).

second, change sys_boot = 0b110101, but NAND Booting is not working.

third, change sys_boot=0b001111, xloader working through MMC, u-boot working through NAND.

why not working case "sys_boot = 0b110101".

over 15 years ago

0 Bernie Thompson TI over 15 years ago

TI__Mastermind 41665 points

SUN MYUNG PARK said:
why not working case "sys_boot = 0b110101".

Most likely this would be a failure for the RBL to detect a proper image in the NAND, so the issue could stem from a NAND writing issue to corruption of the X-Loader image itself that is being written to NAND. Note that sys_boot of 0b001111 will try a NAND boot first as well, so NAND boot is being bypassed and you are ending up in the MMC boot mode as a result of a failed NAND boot.

0 Soren Steen Christensen over 15 years ago in reply to Bernie Thompson TI

Genius 3685 points

Have you remembered to sign the x-loader prior to flashing it? And remember that you need to flash it using the HW ECC scheme in U-boot. More info to be found at: http://code.google.com/p/beagleboard/wiki/BeagleSoftCompile and http://elinux.org/BeagleBoardNAND

Good luck
Søren

0 SUN MYUNG PARK over 15 years ago in reply to Bernie Thompson TI

Prodigy 30 points

[1] our prototype system use OMAP3530DCBC + MT29C4G48MAPLCJQ-6 (POP Package , MT46H32M32LFJG-6+MT29F4G16ABCWC).

upper systems are good job with NAND -booting.

[2] but following new system using OMAP3530DCUS + MT29F4G16ABCWC (TSOP Package) is not working same condition.

of coures i used "nand ecc hw" for xloader. (u-boot-1.1.4)

i'dont know why?

Processors

Processors forum

OMAP3530DCUS not working NAND Booting