No response from MMC (CONFIG_MMC_TRACE)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

No response from MMC (CONFIG_MMC_TRACE)

469 Views
AlanWen
Contributor II

I want to enable CMD response from the MMC with "#define CONFIG_MMC_TRACE" in mmc.h but there is nothing happened after I boot up the device.

======================================== mmc.h

struct bd_info;
#if CONFIG_IS_ENABLED(MMC_HS200_SUPPORT)
#define MMC_SUPPORTS_TUNING
#endif
#if CONFIG_IS_ENABLED(MMC_UHS_SUPPORT)
#define MMC_SUPPORTS_TUNING
#endif
#define CONFIG_MMC_TRACE
/* SD/MMC version bits; 8 flags, 8 major, 8 minor, 8 change */
#define SD_VERSION_SD (1U << 31)
#define MMC_VERSION_MMC (1U << 30)
...

 

======================================== boot up log

U-Boot SPL 2022.04-lf_v2022.04+g7376547b9e (Mar 01 2023 - 07:35:40 +0000)
DDRINFO: start DRAM init
DDRINFO: DRAM rate 4000MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
SEC0: RNG instantiated
Normal Boot
Trying to boot from BOOTROM
Boot Stage: Primary boot
image offset 0x8000, pagesize 0x200, ivt offset 0x0
NOTICE: BL31: v2.6(release):lf-6.1.1-1.0.0-0-g616a4588f
NOTICE: BL31: Built : 10:31:38, Mar 1 2023


U-Boot 2022.04-lf_v2022.04+g7376547b9e (Mar 01 2023 - 07:35:40 +0000)

CPU: i.MX8MP[8] rev1.1 1600 MHz (running at 1200 MHz)
CPU: Industrial temperature grade (-40C to 105C) at 29C
Reset cause: POR
Model: NXP i.MX8MPlus LPDDR4 EVK board
DRAM: 4 GiB
tcpc_init: Can't find device id=0x50
setup_typec: tcpc port2 init failed, err=-19
tcpc_init: Can't find device id=0x50
setup_typec: tcpc port1 init failed, err=-19
Core: 193 devices, 29 uclasses, devicetree: separate
MMC: FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... *** Warning - bad CRC, using default environment

[*]-Video Link 0adv7535_mipi2hdmi adv7535@3d: Can't find cec device id=0x3c
fail to probe panel device adv7535@3d
fail to get display timings
probe video device failed, ret -19

[0] lcd-controller@32e80000, video
[1] mipi_dsi@32e60000, video_bridge
[2] adv7535@3d, panel
adv7535_mipi2hdmi adv7535@3d: Can't find cec device id=0x3c
fail to probe panel device adv7535@3d
fail to get display timings
probe video device failed, ret -19
In: serial
Out: serial
Err: serial
SEC0: RNG instantiated

BuildInfo:
- ATF 616a458

switch to partitions #0, OK
mmc1 is current device
flash target is MMC:1
Net:
Warning: ethernet@30bf0000 (eth1) using random MAC address - 1e:ac:13:06:9b:69

Warning: ethernet@30be0000 (eth0) using random MAC address - a2:bd:26:f1:7e:7f
eth0: ethernet@30be0000, eth1: ethernet@30bf0000 [PRIME]
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
starting USB...
Bus usb@38100000: Failed to initialize board for imx8m USB
probe failed, error -22
Bus usb@38200000: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@38200000 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot.scr
157 bytes read in 2 ms (76.2 KiB/s)
## Executing script at 43500000
35262304 bytes read in 5769 ms (5.8 MiB/s)
Booting from mmc ...
85843 bytes read in 16 ms (5.1 MiB/s)
## Flattened Device Tree blob at 43000000
Booting using the fdt blob at 0x43000000
clk usb_phy_root_clk already disabled
Using Device Tree in place at 0000000043000000, end 0000000043017f52
adv7535_mipi2hdmi adv7535@3d: Can't find cec device id=0x3c
fail to probe panel device adv7535@3d
fail to get display timings
probe video device failed, ret -19

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]

...

========================================

It should be like

U-Boot SPL 2023.04-lf_v2023.04+gaf7d004eaf (Jun 06 2023 - 14:59:40 +0000)
DDRINFO: start DRAM init
DDRINFO: DRAM rate 4000MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
SEC0: RNG instantiated
Normal Boot
Trying to boot from BOOTROM
Boot Stage: Primary boot
image offset 0x0, pagesize 0x200, ivt offset 0x0
NOTICE: Do not release JR0 to NS as it can be used by HAB
NOTICE: BL31: v2.8(release):android-13.0.0_2.0.0-0-ge4b2dbfa5
NOTICE: BL31: Built : 06:14:17, Jun 2 2023


U-Boot 2023.04-lf_v2023.04+gaf7d004eaf (Jun 06 2023 - 14:59:40 +0000)

CPU: i.MX8MP[8] rev1.1 1800 MHz (running at 1200 MHz)
CPU: Commercial temperature grade (0C to 95C) at 26C
Reset cause: POR
Model: NXP i.MX8MPlus LPDDR4 EVK board
DRAM: 6 GiB
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C2 0x50]
SNK.Power3.0 on CC1
PDO 0: type 0, 5000 mV, 3000 mA [E]
PDO 1: type 0, 9000 mV, 3000 mA []
PDO 2: type 0, 15000 mV, 3000 mA []
PDO 3: type 0, 20000 mV, 2250 mA []
Requesting PDO 3: 20000 mV, 2250 mA
Source accept request
PD source ready!
tcpc_pd_receive_message: Polling ALERT register, TCPC_ALERT_RX_STATUS bit failed, ret = -62
Power supply on USB2
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x50]
Core: 257 devices, 36 uclasses, devicetree: separate
MMC: FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... CMD_SEND:0
ARG 0x00000000
MMC_RSP_NONE
CMD_SEND:8
ARG 0x000001aa
RET -110
CMD_SEND:55
ARG 0x00000000
RET -110
CMD_SEND:0
ARG 0x00000000
MMC_RSP_NONE
CMD_SEND:8
ARG 0x000001aa
RET -110
CMD_SEND:55
ARG 0x00000000
RET -110
CMD_SEND:0
ARG 0x00000000
MMC_RSP_NONE
CMD_SEND:1
ARG 0x00000000
MMC_RSP_R3,4 0x40ff8080
CMD_SEND:1
ARG 0x40360080
MMC_RSP_R3,4 0x40ff8080
CMD_SEND:1
ARG 0x40360080
MMC_RSP_R3,4 0xc0ff8080
CMD_SEND:2
ARG 0x00000000
MMC_RSP_R2 0x45010044
0x47343033
0x3201108f
0xdc21c800

DUMPING DATA
000 - 45 01 00 44
004 - 47 34 30 33
008 - 32 01 10 8f
012 - dc 21 c8 00
CMD_SEND:3
ARG 0x00010000
MMC_RSP_R1,5,6,7 0x00000500
CMD_SEND:9
ARG 0x00010000
MMC_RSP_R2 0xd00f0032
0x8f5903ff
0xffffffef
0x8a404000

DUMPING DATA
000 - d0 0f 00 32
004 - 8f 59 03 ff
008 - ff ff ff ef
012 - 8a 40 40 00
CMD_SEND:7
ARG 0x00010000
MMC_RSP_R1,5,6,7 0x00000700
CMD_SEND:8
ARG 0x00000000
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:6
ARG 0x03b70200
MMC_RSP_R1b 0x00000800
CMD_SEND:13
ARG 0x00010000
MMC_RSP_R1,5,6,7 0x00000900
CURR STATE:4
CMD_SEND:6
ARG 0x03b90100
MMC_RSP_R1b 0x00000800
CMD_SEND:8
ARG 0x00000000
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:6
ARG 0x03b78600
MMC_RSP_R1b 0x00000800
CMD_SEND:13
ARG 0x00010000
MMC_RSP_R1,5,6,7 0x00000900
CURR STATE:4
CMD_SEND:6
ARG 0x03b90300
MMC_RSP_R1b 0x00000800
CMD_SEND:13
ARG 0x00010000
MMC_RSP_R1,5,6,7 0x00000900
CURR STATE:4
CMD_SEND:8
ARG 0x00000000
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:17
ARG 0x00000000
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:17
ARG 0x00004000
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:17
ARG 0x00030000
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:18
ARG 0x00030002
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:12
ARG 0x00000000
MMC_RSP_R1b 0x00000b00
CMD_SEND:17
ARG 0x00030008
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:17
ARG 0x00032118
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:18
ARG 0x00003800
MMC_RSP_R1,5,6,7 0x00000900
CMD_SEND:12
ARG 0x00000000
MMC_RSP_R1b 0x00000b00
OK
[*]-Video Link 0adv7535_mipi2hdmi adv7535@3d: Can't find cec device id=0x3c
fail to probe panel device adv7535@3d
fail to get display timings
probe video device failed, ret -19

...

Is there any issue with my operation ?

or

Is there any other way to show the CMD response ?

Thanks

Labels (2)
Tags (3)
0 Kudos
2 Replies

445 Views
Rita_Wang
NXP TechSupport
NXP TechSupport

Before you enable the #define CONFIG_MMC_TRACE" can system boot up well ?

0 Kudos

441 Views
AlanWen
Contributor II

Probably yes, I can boot up when first power on but I got failed while calling reboot command and encountered the "Error reading cluster" issue in u-boot. About the MMC response, I think it will show up any first time when I boot up the device but it did not show even the first boot up.

AlanWen_0-1697188075567.png

 

0 Kudos