We have an interesting issue where the Jetson won’t initialize the QSPI, so we can’t interact with the SMD firmware, do A/B redudnancy, etc. In the dmesg:
[ 5.569214] qspi_mtd spi6.0: unrecognized JEDEC id 000000
Since it’s the dev kit, I have independent SD cards with our kernel and rootfs, and the “stock” l4t-32.5.1 installation. The “stock” version does see the QSPI:
[ 1.627226] qspi_mtd spi6.0: s25fs256s SSG 8 0 1000 2000000 [ 1.627235] qspi_mtd spi6.0: s25fs256s (32768 Kbytes) [ 1.627245] qspi_mtd spi6.0: mtd .name = spi6.0, .size = 0x2000000 (32MiB) .erasesize = 0x00010000 (64KiB) .numeraseregions = 0 [ 1.627462] 1 ofpart partitions found on MTD device spi6.0 [ 1.627467] Creating 1 MTD partitions on "spi6.0": [ 1.627491] 0x000000000000-0x000002000000 : "Whole_flash0"
So I know the hardware is working.
I’ve tried various N-way diffs between the dmesg logs,
/proc/config.gz, DTB, and kernel source code looking for an obvious difference, and am stumped.
Any suggestions on approaches for debugging this issue?