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

Original question:

AM5718: EMIF tools question

Linux/AM5718: SPL: failed to boot from all boot devices

ravi rk
Intellectual 925 points
Part Number: AM5718


Tool/software: Linux

Hi ,

We are try to bring up AM5718 custom board, we successfully boot up u-boot-spl.

While loading u-boot i am getting following  error,

And board boot through Micro SD Card on MMC1

U-Boot SPL 2018.01-00569-gfd38f5a-dirty (May 08 2019 - 15:32:32)
DRA722-GP ES2.0
SPL: 355 Trying to boot from MMC1
spl_mmc_load filename u-boot.img
no pinctrl state for default mode
no pinctrl state for default mode
spl_load_image_fat_os: error reading image args, err - -2
omap_hsmmc_send_cmd : DMA timeout: No status update
Error reading cluster
spl_load_image_fat_buf: error reading image u-boot.img, err - -1

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
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
** Can't read partition table on 0:0 **
spl: no partition table found
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
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
** Can't read partition table on 0:0 **
spl: no partition table found
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

we are running out of time,so kind help us to over come this issue.

Regards,

Ravi

  • 0
    TI__Guru 55345 points

    Hello Ravi,

    You have an incorrect MMC1 pinmux settings in U-Boot or there is a bad hardware connection with MMC1. Please, see this post for more details.

    Best regards,
    Kemal

  • 0 in reply to Kemal R. Shakir
    Intellectual 925 points

    Hi Kemal,

    I found pinmux in "u-boot-2018.01+gitAUTOINC+313dcd69c2-g825ac6e1ac/board/ti/am57xx/mux_data.h" and look like below

    {MMC1_CLK, (M0 | PIN_INPUT_PULLUP)}, /* mmc1_clk.mmc1_clk */
    {MMC1_CMD, (M0 | PIN_INPUT_PULLUP)}, /* mmc1_cmd.mmc1_cmd */
    {MMC1_DAT0, (M0 | PIN_INPUT_PULLUP)}, /* mmc1_dat0.mmc1_dat0 */
    {MMC1_DAT1, (M0 | PIN_INPUT_PULLUP)}, /* mmc1_dat1.mmc1_dat1 */
    {MMC1_DAT2, (M0 | PIN_INPUT_PULLUP)}, /* mmc1_dat2.mmc1_dat2 */
    {MMC1_DAT3, (M0 | PIN_INPUT_PULLUP)}, /* mmc1_dat3.mmc1_dat3 */
    {MMC1_SDCD, (M14 | PIN_INPUT | SLEWCONTROL)}, /* mmc1_sdcd.gpio6_27 */
    {MMC1_SDWP, (M14 | PIN_INPUT | SLEWCONTROL)}, /* mmc1_sdwp.gpio6_28 */

    And DTS file used am57xx-idk-common.dtsi and am571x-idk.dts

    &mmc1 {
    status = "okay";
    vmmc-supply = <&v3_3d>;
    vqmmc-supply = <&ldo1_reg>;
    bus-width = <4>;
    cd-gpios = <&gpio6 27 GPIO_ACTIVE_LOW>; /* gpio 219 */
    };

    &mmc1 {
    pinctrl-names = "default", "hs", "sdr12", "sdr25", "sdr50", "ddr50", "sdr104";
    pinctrl-0 = <&mmc1_pins_default>;
    pinctrl-1 = <&mmc1_pins_hs>;
    pinctrl-2 = <&mmc1_pins_sdr12>;
    pinctrl-3 = <&mmc1_pins_sdr25>;
    pinctrl-4 = <&mmc1_pins_sdr50>;
    pinctrl-5 = <&mmc1_pins_ddr50_rev20 &mmc1_iodelay_ddr50_conf>;
    pinctrl-6 = <&mmc1_pins_sdr104 &mmc1_iodelay_sdr104_rev20_conf>;
    };

    In our design We follow AM5718-IDK schematic for MMC1 SD Card interface,expect the "mmc1_sdwp.gpio6_28"  is NC.

    For your information same SD card is booted on AM5718-IDK.

    Regards,

    Ravi

  • 0 in reply to ravi rk
    TI__Guru 55345 points
    Hello Ravi,

    Are you still facing this issue or you have resolved it?

    Best regards,
    Kemal
  • 0 in reply to Kemal R. Shakir
    Intellectual 925 points
    Hi Kemal,

    Yes, we are still facing this issue.

    For your information, If we have enabled the debug print (Adding the " #define DEBUG" in am57xx_evm.h file) then this issue not produced(randomly) & we observed u-boot.img image fat read debug prints. But in this case also u-boot jump not happened.

    In debug prints disabled case (Don't enabled "#define DEBUG" in am57xx_evm.h file) case, always we have faced "spl_load_image_fat_buf: error reading image u-boot.img, err - -1" issue.

    Regards,
    Ravi
  • 0 in reply to ravi rk
    TI__Guru 55345 points
    Can you attach the boot log with " #define DEBUG" enabled in am57xx_evm.h file?
  • 0 in reply to Kemal R. Shakir
    Intellectual 925 points

    Hi Kemal,

    We have got 2x different log files with same software by power OFF/ON the platform. 

    Logfile Name: AM5718_Logfiles_17May2019.zip




  • 0 in reply to ravi rk
    TI__Guru 55345 points

    The strange things I've noticed in the logs are, omap_hsmmc_getcd value : <1465> , [1] and the second time part_init: try 'DOS': ret=-1 returns -1 except 0. Can you do your investigation in this direction? Also can you remove the "#define DEBUG" from am57xx_evm.h run ARCH=arm make menuconfig and disable the SPL / TPL  ---> [ ]   Only use malloc_simple functions in the SPL option and see if the booting goes further.

  • 0 in reply to Kemal R. Shakir
    Intellectual 925 points

    Hi kemal,

    Thanks for your support.

    We solve our issue,now we stuck in kernel reboot issue I posted here https://e2e.ti.com/support/processors/f/791/t/805224.

    Regards,

    Ravi