CRC Error During Software Reboot on Jetson Nano with Custom Carrier Board (L4T 32.6.1)

Hello @JerryChang
I am using a Jetson Nano with a custom carrier board and booting from an SD card. I flashed the SD card using the Balena Etcher tool. After flashing, I modified the extlinux configuration file, changing the boot target from mmcblk0p1 to mmcblk1p1. The board is set to autoboot, and it boots successfully from the SD card when power-cycled.

However, I encounter an issue when rebooting the device via software. During a software reboot, the system fails to boot, and I get the following CRC error in the console log:

127.840643] mmcblk1: error -84 transferring data, sector 385080, n0
[ 127.850381] mmcblk1: retrying using single block read
[ 127.857275] mmc1: Data CRC error
[ 127.860526] sdhci: =========== REGISTER DUMP (mmc1) ===========
[ 127.866386] sdhci: Sys addr: 0x00000008 | Version: 0x00000303
[ 127.872270] sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000000
[ 127.878184] sdhci: Argument: 0x0005e039 | Trn mode: 0x00000013
[ 127.884096] sdhci: Present: 0x01fb0000 | Host ctl: 0x00000013
[ 127.890004] sdhci: Power: 0x00000001 | Blk gap: 0x00000000
[ 127.895915] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
[ 127.901824] sdhci: Timeout: 0x0000000e | Int stat: 0x00000000
[ 127.907735] sdhci: Int enab: 0x02ff100b | Sig enab: 0x02fc100b
[ 127.913642] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 127.919551] sdhci: Caps: 0x376cd08c | Caps_1: 0x10006f77
[ 127.925458] sdhci: Cmd: 0x0000113a | Max curr: 0x00000000
[ 127.931365] sdhci: Host ctl2: 0x00003001
[ 127.935362] sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000ffef0
[ 127.942010] sdhci: ===========================================
I am using L4T 32.6.1 on this setup. The issue only arises during a software reboot and not during a power cycle.
Additional Observation:
When I connect an HDMI cable to the device, the CRC error does not occur, and the system boots successfully from the SD card. However, when the HDMI cable is unplugged, the CRC error logs are continuously printed in the console, and I cannot log in to the device.

Could someone explain the reason for this behavior and help me resolve the issue?

Are you the board vendor who made this board or you bought this board from others?

Yes we are the vendor.

Have you modified the device tree to meet your hardware design?

Yes,modified.

You should share that out and schematic for review.

We regret that we cannot share the schematic as it contains proprietary information. However, we would greatly appreciate any guidance or recommendations to help resolve this issue. Could you suggest any specific tests, configurations, or debugging steps we should perform to pinpoint the root cause?

That includes the review of your schematic and how your device tree looks like.

You could search sdmmc3 in this forum as this kind of configuration has been asked for more than 5 years.

Is the Below DTS Change Causing the CRC Errors on My Jetson Nano with a Custom Carrier Board?
patch.txt (1.1 KB)

vmmc-supply is still needed.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.