Nano failed to boot

Robotics & Edge Computing Jetson & Embedded Systems Jetson Nano
1

We got few new Nanos (ex:SN:1422419009757) and the Nano all failed to boot.

As We used a SDcard which worked well on our previous Nano board. (ex:SN:0421119030681) to boot,
and got boot fail.

However, the Nano worked well after be re-flashed by using SDKManager.

Is it normal?

Our previous Nanos do work with different SDcard which is flahed by the other Nano.

Attach the log.

Thank you for any advice,
Nano_r32_2_1_boot_fail_r32_2_1.txt (2.67 KB)

2

I saw this error.

[0000.272] Invalid GPT Partition

Looks the GPT parition is corrupted.

Could you also check your card with commands like sudo gdisk /dev/sdb ?

3

Hi WayneWWW,

Thank you for your support.
Below is the message of “sudo gdisk /dev/sdb.”
It does show reading error.
However, this SDcard was flashed by Sdkmanager 0.9.14 on Nano.

nvn2@nvn2-desktop:~$ sudo gdisk /dev/sdb
[sudo] password for nvn2:
GPT fdisk (gdisk) version 1.0.3

Problem opening /dev/sdb for reading! Error is 2.
The specified file does not exist!

Thanks,

4

Hi HuiW,

Please correct the device name to the specific name for your sdcard…

sdb is just a random device name.

5

Hi WayneWWWW,

Could you address more about “correct the device name to the specific name for your sdcard”?

What should we do after doing SDKManager flashed to make the SDcard work on a new Nano?

Thank you,

6

Once the error occurred, please put this sdcard to your x86 host and run gdisk command.

Also, please read the error you pasted in #3.
Your error indicates sdb does not exist, so please confirm if your sdcard is sdb or not. If not, please use the right name and run gdisk command again.

Problem opening /dev/sdb for reading! Error is 2.
The specified file does not exist!
7

Below is the message of run gdisk.
Is this what you want to check?

$ sudo gdisk /dev/sdc
GPT fdisk (gdisk) version 1.0.1

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): v

No problems found. 1748497 free sectors (853.8 MiB) available in 1
segments, the largest of which is 1748497 (853.8 MiB) in size.

Thank you,

8

Hi HuiW,

The exact steps to check with gdisk is as below

  1. Sdcard flashed with sdkmanager.
  2. Use gdisk to check the sdcard → should have valid GPT partition
  3. Move sdcard to first Nano device → should boot normally.
  4. Unplug the sdcard and check with gdisk again.
  5. Put sdcard to second nano device → cannot boot
  6. Use gdisk on sdcard again and see if GPT is corrupted.
9

Hi WayneWWW,

As the test results we got, the same SDcard has different behavior on a new Nano device or a used Nano device.

Here are the steps we did.

  1. Sdcard flashed on Nano with sdkmanager.
  2. Boot normally — GPT not present.
  3. Unplug the sdcard and put the sdcard to a new nano device → cannot boot
  4. Use a x86 system to check gdisk on sdcard again → GPT: present

However, if the step 3 replaced a used Nano:
3. Unplug the sdcard and put the sdcard to a used nano device → boot successfully.
4. Use gdisk on sdcard again → GPT not present. (see attached.)

On a x86 system:
sudo gdisk /dev/sdb
GPT fdisk (gdisk) version 1.0.1

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): v

No problems found. 1748497 free sectors (853.8 MiB) available in 1
segments, the largest of which is 1748497 (853.8 MiB) in size.

nvn2_boot_ok_noGDP.jpg
nvn2_boot_ok_noGDP.jpg1920×1200 681 KB

nvn2_boot_ok_noGDP.jpg
nvn2_boot_ok_noGDP.jpg1920×1200 689 KB

10

Hi HuiW,

We cannot repro this issue with two Nano devices. Also, gpt partition always exists after each boot.

Below part is the one that differs from normal boot.

[0000.266] Non secure mode, and RB not enabled.
[0000.272] Invalid GPT Partition
[0000.287] Using BFS PT to query partitions 
[0000.291] failed to load NvTbootTbootCpu from (2:0)
[0000.296] re-load NvTbootTbootCpu from (4:0)
[0000.471] Csd NumOfBlocks=31116288
[0000.486] Using GPT Primary to query partitions
[0000.494] Loading Tboot-CPU binary
[0000.871] Verifying TBC in OdmNonSecureSBK mode
[0000.881] Bootloader load address is 0xa0000000, entry address is 0xa0000258
[0000.888] Bootloader downloaded successfully.
[0000.892] Downloaded Tboot-CPU binary to 0xa0000258

Did you also try other sdcard?

11

Hi WayneWWW,

The issue can only be duplicated with new Nano devices which are new purchased.
Unfortunately, we tested 4~6 sdcards and all got the same error result.

Thank you,

12

Hi HuiW,

I still want to try other test to narrow down this issue.

  1. Could you try to use sdkmanager rel-32.1 and see if issue can be reproduced?
  2. Also, how about using etcher with pre-built sdcard image?
13

Hi HuiW,

Thank you for your feedback, we have logged an internal bug to track this fix. It is targeted for 1H 2020.
Before that, please be sure to flash the device with the SDKM, then boot first.

14

Hi Kayccc,

Thank you for your update.
I appreciate you could keep us posted.
As you have the root caused or any update.

Thanks you,