• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 763 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Linux/AM5708: U-boot failed to start

TianShen
Intellectual 510 points
Part Number: AM5708
Other Parts Discussed in Thread: DRA742, PCF8575, PMP

Tool/software: Linux

Hi:

Software version: ti-processor-sdk-linux-am57xx-evm-04.03.00.05,  hardware version: AM5708-ES2.0, custom board,

The main chip model XAM5708BCBDJEA is equipped with the power management chip model tps65919, and u-boot is successfully started.
The main chip model AM5708BCBDJA is equipped with the power management chip model tps65919, u-boot fails to start.

U-boot prompt error is as follows：

U-Boot SPL 2017.01 (Nov 14 2018 - 01:38:38) 

DRA722-GP ES2.0 
Trying to boot from MMC1 
omap_hsmmc_send_cmd: timedout waiting on cmd inhibit to clear 
omap_hsmmc_send_cmd: timedout waiting on cmd inhibit to clear 
omap_hsmmc_send_cmd: timedout waiting on cmd inhibit to clear 
spl: mmc init failed with error: -110 
SPL: failed to boot from all boot devices 
### ERROR ### Please RESET the board ###

We will change the main chip model XAM5708BCBDJEA into AM5708BCBDJA hardware and software needs to be changed.
Best Regards
Biser
  • 0
    TI__Guru**** 170625 points
    Hi Shen,

    Is it the same custom board, on which you replace XAM5708BCBDJEA with AM5708BCBDJA? Or you have two custom boards, one with XAM5708BCBDJEA and one with AM5708BCBDJA?

    Both devices are ES2.1, while your boot flow shows ES2.0. Can you provide also the successful u-boot boot log (XAM5708BCBDJEA)?

    The only difference I see between these two AM5708 devices is that AM5708BCBDJA support only basic industrial protocols, while XAM5708BCBDJEA support all (basic + EtherCAT slave and POWERLINK slave). Have you made any modifications in u-boot code base regarding EtherCAT and POWERLINK industrial protocols?

    Regards,
    Pavel
  • 0 in reply to Pavel Botev
    Intellectual 510 points

    Hi:

    yes, on which you replace XAM5708BCBDJEA with AM5708BCBDJA, have two custom boards, one with XAM5708BCBDJEA and one with AM5708BCBDJA.

    U-boot boot log:(XAM5708BCBDJEA)

    U-Boot 2017.01 (Nov 15 2018 - 19:47:42 -0800)

    CPU : DRA722-GP ES2.0
    Model: TI DRA742
    Board: DRA72x EVM REV
    DRAM: 1 GiB
    NAND: 0 MiB
    MMC: i2c_write: error waiting for data ACK (status=0x116)
    pcf8575_i2c_write_le16 i2c write failed to addr 21
    OMAP SD/MMC: 0, OMAP SD/MMC: 1
    reading uboot.env

    ** Unable to read "uboot.env" from mmc0:1 **
    Using default environment

    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: addr 1 01 line: 860
    phy_mask 2 02 line: 678
    devad -1 ffffffff line: 679
    phy_id 33281 8201 line: 683

    Warning: ethernet@48484000 using MAC address from ROM
    eth0: ethernet@48484000
    Hit any key to stop autoboot: 0

    =>

  • 0 in reply to TianShen
    TI__Guru**** 170625 points

    Tian,

    Do you use MMC/SD card boot for both boards?

    Do you use the same u-boot code base for both boards?

    Have you made any modifications in u-boot code base regarding EtherCAT and POWERLINK industrial protocols?

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    TI__Guru**** 170625 points
    If you have no more questions related to the subject, please close/verify/resolve this thread.

    Regards,
    Pavel