This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP3530 Boot Problum

Other Parts Discussed in Thread: OMAP3530, TPS65950

Hi,

On our custom omap3530 based board we are facing nand boot problem at power on. We have x-loader and u-boot flashed into NAND. The board doesn't boot from nand at power on. When we downloaded x-loader through JTAG, then u-boot is booting from nand. We also find that DDR SDRAM clock is some times 90MHz and sometimes 220 MHz.  We have several boards with this hardware configuration. All boards are booting and working fine with Linux except this board.

Reading CONTROL_STATUS (0x4800 22F0) through JTAG we find that sys_boot[5:0] pins are sampled as 0x0E at power on even though we configured it for 0x0F for NAND boot. On working boards these pins are read correctly as 0x0F while non working board sees it as 0X0E. Could this be the problem for NAND boot failure at power on? Can you please suggest what else could be the problem and how to debug it?

we are using the following hardware in our board.

Processor -     OMAP3530DCBBA

DDR -              MT46H128M16LF

NAND -           MT29F2G08AADWP

Power management IC - TPS65950

Thank you

Eswar

  • I think this is definitely a problem.  The sysboot signals are sampled at the rising edge of PWRONRST.  I would probe the sysboot signals right around this point.    There may be something conflicting with the value of these signals (maybe you are intending to use these signals in a different mux mode in your application).

    Regards,

    James

  • Hi James,

      Thanks for Reply. That was useful. We traced a dry solder on sysboot pins for OMAP3530 processor.

    Thanks You

    Eswar