Jetson Nano Dev Kit w/B01 carrier - no console output and will not boot

I have a Jetson Nano Dev Kit on the B01 carrier. The current board will not boot - no Nvidia logo on HDMI, no HDMI output at all, no serial console output at all, however can be put into recovery mode. This kit booted fine before and no updates to the SD card - so it was basically turned off and then a week later turned on for more development.

The SDK manager sees it when it is in recovery mode - otherwise there is no indication that it has booted (no network traffic or even LEDs blinking due to traffic). The power supply has swapped from external power to USB power using a powered hub that supplies more than 20W.

dmesg output when I plug into my host in recovery mode:
[523045.537031] usb 1-4.4: new high-speed USB device number 16 using xhci_hcd
[523045.638137] usb 1-4.4: New USB device found, idVendor=0955, idProduct=7f21, bcdDevice= 1.02
[523045.638150] usb 1-4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[523045.638156] usb 1-4.4: Product: APX
[523045.638160] usb 1-4.4: Manufacturer: NVIDIA Corp.

Has anyone had this issue before where it looks like it is basically a dead board? I wouldn’t even debug this but rather get another board if there were boards available.

What is going on after you put the board into recovery mode? Why the story just stopped here?

After putting the board into recovery mode, you should let sdkmanager flash it.

SDK Manager always fails on trying to flash.

06:56:34 ERROR: Flash Jetson Nano - flash: — Parsing board ID (ERROR: calculated CRC8 0x34 != stored CRC8 0x75) succeeded.
06:56:34 ERROR: Flash Jetson Nano - flash: — Parsing board version (ERROR: calculated CRC8 0x34 != stored CRC8 0x75) succeeded.
06:56:34 ERROR: Flash Jetson Nano - flash: — Parsing board SKU (ERROR: calculated CRC8 0x34 != stored CRC8 0x75) succeeded.
06:56:34 ERROR: Flash Jetson Nano - flash: — Parsing board REV (ERROR: calculated CRC8 0x34 != stored CRC8 0x75) succeeded.
06:56:34 ERROR: Flash Jetson Nano - flash: — Parsing board ID (ERROR: calculated CRC8 0x34 != stored CRC8 0x75) succeeded.
06:56:34 ERROR: Flash Jetson Nano - flash: — Parsing board version (ERROR: calculated CRC8 0x34 != stored CRC8 0x75) succeeded.
06:56:34 ERROR: Flash Jetson Nano - flash: — Parsing board SKU (ERROR: calculated CRC8 0x34 != stored CRC8 0x75) succeeded.
06:56:34 ERROR: Flash Jetson Nano - flash: — Parsing board REV (ERROR: calculated CRC8 0x34 != stored CRC8 0x75) succeeded.
06:56:34 ERROR: Flash Jetson Nano - flash: Error: Target board not found.
06:56:34 ERROR: Flash Jetson Nano - flash: command terminated with error
06:56:34 SUMMARY: Flash Jetson Nano - flash: First Error: Installation failed.

Oh ok. Your issue is duplicated as this one. Please follow the steps here to flash the board and recover the eeprom content.

Followed the steps exactly - using the same values in step 5 that were added for my Nano dev kit. Modified file p3449-0000+p3448-0002.conf and get this missing dtb file error.

sudo ./flash.sh jetson-nano-emmc mmcblk0p1
#########################################################

L4T BSP Information:

R32 , REVISION: 6.1

#########################################################

Target Board Information:

Name: jetson-nano-emmc, Board Family: t210ref, SoC: Tegra 210,

OpMode: production, Boot Authentication: ,

Disk encryption: disabled ,

#########################################################
Board ID(“3448”) version(“400”)
Error: missing dtbfile (/home/jay/Downloads/nvidia/Jetson-210_Linux_R32.6.1_aarch64/Linux_for_Tegra/kernel/dtb/tegra210-p3448-“0002”-p3449-0000-b00.dtb).

I don’t know if you are using sdcard module or emmc module. The steps provided to you is for emmc.

If you are using sdcard, you should modify the corresponding conf file. p3448-0000 is for sdcard, p3448-0002 is for emmc.

Removed the “” around the sections to update in 3449-0000+p3448-0002.conf. Flashing failed. See attached log file.
flash_log_failure.txt (12.0 KB)

Also, you don’t need to prepare “Jetson-210_Linux_R32.6.1_aarch64” by yourself. SDKM already downloaded that to your host under path ~/nvidia.

If you see some files are missing, it probably due to your manual download.

flash_log_failure_sdcard.txt (9.0 KB)

I’m using the SDCard. So modifying p3449-0000+p3448-0000-qspi-sd.conf instead with same values used per other link (and without quotes)

sudo ./flash.sh jetson-nano- mmcblk1p1 also fails. See attached.

Hi,

What did you modify exactly? The log says you are still flashing tegra210-p3448-0002-p3449-0000-b00 device tree to the board.

As I said, p3448-0002 is for the emmc module. The board sku you should provide is 0000 but not 0002.

That was my mistake. Here’s the corrected version and the SKU correctly changed to 0000 for the p3449-0000+3448-0000-qspi-sd.conf file. See the output and you can see that the right dtb is copying this time however, same failure.

flash_log_failure_sdcard_2ndtry.txt (9.1 KB)

  1. What is the content in your “board_config_p3448.xml” ?

  2. Could you just list out a diff of what you have added to each file?

Here is the sdcard module case that happened and resolved on another user.

Changed per the note for sd card. Failed again and attached log.

for board_config_p3448.xml the change is as follows:

flash_log_failure_sdcard_3rdtry.txt (10.0 KB)

jay@spgubuntu:~/Downloads/nvidia/Jetson-210_Linux_R32.6.1_aarch64/Linux_for_Tegra$ diff p3448-0000.conf.common ~/Desktop/p3448-0000.conf.common
174d173
< BCFFILE=“bootloader/${target_board}/cfg/board_config_p3448.xml”;

for p3449-0000+p3448-0000-qspi-sd.conf

jay@spgubuntu:~/Downloads/nvidia/Jetson-210_Linux_R32.6.1_aarch64/Linux_for_Tegra$ diff p3449-0000+p3448-0000-qspi-sd.conf ~/Desktop/p3449-0000+p3448-0000-qspi-sd.conf
29,33d28
< BOARDID=3448;
< FAB=000;
< BOARDSKU=0000;
< BOARDREV=70;
<

I mean what is inside your " board_config_p3448.xml"…

It is untouched. I’ve attached it.
board_config_p3448.xml (261 Bytes)

Could you give FAB=400 instead of 000?

Same failure with FAB=400.

Is there any sticker on your module? If so, please take a picture.

No sticker on module. Here’s a picture anyways.
image