# How to modify the boot logo with JetPack\_5.0.2\_Linux\_JETSON\_XAVIER\_NX\_TARGETS **URL:** \ **Category:** Jetson Xavier NX\ **Tags:** boot\ **Created:** [December 6, 2023, 11:20am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206 "2023-12-06T11:20:36Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![2398492542](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@2398492542](https://forums.developer.nvidia.com/u/2398492542)\ **Post date:** [December 6, 2023, 11:20am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/1 "2023-12-06T11:20:36Z")
How to modify the boot logo with JetPack\_5.0.2\_Linux\_JETSON\_XAVIER\_NX\_TARGETS ---
**Author:** ![TomNVIDIA](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/tomnvidia/32/14181_2.png) [@TomNVIDIA](https://forums.developer.nvidia.com/u/TomNVIDIA)\ **Post date:** [December 6, 2023, 4:24pm UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/2 "2023-12-06T16:24:14Z")
Hello, this topic belongs here: [Jetson & Embedded Systems - NVIDIA Developer Forums](https://forums.developer.nvidia.com/c/agx-autonomous-machines/jetson-embedded-systems/70) I will move it over for you. ---
**Author:** ![KevinFFF](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kevinfff/32/15508_2.png) [@KevinFFF](https://forums.developer.nvidia.com/u/KevinFFF)\ **Post date:** [December 7, 2023, 5:05am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/4 "2023-12-07T05:05:42Z")
Hi 2398492542, Are you using the devkit or custom board for Xavier NX? Please refer to the following instruction. [UEFI Adaptation — Jetson Linux Developer Guide 34.1 documentation (nvidia.com)](https://docs.nvidia.com/jetson/archives/r35.1/DeveloperGuide/text/SD/Bootloader/UEFI.html#customized-logo) ---
**Author:** ![1260092123](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@1260092123](https://forums.developer.nvidia.com/u/1260092123)\ **Post date:** [December 7, 2023, 5:35am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/5 "2023-12-07T05:35:47Z")
Hi,I want to remove uboot logo jetpack\_5.1.1. HOW to deal with? ---
**Author:** ![KevinFFF](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kevinfff/32/15508_2.png) [@KevinFFF](https://forums.developer.nvidia.com/u/KevinFFF)\ **Post date:** [December 7, 2023, 9:07am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/6 "2023-12-07T09:07:14Z")
For Jetpack 5, we uses UEFI as bootloader instead of uboot. You could also refer to the UEFI source to remove LogoDxe from config file. ---
**Author:** ![2398492542](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@2398492542](https://forums.developer.nvidia.com/u/2398492542)\ **Post date:** [December 7, 2023, 11:47am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/7 "2023-12-07T11:47:43Z")
I used the method you provided and got the following prompt in the terminal: nvidia: building from workspace rooted at: /home/hz/nvidia-uefi nvidia: found command: python3. nvidia: found command: virtualenv. nvidia: found command: mono. nvidia: found command: aarch64-linux-gnu-gcc. nvidia: found Python 3.9 or later. nvidia: Activating Python virtual environment. nvidia: Updating build environment (edk2-nvidia/Platform/NVIDIA/Jetson/PlatformBuild.py). edk2-nvidia/Silicon/NVIDIA/scripts/prepare\_stuart.sh: 行 41: stuart\_update：command not found ---
**Author:** ![mrhrobertson](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@mrhrobertson](https://forums.developer.nvidia.com/u/mrhrobertson)\ **Post date:** [December 7, 2023, 11:52am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/8 "2023-12-07T11:52:54Z")
This feels like the discovery and potential exploitation of the LogoFAIL vulnerability discovered by Binarly: [Finding LogoFAIL: The Dangers of Image Parsing During System Boot | Binarly – AI -Powered Firmware Supply Chain Security Platform](https://binarly.io/posts/finding_logofail_the_dangers_of_image_parsing_during_system_boot/index.html) Is NVIDIA looking to make the logo unmodifiable/protected in a security patch to the UEFI bootloader? ---
**Author:** ![2398492542](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@2398492542](https://forums.developer.nvidia.com/u/2398492542)\ **Post date:** [December 8, 2023, 3:42am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/10 "2023-12-08T03:42:16Z")
I have successfully applied the logo to the board, but the size of the logo is too small. Is there any way to change the size of the logo? ---
**Author:** ![KevinFFF](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kevinfff/32/15508_2.png) [@KevinFFF](https://forums.developer.nvidia.com/u/KevinFFF)\ **Post date:** [December 8, 2023, 6:15am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/11 "2023-12-08T06:15:21Z")
There should be 3 logo images with different resolution. What do you mean about the “the size of the logo is too small”? Which resolution is using currently? ---
**Author:** ![2398492542](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@2398492542](https://forums.developer.nvidia.com/u/2398492542)\ **Post date:** [December 10, 2023, 2:36am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/12 "2023-12-10T02:36:48Z")
I’ve solved the problem, thank you very much. After restarting, it will display normally. I manually modified the p3668.conf.common file. The modification content was to change CMDLINE\_ADD=“console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0”; to CMDLINE\_ADD=“console=ttyTCU0,115200n8 fbcon =map:0 net.ifnames=0”;The purpose is to prevent kernel information from being printed when the system starts. How can I flash only the modified files into the system? ---
**Author:** ![KevinFFF](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kevinfff/32/15508_2.png) [@KevinFFF](https://forums.developer.nvidia.com/u/KevinFFF)\ **Post date:** [December 11, 2023, 3:09am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/13 "2023-12-11T03:09:31Z")
Since you are modifying the cmdline for kernel, you could also just modify it in _/boot/extlinux/extlinux.conf_ from your board. ---
**Author:** ![2398492542](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@2398492542](https://forums.developer.nvidia.com/u/2398492542)\ **Post date:** [December 11, 2023, 10:53am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/14 "2023-12-11T10:53:45Z")
The contents of the /boot/extlinux/extlinux.conf file on the board are as follows: > TIMEOUT 30 > DEFAULT primary > > MENU TITLE L4T boot options > > LABEL primary > > ``` > LINUX /boot/Image > FDT /boot/dtb/kernel_tegra194-p3668-0001-p3509-0000.dtb > INITRD /boot/initrd > APPEND ${cbootargs} root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 nv-auto-config > > ``` > > # When testing a custom kernel, it is recommended that you create a backup of > > # the original kernel and add a new entry to this file so that the device can > > # fallback to the original kernel. To do this: > > # > > # 1, Make a backup of the original kernel > > # sudo cp /boot/Image /boot/Image.backup > > # > > # 2, Copy your custom kernel into /boot/Image > > # > > # 3, Uncomment below menu setting lines for the original kernel > > # > > # 4, Reboot > > # LABEL backup > > # MENU LABEL backup kernel > > # LINUX /boot/Image.backup > > # FDT /boot/dtb/kernel\_tegra194-p3668-0001-p3509-0000.dtb > > # INITRD /boot/initrd > > # APPEND ${cbootargs} How should I modify this file to ensure that the kernel log information will not be printed when the board starts up? What operations are required after the modification? I also want to ask what the role of TIMEOUT 30 in the first line of this file is. [extlinux.zip](https://forums.developer.nvidia.com/uploads/short-url/zvQ1uf9u21lJLqcbRMz0lEt4Yj7.zip) (643 Bytes) ---
**Author:** ![KevinFFF](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kevinfff/32/15508_2.png) [@KevinFFF](https://forums.developer.nvidia.com/u/KevinFFF)\ **Post date:** [December 12, 2023, 5:53am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/15 "2023-12-12T05:53:02Z")
> [@2398492542](#): > > ` APPEND ${cbootargs} root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 nv-auto-config` Please just remove `console=tty0` in above line. ---
**Author:** ![2398492542](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@2398492542](https://forums.developer.nvidia.com/u/2398492542)\ **Post date:** [December 12, 2023, 7:16am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/16 "2023-12-12T07:16:38Z")
I have tried this method. After deleting console=tty0, I tried restarting, but the kernel log information will still be printed. ---
**Author:** ![KevinFFF](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kevinfff/32/15508_2.png) [@KevinFFF](https://forums.developer.nvidia.com/u/KevinFFF)\ **Post date:** [December 12, 2023, 7:29am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/17 "2023-12-12T07:29:42Z")
> [@2398492542](#): > > The modification content was to change > CMDLINE\_ADD=“console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0”; to CMDLINE\_ADD=“console=ttyTCU0,115200n8 fbcon =map:0 net.ifnames=0”; I should do the same trick as you did before. Which UART interface do you want to disable the debug message? Have you also tried to remove `console=ttyTCU0,115200n8`? ---
**Author:** ![2398492542](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@2398492542](https://forums.developer.nvidia.com/u/2398492542)\ **Post date:** [December 12, 2023, 7:51am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/18 "2023-12-12T07:51:37Z")
Directly add the p3668.conf.common file in JetPack\_5.0.2\_Linux\_JETSON\_XAVIER\_NX\_TARGETS CMDLINE\_ADD=“console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0”; change it to CMDLINE\_ADD=“console=ttyTCU0,115200n8 fbcon =map:0 net.ifnames=0”; and then refresh the system. I successfully set the kernel information not to be printed, but I tried modifying it directly in the extlinux.conf of the board several times without success.After trying to remove console=ttyTCU0, 115200n8 also failed to remove the kernel information printing. ---
**Author:** ![KevinFFF](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kevinfff/32/15508_2.png) [@KevinFFF](https://forums.developer.nvidia.com/u/KevinFFF)\ **Post date:** [December 12, 2023, 9:27am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/19 "2023-12-12T09:27:40Z")
> [@2398492542](#): > > After trying to remove console=ttyTCU0, 115200n8 also failed to remove the kernel information printing. Which UART interface do you see the logs output? You could run `cat /proc/cmdline` to check if your modification take effects. ---
**Author:** ![2398492542](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@2398492542](https://forums.developer.nvidia.com/u/2398492542)\ **Post date:** [December 13, 2023, 1:02am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/20 "2023-12-13T01:02:56Z")
The output I get using cat /proc/cmdline is what the picture below shows: ![cat](https://global.discourse-cdn.com/nvidia/original/4X/3/e/0/3e0344a99f876f1f6f1c13483a7a37409138b0be.jpeg) From this picture, we can see that directly modifying extlinux.conf does not work. Are there any other modifications that need to be made? ? ---
**Author:** ![KevinFFF](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kevinfff/32/15508_2.png) [@KevinFFF](https://forums.developer.nvidia.com/u/KevinFFF)\ **Post date:** [December 13, 2023, 8:07am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/21 "2023-12-13T08:07:34Z")
> [@2398492542](#): > > The output I get using cat /proc/cmdline is what the picture below shows: It seems `ttyTCU0` and `tty0` still exist in kernel cmdline. Please just modify it in board config and re-flash the board to apply the change. ---
**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\ **Post date:** [January 3, 2024, 5:40am UTC](https://forums.developer.nvidia.com/t/how-to-modify-the-boot-logo-with-jetpack-5-0-2-linux-jetson-xavier-nx-targets/275206/23 "2024-01-03T05:40:40Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.