• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 99 subscribers
  • Views 210 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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 kernel boot failed

XIAN ZHAO
Prodigy 110 points
Other Parts Discussed in Thread: TPS65930, OMAP3530

Hi!

I  am using OMAP3530 and tps65930.For some reasons, we don't use the I2C1 to control tps65930,instead I2C3 are used.

We successfully boot x-loader and u-boot from SD card by enabling VMMC1 LDO through I2C3 .

But after the kernel has been uncompressed, it halt runing.

What may be the problem?

I guess if the kernel is communicating with tps65930 at boot time using I2C1,   which we did not use at all. The Kernel can't receive any ACK from the I2C1, thus causing it to try in a dead loop .

Or is there any other reasons?

THANKS!

  • 0
    TI__Expert 4590 points

    I am assuming that by halt you mean - there is no activity on the console beyond this print:

    "Uncompressing Linux... done, booting the kernel."

    If so, there may be many reasons to it. Debugging with JTAG would be the fastest way to eliminate the causes.

    Some questions and suggestions that me help you:

    - Are you reading the x-loader, u-boot and kernel from same SD card?

    - Are all changes for custom board taken care while creating the board configuration?

    - You can start with minimal board file and work upwards adding more drivers  (via Kconfig) and content (in board specific file).

    - If you have disabled Low Level debug in the kernel configuration, you can enable the same for more verbose messages during debug.

    Best regards,
    Sanjeev