- 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
- 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
-
- 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
-
- 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
-
- Home
- :
- i.MX Forums
- :
- i.MX Processors
- :
- "mmc fail to send stop cmd" in uboot-2020-04 on Linux 5.4.47_2.2.0
"mmc fail to send stop cmd" in uboot-2020-04 on Linux 5.4.47_2.2.0
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
We try to upgrade our product to the new Linux 5.4.47_2.2.0 release, starting with uboot.
MMC is not working in uboot, we get these errors:
U-Boot 2020.04-5.4.47-2.2.0+gffc3fbe (Oct 20 2020 - 17:30:17 +0000)
CPU: i.MX6Q rev1.3 996 MHz (running at 792 MHz)
CPU: Extended Commercial temperature grade (-20C to 105C) at 37C
Reset cause: POR
Model: Freescale i.MX6 Quad AME V2GCC
Board: MX6Q_V2GCC ()
Hardware PN: 6015-1800-4602 SN: 19-24-001-072
DRAM: 1 GiB
PMIC: PFUZE100! DEV_ID=0x10 REV_ID=0x21
MMC: No max bus width provided. Assume 8-bit supported.
FSL_SDHC: 0, FSL_SDHC: 1
Warning: i.MX Power-on reset. Kernel did not load! Rootfs did not load!
Booting from USDHC-4, MMC device 1
Normal Boot
Autoboot in 1 seconds.
## Error: "checkLogo" not defined
switch to partitions #0, OK
mmc1(part 0) is current device
mmc fail to send stop cmd
*** ERROR: Can't read GPT Entries ***
GPT: Failed to allocate memory for PTE
mmc fail to send stop cmd
*** ERROR: Can't read GPT Entries ***
GPT: Failed to allocate memory for PTE
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
** Invalid partition 1 **
=>
It was working fine on Yocto sumo, uboot 2018.
We do not use CONFIG_DM_MMC but configure it via code.
When i look through the uboot code, i found out that the ESDHC driver is now split.
I tried both CONFIG_FSL_ESDHC_IMX=y and CONFIG_FSL_ESDHC=y
What i found that both do not seem to work, but with CONFIG_FSL_ESDHC=y my mmc info prints output.
With FSL_ESDHC_IMX, the system just hangs when it tries to read from mmc, or access it at all.
I was wondering if this is perhaps a known issue for the release, or if somebody else has encountered this.
Best regards,
Rick Veens
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi guys i have solved the problem.
if someone else would stumble on this problem in the future, you need to define the following:
#define CONFIG_SYS_FSL_ERRATUM_ESDHC111
With some digging i found the function esdhc_send_cmd_common in drivers/mmc/fsl_esdhc.c .
I looked into the IMX6 refrence manual and printed the CMD codes. I noticed that it failed on CMD 12.
For this CMD i noticed there is a ifdef block in the code, with CONFIG_SYS_FSL_ERRATUM_ESDHC111 .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi guys i have solved the problem.
if someone else would stumble on this problem in the future, you need to define the following:
#define CONFIG_SYS_FSL_ERRATUM_ESDHC111
With some digging i found the function esdhc_send_cmd_common in drivers/mmc/fsl_esdhc.c .
I looked into the IMX6 refrence manual and printed the CMD codes. I noticed that it failed on CMD 12.
For this CMD i noticed there is a ifdef block in the code, with CONFIG_SYS_FSL_ERRATUM_ESDHC111 .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @r_veens ,
I'm getting the same error with 2020.04 u-boot. As you mentioned, I've enabled "CONFIG_FSL_ESDHC=y" and added "#define CONFIG_SYS_FSL_ERRATUM_ESDHC111" "in include/configs/board.h" file. But I'm still getting the error. Is there anything else I need to enable it to fix the issue?
