I can`t install Jetson OS from sdk or terminal for Jetson Nano Model: 3450

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

Hello, I can`t install soft from sdk or terminal for Jetson Nano Model: 3450. This is Jetson Nano 2GB developer kit.

What I did?
I tried 3 variants of installation and all of them failed.

VARIANT_1. Install Jetson OS via SDK I had empty HDD, on which I have already installed Ubuntu 18.04. After that I found this manual https://www.waveshare.com/wiki/JETSON-NANO-DEV-KIT-MANUAL#System_Installation and installed SDK.
After that I prepared hardware configuration:

  1. Use jumper caps or Dupont wires to short-circuit the FC REC and GND pins, as shown in the figure below, at the bottom of the core board.
  2. Connect the DC power supply to the circular power port and wait a moment.
  3. Connect the Micro USB port of the Jetson Nano to the Ubuntu host with a USB cable (note that it is a data cable).
    I opened the Ubuntu computer terminal and run the SDK Manager to open the software.
    I tried to install Jetpack 4.6.3, 4.6.2, 4.6.1 , but scenario are the same for all of these versions.
    SDK tried to install Jetson OS and when he installed 99.8% of Jetson OS, he wrote such message:
    image
    image1376×910 186 KB

    I pushed button continue 3 times. SDK asked me every 15 minutes. But when you push NO _> it will write error in termial:
14:58:05 INFO: Flash Jetson Nano - flash: [ 3.1145 ] Saved platform info in storage_info.bin
17:03:54 DEBUG: running command < true >
17:03:54 DEBUG: running command < true >
17:03:54 INFO: command finished successfully
17:03:54 DEBUG: running command < ps aux | grep NV_L4T_FLASH_NANO_WITH_OS_IMAGE_COMP | grep -v grep | awk '{print $2}' | xargs kill -9 >
17:03:54 INFO: exec_command: ps aux | grep NV_L4T_FLASH_NANO_WITH_OS_IMAGE_COMP | grep -v grep | awk '{print $2}' | xargs kill -9
17:03:54 ERROR: command terminated with error

VARIANT_2. Directly Download Jetpack and install it from terminal of your host machine.

  1. I downloaded packages from these links:
    https://developer.nvidia.com/embedded/l4t/r32_release_v7.2/t210/jetson-210_linux_r32.7.2_aarch64.tbz2
    https://developer.nvidia.com/embedded/l4t/r32_release_v7.2/t210/tegra_linux_sample-root-filesystem_r32.7.2_aarch64.tbz2
  2. I created needful packages and ran such commands:
sudo ./flash.sh jetson-nano-emmc mmcblk0p1

40 minutes later I saw the same message in logs:

[   0.5983 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml
[   0.5993 ] BR_CID: 0x32101001644568012400000007000540
[   0.6266 ] RCM version 0X210001
[   0.6750 ] Boot Rom communication completed
[   1.6826 ] 
[   1.6827 ] Sending BCTs
[   1.6870 ] tegrarcm --download bct P3448_A00_lpddr4_204Mhz_P987.bct
[   1.6904 ] Applet version 00.01.0000
[   1.7645 ] Sending bct
[   1.7646 ] [................................................] 100%
[   1.9893 ] 
[   1.9950 ] tegrahost --chip 0x21 --align cboot.bin
[   1.9984 ] 
[   2.0062 ] tegrahost --magicid EBT --appendsigheader cboot.bin cboot.bin_blheader
[   2.0157 ] 
[   2.0238 ] tegrasign --key None --list cboot.bin_list.xml
[   2.0276 ] Assuming zero filled SBK key
[   2.0596 ] 
[   2.0626 ] tegrahost --updatesigheader cboot.bin_blheader.encrypt cboot.bin_blheader.hash zerosbk
[   2.0648 ] 
[   2.0682 ] tegrahost --chip 0x21 --align tegra210-p3448-0000-p3449-0000-b00.dtb
[   2.0696 ] 
[   2.0720 ] tegrahost --magicid DTB --appendsigheader tegra210-p3448-0000-p3449-0000-b00.dtb tegra210-p3448-0000-p3449-0000-b00.dtb_blheader
[   2.0743 ] 
[   2.0770 ] tegrasign --key None --list tegra210-p3448-0000-p3449-0000-b00.dtb_list.xml
[   2.0782 ] Assuming zero filled SBK key
[   2.0867 ] 
[   2.0913 ] tegrahost --updatesigheader tegra210-p3448-0000-p3449-0000-b00.dtb_blheader.encrypt tegra210-p3448-0000-p3449-0000-b00.dtb_blheader.hash zerosbk
[   2.0935 ] 
[   2.0941 ] Sending bootloader and pre-requisite binaries
[   2.0954 ] tegrarcm --download ebt cboot.bin.encrypt 0 0 --download rp1 tegra210-p3448-0000-p3449-0000-b00.dtb.encrypt 0
[   2.0965 ] Applet version 00.01.0000
[   2.1710 ] Sending ebt
[   2.1713 ] [................................................] 100%
[   2.2783 ] Sending rp1
[   2.2801 ] [................................................] 100%
[   2.3363 ] 
[   2.3419 ] tegrarcm --boot recovery
[   2.3469 ] Applet version 00.01.0000
[   2.4251 ] 
[   2.4253 ] Retrieving storage infomation
[   2.4303 ] tegrarcm --oem platformdetails storage storage_info.bin
[   2.4335 ] Applet is not running on device. Continue with Bootloader
[   2.9739 ] 
[   3.0044 ] tegradevflash --oem platformdetails storage storage_info.bin
[   3.0091 ] Cboot version 00.01.0000
[   3.0530 ] Saved platform info in storage_info.bin

I waited 1 hour 30 minutes and after that I declined this process.

VARIANT_3. Write image to microSD card and install software from it.
I formatted card and wrote image, as it described in this manual : Get Started With Jetson Nano Developer Kit | NVIDIA Developer
I connected keyboard, mouse and monitor, but I saw only logo of NVIDIA, no actions and no reactions from board, when you push keyboard buttons.
What we should see in first boot session we can read here: Get Started With Jetson Nano Developer Kit | NVIDIA Developer
Also such steps we can see here: https://www.youtube.com/watch?v=uvU8AXY1170.

But as a result: when I switch on Jetson Nano, I saw only NVIDIA logo on monitor. Thats all. What to do I dont know. Please, help me to install Jetson sotware on board. Thanks.

3

Hi,

You should use jetson-nano-2gb-devkit as the config file here.

4

Hi, Dave !

For 4GB devkit will be the same command?
sudo ./flash.sh jetson-nano-4gb-devkit

5

jetson-nano-devkit for modules with an SD card slot,
jetson-nano-devkit-emmc for modules with eMMC.

6

Sorry, but I can`t understand what to write in this command:

 sudo ./flash.sh jetson-nano-devkit

Usage: sudo ./flash.sh [options] <target_board> <rootdev>
  Where,
	target board: Valid target board name.
	rootdev: Proper root device.

Here, we have 2 arguments sudo ./flash.sh [options] <target_board> <rootdev>:
<target_board> and .

How to set <rootdev> you have already answered in message above:

jetson-nano-devkit for modules with an SD card slot,
jetson-nano-devkit-emmc for modules with eMMC.

What about <target_board> ?
We have 2 board:

  • one board with card slot, her Model is P3450
  • second board with crystal Model P3448 180-13448-DAAA-B01

image
image1920×2560 481 KB

image
image540×720 54 KB

7

You just did it here…
mmcblk0p1 was right, but change jetson-nano-emmc with the correct name.

8

Also I have question about pin J48. This 2 pins can switch on board from which connector motherboard will take a power. So, question: should J48 be pinned, when we have recovery mode for our command sudo ./flash.sh jetson-nano-devkit mmcblk0p1 ?

9

It depends on which type of power supply you are using, which I don’t know…

10

Output 5 Volts, 4A =)

11

Then you should place a jumper across J48 in order to use the 5V 4A adapter.

12

Thank you for your patience.

  1. So, I formatted card and wrote image, as it described in this manual : Get Started With Jetson Nano Developer Kit | NVIDIA Developer
  2. I pinned J38 + I pinned recovery mode pins.
    In terminal of host machine with Ubuntu 18.04 I ran command: ~/sources_nano/Linux_for_Tegra$ sudo ./flash.sh jetson-nano-devkit mmcblk0p1

25 minutes later I got result:

[  89.8591 ] Writing partition BPF with sc7entry-firmware.bin.encrypt
[  90.1198 ] [................................................] 100%
[  90.1299 ] Writing partition TOS with tos-mon-only.img.encrypt
[  90.3919 ] [................................................] 100%
[  90.4036 ] Writing partition DTB with kernel_tegra210-p3448-0000-p3449-0000-b00.dtb.encrypt
[  93.8389 ] [................................................] 100%
[  93.8567 ] Writing partition LNX with boot.img.encrypt
[ 108.2713 ] [................................................] 100%
[ 108.3043 ] Warning: EKS partition magic header mismatch!
[ 148.1016 ] Writing partition EKS with eks.img
[ 148.1023 ] [................................................] 100%
[ 148.1125 ] Writing partition BMP with bmp.blob
[ 148.3746 ] [................................................] 100%
[ 148.3911 ] Writing partition RP4 with rp4.blob
[ 157.4375 ] [................................................] 100%
[ 157.4748 ] Writing partition VER_b with qspi_bootblob_ver.txt
[ 165.3022 ] [................................................] 100%
[ 165.3144 ] Writing partition VER with qspi_bootblob_ver.txt
[ 165.5765 ] [................................................] 100%
[ 165.5867 ] Writing partition APP with system.img
[ 165.8485 ] [................................................] 100%
[ 891.0319 ] 
[ 891.0371 ] tegradevflash --write BCT P3448_A00_lpddr4_204Mhz_P987.bct
[ 891.0403 ] Cboot version 00.01.0000
[ 891.0750 ] Writing partition BCT with P3448_A00_lpddr4_204Mhz_P987.bct
[ 891.0774 ] [................................................] 100%
[ 897.7308 ] 
[ 897.7310 ] Flashing completed

[ 897.7312 ] Coldbooting the device
[ 897.7360 ] tegradevflash --reboot coldboot
[ 897.7373 ] Cboot version 00.01.0000
[ 897.7672 ] 
*** The target t210ref has been flashed successfully. ***
Reset the board to boot from internal eMMC.

What we will do with [ 108.3043 ] Warning: EKS partition magic header mismatch!?

13

Does the device boot up normally?
I think it doesn’t matter if it’s just warning instead of error.

14

Yes the device boot up normally. I will install Ubuntu. After that I need pytorch, opencv and CUDA, so I will ask few questions later =)

15

Hi!
I am trying to install CUDA via this manual: Installing CUDA on Nvidia Jetson Nano - JFrog Connect

But on command: sudo tar -xjf cuda-repo-ubuntu1804-11-0-local_11.0.2-450.51.05-1_arm64.deb
I got an error:

 sudo tar -xjf cuda-repo-ubuntu1804-11-0-local_11.0.2-450.51.05-1_arm64.deb
bzip2: (stdin) is not a bzip2 file.
tar: Child returned status 2
tar: Error is not recoverable: exiting now

PC downloaded all file via command from manual :

 sudo dpkg -i cuda-repo-ubuntu1804-11-0-local_11.0.2-450.51.05-1_arm64.deb
(Reading database ... 190197 files and directories currently installed.)
Preparing to unpack cuda-repo-ubuntu1804-11-0-local_11.0.2-450.51.05-1_arm64.deb ...
Unpacking cuda-repo-ubuntu1804-11-0-local (11.0.2-450.51.05-1) ...
dpkg-deb (subprocess): cannot copy archive member from 'cuda-repo-ubuntu1804-11-0-local_11.0.2-450.51.05-1_arm64.deb' to decompressor pipe: unexpected end of file or stream
dpkg-deb (subprocess): decompressing archive member: lzma error: unexpected end of input
dpkg-deb: error: <decompress> subprocess returned error exit status 2
dpkg: error processing archive cuda-repo-ubuntu1804-11-0-local_11.0.2-450.51.05-1_arm64.deb (--install):
 cannot copy extracted data for './var/cuda-repo-ubuntu1804-11-0-local/libcufft-dev-11-0_10.2.0.218-1_arm64.deb' to '/var/cuda-repo-ubuntu1804-11-0-local/libcufft-dev-11-0_10.2.0.218-1_arm64.deb.dpkg-new': unexpected end of file or stream
Errors were encountered while processing:
 cuda-repo-ubuntu1804-11-0-local_11.0.2-450.51.05-1_arm64.deb

I tried to download twice, but id didn’t help.

16

Please file a new topic if it’s not related to your original issue.

1 Like
17

Ok. I created new topic here: Can`t Install CUDA from official manual

19

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