Hello,
Jetpack 4.4 and TX2i with our custom-designed board.
I need to boot with our custom logo instead of nvidia logo.
I tried with 2 methods both are not reflecting our changes.
1st method is not working.
2nd Method is also not working
/Linux_for_Tegra/tools/bmp-splash
- OUT=/home/parashuram/ ./genbmpblob_L4T.sh t210 ./config_file.example ./BMP_generator_L4T.py /usr/bin/lz4c my-bmp.blob
Output
BMP IMAGE INFO : ./parashuram480.bmp parashuram 480; ./parashuram720.bmp parashuram 720; ./parashuram1080.bmp parashuram 1080
1+0 records in
1+0 records out
1 byte copied, 3.4829e-05 s, 28.7 kB/s
1+0 records in
1+0 records out
1 byte copied, 2.7129e-05 s, 36.9 kB/s
1+0 records in
1+0 records out
1 byte copied, 3.63e-05 s, 27.5 kB/s
1+0 records in
1+0 records out
1 byte copied, 3.0275e-05 s, 33.0 kB/s
./genbmpblob_L4T.sh: Success! bmp.blob is in ‘my-bmp.blob’.
- cp my-bmp.blob …/…/bootloader/bmp.blob
copied my-bmp.blob to bootloader
- sudo ./flash.sh -k BMP --image ./bootloader/bmp.blob jetson-tx2i mmcblk0p1
But this method also changes is not reflecting.
Am I doing any wrong here? if yes please help me out.
Thanks,
Parashuram
Hi,
Method 2 should work. Please share us the boot up log after you update the boot logo.
Hello,
Please find the attached boot_log.txt file. boot_log.txt (25.9 KB)
I can see this in boot log [0004.416] W> Boot logo display failed…
I’m Using DP port display for your reference.
Thanks,
Parashuram
Hi,
One more question here.
If you already crashed the logo and it will get blanked, what will you see if you restore to the original BMP blob file? Will the NV logo be restored?
Hello,
Yeah, still I can see A NV logo in display after logging in. If it’s crashed then it should any error or should show NV logo right?
Thanks,
Parashuram
Hi,
Yeah, still I can see A NV logo in display after logging in. If it’s crashed then it should any error or should show NV logo right?
This maybe just the jpeg file we put in rootfs but not splash screen. It is easily to get confused because these two are same picture.
Could you show me your original serial console log? I mean without any modification, just pure jetpack based release on your custom carrier board.
According to your log, It looks like your board does not have logo even without your change in BMP blob.
Hello,
This log file is without modification anything just cloned fresh L4T and flashed to TX2i.
boot_logo_fresh.txt (22.2 KB)
Thanks,
Parashuram
Hi,
Why do you use hdmi in this case? Where is the DP?
Hello,
Please find the boot log for tx2i with DP display.
boot_log_tx2i_dp.txt (22.2 KB)
Thanks,
Parashuram
Hi,
Your DP monitor is not initiated even in original setup.
It has nothing to do with BMP configuration.
Hello,
The logo will support for DP monitor right?
Because I’m not done any modification in L4t related to BMP configuration.
Regards,
Parashuram
Does boot logo will support for DP monitor right?
by default, bmp.blob is not able to reflect.
[0004.428] I> tegrabl_load_kernel_and_dtb: Done
[0004.432] E> tegrabl_display_clear: display is not initialized
[0004.438] W> Boot logo display failed…
[0004.441] I> Kernel EP: 0x80600000, DTB: 0x80000000
Could you please update I’m not able to load the boot logo.
Thanks,
Parashuram
I just checked… cboot does not support DP so no boot logo on DP.
Hello,
Thanks for your update.
Is there any method to do cause we don’t have the HDMI port in our custom board we have only DP ports.
I can in see a message in Boot log welcome to Cboot is there any method to do.
Like this
Welcome to Cboot
[0001.208] I> Cboot Version: t186-02737b3e
[0001.212] I> CPU-BL Params @ 0x235800000
please have a look into this let me know.boot_log_tx2i_dp.txt (22.2 KB)
Any help will be greatly apperciated.
Hi,
Unfortunately, if this is a feature that not supported now, then nothing we can help here.
You can find the tx2 cboot source from the download center and see if you can implement the DP support by yourself.
Hello Wayne,
Thank you for the update.