• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 353 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.

AM5728: Custom Board failed boot

Hanmant Gaikwad
Prodigy 110 points
Part Number: AM5728
Other Parts Discussed in Thread: PMP

Hi,

Failed to boot my custom Am5728 board from sd card u-boot.

please see output logs as below:


U-Boot SPL 2016.05-00118-gdd926c6000-dirty (Dec 18 2023 - 18:34:54)
DRA752-GP ES2.0
Trying to boot from MMC1
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img
reading u-boot.img
reading u-boot.img


U-Boot 2016.05-00118-gdd926c6000-dirty (Dec 18 2023 - 18:34:54 +0530)

CPU : DRA752-GP ES2.0
Model: TI AM5728 IDK
Board: AM572x IDK REV <NULL>
DRAM: 2 GiB
MMC: no pinctrl for sdr104
no pinctrl for ddr50
no pinctrl for sdr50
no pinctrl for sdr25
no pinctrl for sdr12
OMAP SD/MMC: 0, OMAP SD/MMC: 1
MMC: no card present
** Bad device mmc 0 **
Using default environment

I2C chip 50: requested alen 2 does not match chip offset_len 1
SCSI: SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst
scanning bus for devices...
Found 0 device(s).
Net: <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot: 0
MMC: no card present
MMC: no card present
MMC: no card present
MMC: no card present
** First descriptor is NOT a primary desc on 1:1 **
switch to partitions #0, OK
mmc1(part 0) is current device
** First descriptor is NOT a primary desc on 1:1 **
SD/MMC found on device 1
** No partition table - mmc 1 **

  • 0
    TI__Mastermind 31805 points

    Hello Hanmant,

    Seems like there is issues finding your device SD card. 

    Is your board design very similar to one of the TI boards? If so, which one? Which mmc device is supposed to be your SD card?

    It also looks like you are using an older SDK? Could you confirm please.

    -Josue

  • 0 in reply to Josue Zamitiz-Ayala
    Prodigy 110 points

    Yes I'm using old SDK .

    I run command on u-boot terminal and i see below:

    => mmc list
    OMAP SD/MMC: 0
    OMAP SD/MMC: 1 (eMMC)

    => mmc info
    Device: OMAP SD/MMC
    Manufacturer ID: da
    OEM: 100
    Name: 00064
    Tran Speed: 52000000
    Rd Block Len: 512
    MMC version 5.0
    High Capacity: Yes
    Capacity: 58.3 GiB
    Bus Width: 8-bit DDR
    Erase Group Size: 512 KiB
    HC WP Group Size: 8 MiB
    User Capacity: 58.3 GiB WRREL
    Boot Capacity: 4 MiB ENH
    RPMB Capacity: 4 MiB ENH

    below is design related to sd/mmc1

  • 0 in reply to Hanmant Gaikwad
    Prodigy 110 points


    => mmc dev 0
    MMC: no card present
    => mmc dev 1
    ** First descriptor is NOT a primary desc on 1:1 **
    switch to partitions #0, OK
    mmc1(part 0) is current device
    =>

  • 0 in reply to Hanmant Gaikwad
    TI__Mastermind 31805 points

    Hello Hanmant, 

    Your mmc printout is very different then ours.

    Device: OMAP SD/MMC
Manufacturer ID: 9f
OEM: 5449
Name: 00000 
Bus Speed: 24000000
Mode: MMC legacy
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 29.1 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
=> mmc list
OMAP SD/MMC: 0 (SD)
OMAP SD/MMC: 1 (eMMC)

    So I suspect your DT entry looks different than ours.

    Also, your design seems to not be following the schematic checklist

    Please see https://www.ti.com/lit/an/sprack7b/sprack7b.pdf#page=9

    "For SD-CARD implementations, 10K pull-up resistors are needed on all data signals and on the command signal."

    -Josue

  • 0 in reply to Josue Zamitiz-Ayala
    Prodigy 110 points

    HI Josue,

    Thanks for your answer .

    please confirm is it Ok to MMC1_DATA3 and MMC1_SDCD ?As in our design we have connected MMC1_DATA3 and MMC1_SDCD .

    I will replace  all signal with 10K pull-up resistors.

    Is there any idea or anything i need to change in u-boot code?

    Please suggest me to resolve.

    Thanks,

    Hanmant

  • 0 in reply to Hanmant Gaikwad
    TI__Mastermind 31805 points

    Hello Hanmant,

    I will need to double check with our HW engineers for :

    Hanmant Gaikwad said:
    please confirm is it Ok to MMC1_DATA3 and MMC1_SDCD ?As in our design we have connected MMC1_DATA3 and MMC1_SDCD .

    but based on our reference board, it seems like this could be ok ..

    Have you made any changes in U-boot from the base SDK?
    Can you share your DTS entries for SD card?

    -Josue