Jetson Xavier Bricked & Un-flashable

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
1

Working on Ubuntu Desktop 18.04.2 with a Jetson-Xavier that has stopped working.

The UART Debug channel throws

[0010063.673] I> MB1 (prd-version: 1.0.0.0-t194-41334769-a3872862)
[0063.678] I> Boot-mode: L1 RCM
[0063.681] I> chip revision : A02
[0063.684] I> Bootrom patch version : 7 (correctly patched)
[0063.689] I> ATE fuse revision : 0x200
[0063.693] I> Ram repair fuse : 0x0
[0063.696] I> Ram Code : 0x0
[0063.698] I> rst_source : 0xb
[0063.701] I> rst_level : 0x1
[0063.705] I> USB configuration success
[0065.959] I> Command received is 1
[0066.251] I> Command received is 1
[0066.259] I> Command received is 2
[0066.264] I> bct_bootrom image downloaded
[0066.271] I> Command received is 2
[0066.279] E> No fuse-bypass data
[0066.282] E> MB1_PLATFORM_CONFIG: device prod data is empty in MB1 BCT.
[0066.288] E> MB1_PLATFORM_CONFIG: Failed to initialize device prod.
[0066.295] I> temperature = 39500
[0066.298] W> Skipping boost for clk:bpmp_cpu_nic
[0066.303] W> Skipping boost for clk:bpmp_apb
[0066.306] W> Skipping boost for clk:axi_cbb
[0066.310] W> Skipping boost for clk:aon_cpu_nic
[0066.315] W> Skipping boost for clk:aon_can0
[0066.319] W> Skipping boost for clk:aon_can1
[0066.323] I> Boot-device: eMMC
[0066.326] I> Boot-device: eMMC
[0066.329] W> DEVICE_PROD: device prod is not initialized.
[0066.334] W> DEVICE_PROD: device prod is not initialized.
[0066.353] I> Sdmmc: HS400 mode enabled
[0066.357] I> bct_mb1 image downloaded
[0066.363] I> Command received is 2
[0066.374] I> ECC region[0]: Start:0x0, End:0x0
[0066.378] I> ECC region[1]: Start:0x0, End:0x0
[0066.382] I> ECC region[2]: Start:0x0, End:0x0
[0066.386] I> ECC region[3]: Start:0x0, End:0x0
[0066.390] I> ECC region[4]: Start:0x0, End:0x0
[0066.395] I> Non-ECC region[0]: Start:0x80000000, End:0x100000000
[0066.400] I> Non-ECC region[1]: Start:0x0, End:0x0
[0066.405] I> Non-ECC region[2]: Start:0x0, End:0x0
[0066.409] I> Non-ECC region[3]: Start:0x0, End:0x0
[0066.414] I> Non-ECC region[4]: Start:0x0, End:0x0
[0066.420] W> MB1_PLATFORM_CONFIG: Rail ID 9 not found in pmic rail config table.
[0066.427] E> FAILED: Thermal config
[0066.430] W> DEVICE_PROD: device prod is not initialized.
[0066.435] W> DEVICE_PROD: device prod is not initialized.
[0066.444] W> MB1_PLATFORM_CONFIG: Rail ID 7 not found in pmic rail config table.
[0066.451] E> FAILED: MEMIO rail config
[0066.464] E> task 40 failed (err: 0x1c)
[0066.467] E> top caller module: NONE, error module: NONE, reason: 0x1c, aux_info: 0x00
[0066.475] I> MB1(1.0.0.0-t194-41334769-a3872862) BIT boot status dump :
1111111111110000111111111111001100001111100000000000000000000000000000000000000000000000000000000000000000000000000000000000000011001000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

And The Jetpack 4.1 installer fails with the output:

[   9.5355 ] tegrarcm_v2 --download bct_bootrom br_bct_BR.bct --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt --download bct_mem tmpPCVisQ1_1_sigheader.bct.encrypt
[   9.5373 ] Applet version 01.00.0000
[   9.8257 ] Sending bct_bootrom
[   9.8260 ] [................................................] 100%
[   9.8323 ] Sending bct_mb1
[   9.8378 ] [................................................] 100%
[   9.8471 ] Sending bct_mem
[   9.9303 ] [................................................] 100%
[  10.0775 ] 
Error: Return value 8
Command tegrarcm_v2 --download bct_bootrom br_bct_BR.bct --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt --download bct_mem tmpPCVisQ1_1_sigheader.bct.encrypt
Failed flashing t186ref.

I get the same error when trying to flash Jetpack 4.2

I have run through the forums but there is no obvious place to find the meaning of this return value and the debug error is equally unhelpful.

2

I can’t answer, but whoever responds will probably want to know if this is the dev carrier board and if the power supply is the default it comes with.

3

I am currently unsure about whether this is the dev carrier board or not, however I know that the adapter is not default. I am checking with a superior about this.

4

If you go here there is a picture. The developer kit carrier board is tiny, and most of the picture near the top is the module:
[url]Buy the Latest Jetson Products | NVIDIA Developer

However, if you look close there is a PCIe slot on one side, plus a 40-pin header on the other side (the header has a micro-USB connector on one end, and a USB-C connector on the other end). This would be the dev kit (the module is basically the heat sink, and the base it sits on is the carrier board…carrier board is much smaller than the heat sink).

Dev kits come with a power adapter. The power unit you are using might not be an issue, but if you have one of the original power bricks to test with the result of switching to this would be useful information.

5

It is definitely a dev kit. I am unable to ask about the original adapter currently as it is after 17:00 on a Friday here. I will try to chase it down Monday and follow up with results.

6

Further Testing with an adapter designed for the dev kit has yielded the same results.

7

You may have an actual hardware failure, but some of the earlier message errors shown are not actually a problem (for example you could see errors related to secure boot if secure boot isn’t enabled). Would it be possible to try to flash with SDK Manager 4.2 (essentially the replacement to JetPack)? You would disable all of the software install steps and just flash.

Installer: [url]https://developer.nvidia.com/embedded/dlc/nv-sdk-manager[/url]
Instructions 1 (Download/Run): [url]http://docs.nvidia.com/sdk-manager/download-run-sdkm/index.html[/url]
Instructions 2 (Install Software to Jetson): [url]http://docs.nvidia.com/sdk-manager/install-with-sdkm-jetson/index.html[/url]

1 Like
8

I began this troubleshooting with the SDK which would end part of the way through flashing the OS. I then Switched to the command-line method of setup to gain more insight into the issue. I would assume there is a hardware issue as well.

9

If you could post a log of command line flash perhaps the issue could be narrowed down (RMA might still be required, but it would better to be sure before going through the effort). For a command line method with logging example:

sudo ./flash.sh jetson-xavier mmcblk0p1 <i><b>2>&1 | gawk '{gsub("[0-9][0-9]+[/][0-9[0-9]+ bytes sent..",".");print}' | tee log.txt</b></i>

The “gawk” part removes some of the command line progress bar from the log, but could be skipped.