ok let us check and comeback to you, is there is any particluar size of the image required? currently its 1.2MB, 3.7MB and 8.3MB
did u checked our logo files with dev kit?
I am following this closely as i am keen on implementing this, i think you issue might be the image files are too big, i noticed this in the documentation page:
Customers can replace the NVIDIA provided logo files with their own files and ensure the UEFI binary with the logo file(s) do not exceed the UEFI partition size (3.5MB) in the partition XML file. The partition XML files for various platforms are located in the ./bootloader/generic/cfg/ directory.
One of you images alone is 8mb which is way over the 3.5mb cap.
hi @brian178 , thank you for the suggestion, but my uefi bin size if 2.5MB only. i suspect some other changes also required to customize the logo, once after putting our logos,the default NVIDIA logo is coming as expected, but our logos not showing.
Hello @KevinFFF ,
thank you for your valuable inputs, after making the compression : none the logos are coming up.
i used to this command to remove the compression convert Wan720.bmp -compress none BMP3:result.bmp
the problem is the image quality is reduced, is there is any tool to make compression as none.
Sounds good news.
Please also do the similar operation for 480 and 1080 files.
UEFI would select one of them according to the resolution of monitor you are using.
Sorry that I’m not familiar with related tool to handle BMP, but you can just refer to the detailed information in our default logo files (nvidiagray*.bmp)
Hello @KevinFFF , any suggestions to implement boot progress bar instead bootlogs in the display.
Sorry that we don’t have experience to do that since there’re multiple boot firmwares during entire boot up.
You can refer to Jetson AGX Orin, Orin NX and Orin Nano Boot Flow — NVIDIA Jetson Linux Developer Guide 1 documentation for the boot flow in Jetson Orin Nano.
1 Like
thank your reply @KevinFFF ,
-
kindly can you please provide us any reference of any of your customer achvied it for replacing boot logs in display with boot progress bar.
-
And also please know us how we can disable showing logs in display, instead we show some logo.
There’re some users disabling the boot logs but not implement something like boot progress bar.
To remove the logs showing in screen during boot up, you may disable the framebuffer in kernel config.
-CONFIG_FRAMEBUFFER_CONSOLE=y
+CONFIG_FRAMEBUFFER_CONSOLE=n
1 Like
generally we wanted to know one thing regarding disabling FRAMEBUFFER,
is it must to enable CONFIG_EXPERT to disable CONFIG_FRAMEBUFFER_CONSOLE?
is not allowing to disable CONFIG_FRAMEBUFFER_CONSOLE without enabling CONFIG_EXPERT option
If it is now allowed, then please also enable CONFIG_EXPERT.
yeah if i enable CONFIG_EXPERT option, unable to flash the device, getting below error while flashing
issue already reported in this ticket Unable to flash after kernel config disable - #16 by bharath.gk
still not able to resolve it
That line is not the error and you can ignore it.
Please provide the full flash log as file here for further check.
yeah if i enable CONFIG_EXPERT option, unable to flash the device
OrinNano_device_logs.txt (105.8 KB)
please find attached logs for both host and device.
Host_logs.txt (306.0 KB)
[ 201]: l4t_flash_from_kernel: Successfully flash the external device
[ 201]: l4t_flash_from_kernel: The device size indicated in the partition layout xml is smaller than the actual size. This utility will try to fix the GPT.
[ 201]: l4t_flash_from_kernel: Error flashing qspi
It seems you’ve flashed the NVMe SSD successfully but fail to flash internal QSPI.
Could you run the following command to flash QSPI only?
$ sudo ./flash.sh -c bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal
we will check and let you know the results of this command
You can ignore that size error messages since it is not the root cause of the failure.
Please share the result about if you can flash QSPI only with the command I shared.
yes we are able to flash the qspi alone with that command you shared, but system is not booting,stuck during kernel boot, shared you the logs