• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 747 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.

OMAP-L138: MMC/SD boot issue

Risto Hedman
Expert 1770 points
Part Number: OMAP-L138

Hi,

We've desperately been trying to boot our custom board from SD. MMC/SD- interface is operational and works fine as RFS storage when we boot from SPI-FLASH. *ais generated with AisGen with our custom u-boot  works fine from SPI-FLASH.

"OMAP-L138 Preparing SD Card for Boot" and "How to boot OMAP-L138 LCDK from SD card" have been studied in this trial. We also have TI's OMAPL-138 LCDK in use. uflash has bee compiled to Linux host and totarget system, has been used in both and results are similar: *.ais will be burned to sector 117 and starts with "TIPA" and uflash console output looks like in documentation. LCDK's SD can not be used fully as our u-boot is using a different UART. Also 'dd' has been used to burn 'ais' - no remarkable differences to 'uflash'.

SD- bus in target system has been investigated with scope when LCDK's SD is in use 'pre-buit-images' SD is n use and our custom 'ais' is in use. In SDs originating from TI, there is more astivity on SD-bus, first low freq burst about 1.8s and then high freq burst; high freq is missing when 'custom-ais-sd' is in use. Most likely 'ais' is found by the low level boot and maybe it interprets 'ais' but does not find u-boot??!!  We wonder how can the situation differ from SPI-BOOT?? We assume that the status of the SD, which partitions are excisting and how they are formatted, does not matter. In 'ais' files prepared to SD/MMC and to SPI-FLASH there is only one difference.

Could some specialist please tell us what is wrong with our logic?

BR, ristoH

  • 0
    TI__Guru**** 161600 points

    Hi,

    Which Processor SDK Linux are you using?

    Best Regards,
    Yordan

  • 0
    Expert 1770 points

    Hi Yordan,

    Thank you for your rapid reply, SDK is quite antique one:

    mcsdk_1_01_00_02

    linux-3.3-psp03.22.00.06.sdk

    u-boot-2012.04.01-psp03.22.00.06.sdk

    Best Regards, 

    ristoH

  • 0 in reply to Risto Hedman
    TI__Guru**** 161600 points

    Hi,

    How did you configure your AISGEN tool when creating the u-boot.ais file?

    Best Regards,
    Yordan

  • 0 in reply to Yordan Kovachev
    Expert 1770 points

    Hi Yordan,

    Please find below the content of the *cfg file.

    risto

    Boot Mode=MMC/SD0
    Boot Speed=5
    Flash Width=1
    Flash Timing=3ffffffd
    Configure Peripheral=True
    Configure PLL0=True
    Configure SDRAM=False
    Configure PLL1=True
    Configure DDR2=True
    Configure LPSC=False
    Configure Pinmux=True
    Enable CRC=False
    Specify Entrypoint=True
    Enable Sequential Read=False
    Use 4.5 Clock Divider=False
    Use DDR2 Direct Clock=False
    Use mDDR=False
    ROM ID=3
    Device Type=0
    Input Clock Speed=24
    Clock Type=0
    PLL0 Pre Divider=1
    PLL0 Multiplier=19
    PLL0 Post Divider=1
    PLL0 Div1=1
    PLL0 Div3=3
    PLL0 Div7=10
    PLL1 Multiplier=25
    PLL1 Post Divider=4
    PLL1 Div1=1
    PLL1 Div2=2
    PLL1 Div3=3
    Entrypoint=c1080000
    SDRAM SDBCR=0
    SDRAM SDTMR=0
    SDRAM SDRSRPDEXIT=0
    SDRAM SDRCR=0
    DDR2 PHY=c5
    DDR2 SDCR=374832
    DDR2 SDCR2=0
    DDR2 SDTIMR=264a3209
    DDR2 SDTIMR2=3c14c722
    DDR2 SDRCR=492
    LPSC0 Enable=0+1+2+3+4+6+7+13+14+15+
    LPSC0 Disable=
    LPSC0 SyncRst=
    LPSC1 Enable=0+1+3+5+6+8+10+11+12+31+
    LPSC1 Disable=
    LPSC1 SyncRst=
    Pinmux=0:88888888+1:88888888+2:0+3:111111+4:22442288+5:88111111+6:88888888+7:88888888+8:88888888+8:88888888+10:88888888+11:88888888+12:88888888+13:88888888+14:88888888+15:80+16:88888880+17:88888888+18:88888888+19:88888888+
    App File String=C:\ti\u-boot040519.bin@0xc1080000
    AIS File Name=C:\ti\u-boot040519-mmc.ais

  • 0 in reply to Risto Hedman
    TI__Guru**** 161600 points

    HI,

    This seems correct. Let me inspect further.

    Best Regards,
    Yordan

  • 0 in reply to Yordan Kovachev
    Expert 1770 points

    Hi Yordan,

    Thank you. Please do not put too much effort on this - we can continue with SPI-FLASH boot if solution to SD- boot is complex.

    Best Regards,

    ristoH 

  • 0 in reply to Risto Hedman
    TI__Guru 50170 points

    Hi, Risto,

    The MCSDK 1.1 is out of our support scope. I strongly suggest you to upgrade to the latest Processor SDK (6.0) for better support. Staying with MCSDK, we can only provide some guidance. In the Proc SDK User's Guide, to burn the .ais image to SD card, the command is 

    $ cd <SDK INSTALL DIR>/board-support/prebuilt-images
$ sudo dd if=u-boot-omapl138-lcdk.ais of=/dev/sd<N> seek=117 bs=512 conv=fsync

    I assume it is the same command for MCSDK 1.1 and this is the one you used to burn SD card.

    You didn't mention if prebuilt image be able to burn to SD card and works on TI EVM. That will be one way to verify your process. 

    Rex

  • 0 in reply to Rex Chang
    Expert 1770 points

    Hi Rex,

    Thank you, I'l follow your recommendations.

    Best Regards,

    ristoH