Tx2 MMC Error (on a fairly new device)

Autonomous Machines Jetson & Embedded Systems Jetson TX2
#1

Hi there, I believe my MMC is failing. But this is a new device. Is this an issue with the Tx2 itself, or would the carrier board be the problem?

Would love some help

[   23.627980] mmc1: Timeout waiting for hardware cmd interrupt.
[   23.633943] sdhci: =========== REGISTER DUMP (mmc1)===========
[   23.639874] sdhci: Sys addr: 0x00000000 | Version:  0x00000404
[   23.645773] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[   23.651676] sdhci: Argument: 0x80062000 | Trn mode: 0x00000000
[   23.657573] sdhci: Present:  0x01fb00f1 | Host ctl: 0x00000001
[   23.663468] sdhci: Power:    0x00000000 | Blk gap:  0x00000000
[   23.669358] sdhci: Wake-up:  0x00000000 | Clock:    0x00000403
[   23.675242] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[   23.681125] sdhci: Int enab: 0x00ff1003 | Sig enab: 0x00fc1003
[   23.687008] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[   23.692895] sdhci: Caps:     0x3f6cd08c | Caps_1:   0x18006f73
[   23.698781] sdhci: Cmd:      0x0000341a | Max curr: 0x00000000
[   23.704666] sdhci: Host ctl2: 0x00003000
[   23.708654] sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000fc100410
[   23.715325] sdhci: ===========================================
[   23.722188] brcmfmac: probe of mmc1:0001:3 failed with error -110
[   23.723709] usbcore: registered new interface driver brcmfmac
[   23.726620] vdd-1v8: voltage operation not allowed
[   23.731594] sdhci-tegra 3440000.sdhci: could not set regulator OCR (-1)
[   23.749768] sdhci-tegra 3440000.sdhci: Auto calibration timed out
[   23.756388] mmc1: Got command interrupt 0x00010001 even though no command operation was in progress.
[   23.765571] sdhci: =========== REGISTER DUMP (mmc1)===========
[   23.771450] sdhci: Sys addr: 0x00000000 | Version:  0x00000404
[   23.777325] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
[   23.783200] sdhci: Argument: 0x80062000 | Trn mode: 0x00000000
[   23.789078] sdhci: Present:  0x01fb0000 | Host ctl: 0x00000000
[   23.794952] sdhci: Power:    0x00000001 | Blk gap:  0x00000000
[   23.800823] sdhci: Wake-up:  0x00000000 | Clock:    0x00000407
[   23.806694] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
[   23.812565] sdhci: Int enab: 0x00ff1003 | Sig enab: 0x00fc1003
[   23.818431] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[   23.824299] sdhci: Caps:     0x3f6cd08c | Caps_1:   0x18006f73
[   23.830166] sdhci: Cmd:      0x0000341a | Max curr: 0x00000000
[   23.836031] sdhci: Host ctl2: 0x00003008
[   23.839996] sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000fc100410
[   23.846643] sdhci: ===========================================
#2

It could be either. If you have a third party carrier board, then you’d need to add that board support package or it might fail on that carrier. If this is the dev kit, then you’d have to say what was flashed to it, and if it was previously working (you said it is new, so I’m thinking maybe you flashed it or not…if not, then you’d need to try to flash it once…if this arrived as a production module and not a dev kit, then no software was ever flashed to it and eMMC won’t function till flashed).

#3

I do have a third party carrier board (orbitty). I’ve never had this problem with other carrier boards though. I have 15 or so devices running the exact same setup.

I flashed it with BalenaOS, so I had to do the whole flash with Jetson then flash with BalenaOS dance.

#4

Every flashed image, and the non-rootfs content, requires customization for different carrier boards. In some cases a third party carrier board may have components wired in the same way as does the developer kit, and the components which are wired the same would work. On the other hand, any component which does not match the layout of the developer carrier board (which used on a non-developer carrier board) would fail. An example of when two components are wired the same across carrier boards, but would still fail, is if the power rail setup were different (the components would appear to be wired the same, but without power there would still be a failure). So you do need to customize for your carrier board.

I’ve only heard of Balena being used with a Nano, not a TX2. And I’m not sure how you’d apply a third party BSP via Balena anyway. I’ll recommend directly flashing the TX2 using JetPack/SDK Manager after adding the Orbitty board support package content.

#5

They do offer tx2 with orbitty, that’s what I’ve been using with my other devices:


It’s all good. I’ll test to see if it’s a failed carrier board and we can go from there!

#6