• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 357 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 X-Loader Fails on DM3730

MattB
Expert 2025 points
Other Parts Discussed in Thread: OMAP3530, DM3730

Hi,

We've had one of our custom boards populated with a DM3730 instead of an OMAP3530. We were hoping/expecting that our existing software would work without modification.

I have an SD card that successfully boots an OMAP3530 but does not boot the DM3730.

I can see the output of the ROM bootloader and it appears OK to me. In other words the UART appears to be working at 115200.

Then I get a stream of unprintable characters. I believe this is the x-loader information coming out of the UART but not at 115200.

Then x-loader appears to hang. In other words it fails to find the u-boot image.

This is a custom version of x-loader for our custom board but it wasn't me who created it hence I'm not sure what is different between it and the TI x-loader. The repo log has this to say about the x-loader:

Sourced from Arago GIT repo - tagged v1.51 http://arago-project.org/git/projects/?p=x-load-omap3.git

I would greatly appreciate any thoughts or pointers towards the things I should check on our board.

Thanks,

Matt

  • 0
    Expert 2025 points

    After rummaging around for a while I realised that the DM3730 is configured by testing the CPU family against the CPU_OMAP36XX macro.

    I think I've now got a handle on the DM3730 configuration that is missing.

    Matt