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

Linux/DRA75: Invalid MMC Device

Kevin S
Mastermind 38390 points
Part Number: DRA75

Tool/software: Linux

Hi,

I am using the TI EVM and trying to boot from eMMC, but obtain the following error:

MMC: bus-width property missing; assuming 1 bit
mmc@4809c000: fail to find default mode FDT_ERR_BADSTRUCTURE
no pinctrl state for default mode
mmc@4809c000 - probe failed: -22
àçùþàçùþHòýHòýðçùþðçùþøçùþøçùþ: 0
MMC Device 1 not found

Please let me know if you have seen this before and what work-around fixed the issue; thanks!

Best regards,
Kevin

  • 0
    TI__Guru*** 125430 points
    Kevin,

    That's not an error I commonly see. Seems like something fundamental is wrong. Are you using the binaries provided by one of the SDK's, or is this something you built? Is the error being shown in SPL, u-boot, or LInux boot? A complete boot log would be preferable. Also please include information on which SDK version you're using, or details such as what defconfig you built, etc. Can you boot from SD card? How did you format/flash the eMMC?

    Best regards,
    Brad
  • 0 in reply to Brad Griffis
    TI__Mastermind 42515 points
    Hi Kevin,

    do you need more help on this?
    Can we close the thread?

    Regards,
    Yordan
  • 0 in reply to Yordan Kamenov
    TI__Mastermind 38390 points

    Hi Brad,

    Thanks for the inputs and quick response. This was a modified version of u-boot based on 6AO.1.1. 

    Hi Yordan,

    You can close the thread. Something I changed in software must have been causing the issue because the issue did not appear when reverting back to the baseline images. I was going to try and see what change caused the issue and post back here, but have not had a chance to debug further. 

    Best regards,
    Kevin