- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Translated Content
- :
- Multi Source Translation Content
- :
- 2414316_en-US
2414316_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2414316_en-US
2414316_en-US
Hi, I am using a CompuLab UCM-iMX95 and I am trying to install and boot Yocto Linux from a micro-SD card.
The boot process starts, and U-Boot successfully loads the Linux kernel. However, Linux fails to initialize the SD/MMC interface.
I get the following error:
mmc0: Timeout waiting for hardware interrupt.
mmc0: sdhci: ============ SDHCI REGISTER DUMP ============ ...
mmc0: error -110 whilst initialising MMC card The kernel then gets stuck during boot.
My Linux version is: Linux 6.12.34-2.0-... The board is: CompuLab UCM-iMX95 I am building my own Yocto image and writing it to a micro-SD card.
Could someone please help me understand what could be causing this mmc0 error -110? In particular: Is this likely to be a hardware/SD-card issue,
or could it be related to the device tree? Which MMC controller corresponds to the micro-SD interface on the UCM-iMX95?
Are there any specific device-tree settings required for the SD interface?
Is there a recommended U-Boot command to verify that the SD card is detected before Linux boots? Is there a known-good UCM-iMX95 Yocto configuration that I can compare my configuration against?
Hello,
The error log you are getting tell us that the MMC controller is attempting to communicate with a device that either wasn't present or wasn't responding properly. The recommended solution is to disable the unused MMC interfaces or fix the DT you configuration.
Our EVK reference design device tree uses the next configuration:
mmc0 usdhc1 eMMC
mmc1 usdhc2 SD cardYou can use our device tree as reference:
Best regards.