There will be an MMC error after TX2 system is rebrushed

We have a batch of TX2 8GB modules. We used SDKmanager to refresh the latest version L4T system on the baseplate of the official suite, and found that one of them would have the following error message after the brush was finished:

[ 5.587589] gpu-throttle-alert cooling device registered.
[ 5.799222] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
[ 5.978770] mmc1: Data timeout error
[ 5.982346] sdhci: =========== REGISTER DUMP (mmc1)===========
[ 5.988168] sdhci: Sys addr: 0x00000000 | Version: 0x00000404
[ 5.993990] sdhci: Blk size: 0x00007004 | Blk cnt: 0x00000001
[ 5.999812] sdhci: Argument: 0x15005804 | Trn mode: 0x00000013
[ 6.005633] sdhci: Present: 0x01fb0000 | Host ctl: 0x00000017
[ 6.011454] sdhci: Power: 0x00000001 | Blk gap: 0x00000000
[ 6.017276] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
[ 6.023097] sdhci: Timeout: 0x0000000b | Int stat: 0x00000000
[ 6.028919] sdhci: Int enab: 0x02ff100b | Sig enab: 0x02fc100b
[ 6.034740] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 6.040562] sdhci: Caps: 0x3f6cd08c | Caps_1: 0x18006f73
[ 6.046383] sdhci: Cmd: 0x0000353a | Max curr: 0x00000000
[ 6.052203] sdhci: Host ctl2: 0x0000308b
[ 6.056118] sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000fc100410
[ 6.062649] sdhci: ===========================================
[ 6.139874] fuse init (API version 7.26)
[ 7.481884] mmc1: Data timeout error
[ 7.485460] sdhci: =========== REGISTER DUMP (mmc1)===========
[ 7.491283] sdhci: Sys addr: 0x00000000 | Version: 0x00000404
[ 7.497105] sdhci: Blk size: 0x00007004 | Blk cnt: 0x00000001
[ 7.502925] sdhci: Argument: 0x15000804 | Trn mode: 0x00000013
[ 7.508747] sdhci: Present: 0x01fb0000 | Host ctl: 0x00000017
[ 7.514568] sdhci: Power: 0x00000001 | Blk gap: 0x00000000
[ 7.520389] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
[ 7.526208] sdhci: Timeout: 0x0000000b | Int stat: 0x00000000
[ 7.532029] sdhci: Int enab: 0x02ff100b | Sig enab: 0x02fc100b
[ 7.537850] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 7.543672] sdhci: Caps: 0x3f6cd08c | Caps_1: 0x18006f73
[ 7.549495] sdhci: Cmd: 0x0000353a | Max curr: 0x00000000
[ 7.555316] sdhci: Host ctl2: 0x0000308b
[ 7.559233] sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000fc100410
[ 7.565764] sdhci: ===========================================

The following is related log information.
tx2_mmc_error_dmesg.log (66.6 KB)

Please share the S/N and the jetpack release in use here.

SN:1420820037279
Jetpack 4.6.2

Hi,

Are you still able to operate your device with console under such situation?

Can enter the system desktop, but the system runs very slowly, and it will affect the operation of our software

Hi,

Are we talking about devkit or custom board?

Only one module hit issue or a batch of module?

Devkit, and only one module hit issue, but we have a batch of modules.

我的意思是如果這是單一module的問題, 麻煩請RMA.

如果是整批module都有問題, 那我們就得繼續確認

所以是哪種狀況?

My point is, if this is only one module case, then please RMA. If the whole batch has this issue, then we need to keep checking here.

What is the case now?

Now only one module has this issue.

Ok then please RMA the module.

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