Not sure what you mean by āboot screen has to be erasedā. Thereās no platform-implementation info in the BMP splash, if thatās what you are referring to - itās just a NVIDIA logo BMP. You can disable it by removing the BMP partition from your flash*.xml file, and removing the bmp.blob from Linux_for_Tegra/bootloader.
If you are wanting to dispense with any boot spew to the UART, there are topics on how to do that that on this board. You can disable some of the bootloader spew, but not all w/o source. And you can also disable kernel spew with the āquietā cmd-line arg IIRC.
Thanks for reply. I canāt find bmp.blob and no Linux_for_Tegra/bootloader path existed on jetson nano, whose system is flashed in SD card. Iām confused about you said. Maybe you mean TX2 or Xavier?
I use sdkmanager to flash nano, I remove bmp.blob and every files that contain ābmp.blobā: ./JetPack_4.2.1_Linux_GA_P3448/Linux_for_Tegra/create-jetson-nano-sd-card-image.sh: āpart_num=12;part_name=BMP;part_size=81920;part_file=bmp.blobā
./JetPack_4.2.1_Linux_GA_P3448/Linux_for_Tegra/bootloader/l4t_bup_gen.func: āpart_name=BMP; part_type=bl,porg_sd; part_spec=${_common_spec}; part_file=bmp.blobā
./JetPack_4.2.1_Linux_GA_P3448/Linux_for_Tegra/bootloader/t210ref/cfg/flash_l4t_t214_emmc.xml: bmp.blob
./JetPack_4.2.1_Linux_GA_P3448/Linux_for_Tegra/bootloader/t210ref/cfg/flash_l4t_t210_spi_sd_p3448.xml: bmp.blob
./JetPack_4.2.1_Linux_GA_P3448/Linux_for_Tegra/bootloader/t210ref/cfg/gnu_linux_tegraboot_emmc_full.xml: bmp.blob
./JetPack_4.2.1_Linux_GA_P3448/Linux_for_Tegra/bootloader/t210ref/cfg/flash_l4t_t214_spi.xml: bmp.blob
./JetPack_4.2.1_Linux_GA_P3448/Linux_for_Tegra/bootloader/t210ref/cfg/flash_l4t_t210_emmc_p3448.xml: bmp.blob [i][/i]
But NVIDIA logo still shows on boot screen, Iām crazyā¦
You only need remove the BMP partition from flash_l4t_t210_spi_sd_p3448.xml for Nano. Remove the entire section, starting with 'partition name=āBMPā and ending with /partition:
You can also delete the bmp.blob binary from your Linux_for_tegra/bootloader subdir, but that isnāt strictly necessary.
Then reflash your Nano (put it into recovery mode first) via:
sudo ./flash.sh jetson-nano-qspi-sd mmcblk0p1
Theoretically, you should also be able to reflash w/SDK manager, but I donāt use that on a daily basis, so Iād prefer if you use the above command. And note that the above is all done on your host system, not on the Nano itself.
Thanks for reply. Unfortunately, it doesnāt work, logo is still here. My steps are:
1, run sdkmanager, if Iāve put nano into recovery mode, flash will run automatically, scripts canāt be modified, so I disconnect nano, then flash is pending.
2, Modify flash_l4t_t210_spi_sd_p3448.xml as you said, bmp.blob is removed also, then put nano into recovery mode and perform sudo ./flash.sh jetson-nano-qspi-sd mmcblk0p1.
Iām nearby the edge of crazy, please help meā¦
2, Modify flash_l4t_t210_spi_sd_p3448.xml as you said, bmp.blob is removed also, then put nano into recovery mode and perform sudo ./flash.sh jetson-nano-qspi-sd mmcblk0p1.
This should work. Could you confirm there is no bmp.blob under bootloader and the partition does not exist?
1, run sdkmanager, if Iāve put nano into recovery mode, flash will run automatically, scripts canāt be modified, so I disconnect nano, then flash is pending.
Please do not use sdkmanager at this moment. Otherwise it may reinstall the missing file.
Thanks for reply. It canāt work. I can confirm that actions needed were done:
nvidia@nvidia-Precision-Tower-3620:~/nvidia/nvidia_sdk/JetPack_4.2.1_Linux_GA_P3448$ sudo find . -name "bmp.blob"
nvidia@nvidia-Precision-Tower-3620:~/nvidia/nvidia_sdk/JetPack_4.2.1_Linux_GA_P3448$ sudo find . -name "flash_l4t_t210_spi_sd_p3448.xml" | grep "bmp"
nvidia@nvidia-Precision-Tower-3620:~/nvidia/nvidia_sdk/JetPack_4.2.1_Linux_GA_P3448$ cd Linux_for_Tegra/
nvidia@nvidia-Precision-Tower-3620:~/nvidia/nvidia_sdk/JetPack_4.2.1_Linux_GA_P3448/Linux_for_Tegra$ sudo ./flash.sh jetson-nano-qspi-sd mmcblk0p1
###############################################################################
# L4T BSP Information:
# R32 , REVISION: 2.0
###############################################################################
# Target Board Information:
# Name: jetson-nano-qspi-sd, Board Family: t210ref, SoC: Tegra 210,
# OpMode: production, Boot Authentication: ,
###############################################################################
./tegraflash.py --chip 0x21 --applet "/home/nvidia/nvidia/nvidia_sdk/JetPack_4.2.1_Linux_GA_P3448/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.0045 ] Generating RCM messages
[ 0.0085 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm /home/nvidia/nvidia/nvidia_sdk/JetPack_4.2.1_Linux_GA_P3448/Linux_for_Tegra/bootloader/nvtboot_recovery.bin 0 0
[ 0.0113 ] RCM 0 is saved as rcm_0.rcm
......
What confuse me most is when I flash nano at the first time, there is no directory ā/JetPack_4.2.1_Linux_GA_P3448/Linux_for_Tegraā, I have to use sdkmanager, then such directory will be create, and flash.sh. So I canāt understand:
Iāve tried with my nano and remove the bmp.blob. The nv logo is gone during boot up.
Yes, you need sdkmanager to install the Linux_for_Tegra for first time. Afterwards, you donāt need to always use it to help flash. You could directly use flash.sh to flash the board. sdkmanager is also using this script to flash.
To prevent sdkmanager reinstall bmp.blob back to your bootloader, I told you please not use sdkmanager during the test.
Would you tell me whatās wrong in my command thread? Iāve attached flash record as 1.txt, partition BMP is not be flashed. But why green NVIDIA logo is still exist?
Thanks. I will attach logs later for no uart cable. I have two nanos, both canāt work after flash. I also reinstall sdkmanager, but nvidia logo both exist.
I do find these logs:
ā¦
[0005.220] bmp blob is not loaded and initialized
[0005.225] Failed to display boot-logo
ā¦
But I swear the logo is still exist.