No, Jetson nano is quite old that only has ubuntu 18.04 to support the flash of it.
There is a wifi driver installation problem occuring in ubuntu 18.04 . So, I am not able to start the process of flaashing again . Could you give me its solution or is there any other solution to do that
No, there is no other method.
Your system got crash from bootloader part. You must use a native Ubuntu 18.04 host to flash your Jetson.
This is actually a very basic operations to every Jetson device.
If the file Linux_for_tegra found then what is the next initial step after it
Put your board into recovery mode by using the jumper.
Then run
sudo ./flash.sh jetson-nano-2gb-devkit mmcblk0p1
I guess your board is a Jetson Nano 2GB board as your previous screenshot shows.
If it is not, please let me know.
it is 4gb
I read the documents and come to the conclusion that flashing through linux_with_tegra does not requires sdk manager. Means either done through sdk manager or with L4T
Sdkmanager has two parts to install here
- BSP package.
- SDK
BSP package means the Linux_for_Tegra package.
SDK means the CUDA/TensorRT ..etc software package.
You are facing a basic OS issue so only need to use BSP package (Linux_for_Tegra) to flash the board first.
Sdkmanager and manual command could flash them too.
It looks like your sdkmanager fails to run and you could not provide us the exact log.
Thus, I suggested you to try flash.sh command directly. If it fails, then you could share me the log for us to check. That is more easier to share.
Hope you understand what is my purpose here.
If that is 4gb module, then please use
sudo ./flash.sh jetson-nano-devkit mmcblk0p1
to flash first.
If it fails, try
sudo ./flash.sh jetson-nano-devkit-emmc mmcblk0p1
jetson-210_linux_r32.7.6_aarch64.tbz2
#Installing driver package
tegra_linux_sample-root-filesystem_r32.7.6_aarch64.tbz2
#For root file system
sudo apt update
sudo apt install -y qemu-user-static
#To install host dependency
mkdir ~/jetson
cd ~/jetson
tar xf jetson-210_linux_r32.7.6_aarch64.tbz2
cd Linux_for_Tegra
#Extract BSP (LINUX FOR TEGRA)
sudo tar xf ../tegra_linux_sample-root-filesystem_r32.7.6_aarch64.tbz2 -C rootfs
#Extract Rootfile system
sudo ./apply_binaries.sh
#Apply NVIDIA Binaries
PULL JETSON IN RECOVERY MODE
- Power OFF Jetson Nano
- Short REC + GND pins
- Connect micro-USB → Host PC
- Power ON Jetson Nano
Flash it
sudo ./flash.sh jetson-nano-devkit mmcblk0p1
If it fails, try
sudo ./flash.sh jetson-nano-devkit-emmc mmcblk0p1
Is this all correct order or anything wrong
Yes, those are correct.
I just want to clarify all this again.
Sdkmanager should already help you download and prepare everything. Only the flash command didn’t get executed.
Thus, all these commands you mentioned are not needed. Sdkmanager will directly prepare these things under your ~/nvidia directory.
jetson-210_linux_r32.7.6_aarch64.tbz2
#Installing driver package
tegra_linux_sample-root-filesystem_r32.7.6_aarch64.tbz2
#For root file system
sudo apt update
sudo apt install -y qemu-user-static
#To install host dependency
mkdir ~/jetson
cd ~/jetson
tar xf jetson-210_linux_r32.7.6_aarch64.tbz2
cd Linux_for_Tegra
#Extract BSP (LINUX FOR TEGRA)
sudo tar xf ../tegra_linux_sample-root-filesystem_r32.7.6_aarch64.tbz2 -C rootfs
#Extract Rootfile system
sudo ./apply_binaries.sh
#Apply NVIDIA Binaries
PULL JETSON IN RECOVERY MODE
1. Power OFF Jetson Nano
2. Short **REC + GND pins**
3. Connect **micro-USB → Host PC**
4. Power **ON** Jetson Nano
If you use the package downloaded by sdkmanager, then you only need to run flash.sh command. No need to do anything else.
Can I run YOLO 11 in Nano jetson developer kit?
Please just focus on original topic.
If you could flash the board and no problem to flash now, then please file a new topic for other questions.
I have done all the steps and flashing is not successful and during boot run time it is again stuck in nvidia logo
sudo ./flash.sh jetson-nano-devkit mmcblk0p1
Is this command correct for flashing jetson nano after put in recovery mode
just want to clarify. if the flash process didn’t succeed, then the situation on your Jetson side is not changed. You just didn’t do anything to your Jetson so situation won’t be different.
please share full text log instead of doing screenshot. Take this as common sense…
please copy all the text into a log file and then attach that log file…
I don’t want to see you share any picture for a log…
###############################################################################
L4T BSP Information:
R32 , REVISION: 7.6
###############################################################################
Target Board Information:
Name: jetson-nano-devkit, Board Family: t210ref, SoC: Tegra 210,
OpMode: production, Boot Authentication: ,
Disk encryption: disabled ,
###############################################################################
./tegraflash.py --chip 0x21 --applet “/home/akshat/jetson/Linux_for_Tegra/bootloader/nvtboot_recovery.bin” --skipuid --cmd “dump eeprom boardinfo cvm.bin”
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
[ 0.0025 ] Generating RCM messages
[ 0.0054 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm /home/akshat/jetson/Linux_for_Tegra/bootloader/nvtboot_recovery.bin 0 0
[ 0.0069 ] RCM 0 is saved as rcm_0.rcm
[ 0.0077 ] RCM 1 is saved as rcm_1.rcm
[ 0.0077 ] List of rcm files are saved in rcm_list.xml
[ 0.0077 ]
[ 0.0078 ] Signing RCM messages
[ 0.0114 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0128 ] Assuming zero filled SBK key
[ 0.0242 ]
[ 0.0242 ] Copying signature to RCM mesages
[ 0.0279 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[ 0.0304 ]
[ 0.0305 ] Boot Rom communication
[ 0.0334 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml --skipuid
[ 0.0349 ] RCM version 0X210001
[ 0.0793 ] Boot Rom communication completed
[ 1.0893 ]
[ 1.0894 ] dump EEPROM info
[ 1.0930 ] tegrarcm --oem platformdetails eeprom /home/akshat/jetson/Linux_for_Tegra/bootloader/cvm.bin
[ 1.0948 ] Applet version 00.01.0000
[ 1.1128 ] Saved platform info in /home/akshat/jetson/Linux_for_Tegra/bootloader/cvm.bin
[ 1.1903 ]
[ 1.1934 ] tegrarcm --reboot recovery
[ 1.1949 ] Applet version 00.01.0000
[ 1.2132 ]
Board ID(3448) version(402)
copying bctfile(/home/akshat/jetson/Linux_for_Tegra/bootloader/t210ref/BCT/P3448_A00_lpddr4_204Mhz_P987.cfg)… done.
copying bootloader(/home/akshat/jetson/Linux_for_Tegra/bootloader/t210ref/cboot.bin)… done.
copying initrd(/home/akshat/jetson/Linux_for_Tegra/bootloader/l4t_initrd.img)… done.
Making Boot image… done.
Existing sosfile(/home/akshat/jetson/Linux_for_Tegra/bootloader/nvtboot_recovery.bin) reused.
copying tegraboot(/home/akshat/jetson/Linux_for_Tegra/bootloader/t210ref/nvtboot.bin)… done.
copying cpu_bootloader(/home/akshat/jetson/Linux_for_Tegra/bootloader/t210ref/cboot.bin)… done.
copying bpffile(/home/akshat/jetson/Linux_for_Tegra/bootloader/t210ref/sc7entry-firmware.bin)… done.
copying wb0boot(/home/akshat/jetson/Linux_for_Tegra/bootloader/t210ref/warmboot.bin)… done.
Existing tosfile(/home/akshat/jetson/Linux_for_Tegra/bootloader/tos-mon-only.img) reused.
.copying tbcdtbfile(/home/akshat/jetson/Linux_for_Tegra/kernel/dtb/tegra210-p3448-0002-p3449-0000-b00.dtb)… done.
ERROR xmllint not found! To install - please run: “sudo apt-get install libxml2-utils”
(END)
as the error log already tell you the missing package. Please install it on your host..
