• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 482 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.

DM3730 Booting Problem

Staphae
Prodigy 125 points
Other Parts Discussed in Thread: DM3730, OMAP3530

DM3730 ROM Loader cannot successfully load X-Loader

I am trying to bring up our custom board with the DM3730 processor. I can connect to the board using Flashv1.6 and load  MLO, U-BOOT, uImage to NAND. I can also use Flash Loader to load and execute u-boot and uImage from RAM.

However what i cannot seem to do is get the ROM Loader to loader X-Loader (MLO) from either SD Card or NAND successfully. I know for a certain that the SD Card is correctly formated and has valid code since i can successful boot the SD Card on the OMAP3530 EVM Board even though this card has kernel for DM3730 found in prebuild images directory from the ti-dvsdk-dm37xxx. But each time i try booting the board with this SD Card I get the following message on the debug port. This message is for when i configure the board to boot from MMC (SD Card)

     Texas Instrument X-Loader 1.46 (Mar 24 2011 - 20:21:25)

      Starting X-loader on MMC

      MMC init failed

      X-Loader hangs

 

The card reader is  connected to MMC2 on the processor and there is activity on the MMC2 interface at reset, very similar to what is observed for the OMAP3530 EVM Board. The insertion of the card is also detected at reset. Please help, i have spent the last few days without any success.

 

 

  • 0
    TI__Guru* 86180 points

    Staphae,

    please check the following wiki for usage notes on booting from MMC2:  http://processors.wiki.ti.com/index.php/SD-MMC_Usage_Notes_on_OMAP35x_and_AM37x

    There are a few restrictions when trying to boot using MMC2. 

    It seems that you are successfully loading xloader, since you get those messages.  Note that the OMAP3EVM is booting from MMC1, whereas you are booting from MMC2.  So you have to change xloader to accomodate for this.

    Regards,

    James

  • 0 in reply to JJD
    Prodigy 125 points

    James,

    Thanks very much for your response. It's making a lot more sense to me now. But what do i need to change in X-Loader for this to happen? Any pointer will be appreciated. 

    One other observation i have is the ROM Loader is not reading X-Loader in Nand and i know for certain that the boot option is set to first look in the Nand before searching on UART3. I can successfully read back both X-Loader and U-Boot in Nand using U-Boot placed in ram using Flash1.6. Do you know why ROM boot code is not reading x-loader and eventually  U-Boot from Nand? I used hwecc 1-bit to write X-Loader and swecc to write u-boot. However,  when i repeat the same procedure on the OMAP3530 EVM it works. The nand size on OMAP is 256MB whereas it's 512MB on the DM37 but they are both from Micron.