JP 5.0.2 nv-l4t-bootloader-config service fails

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
, ,
1

Hi,

I got this issue with a custom rootFS and the 5.0.2 SD Card image. the nv-l4t-bootloader-config.service fails to start:

-- Logs begin at Thu 2022-04-21 14:54:41 CEST, end at Wed 2022-09-28 13:37:46 CEST. --
Sep 28 11:37:00 nvidia-desktop systemd[1]: Started Configure QSPI bootloader service.
Sep 28 11:37:00 nvidia-desktop nv-l4t-bootloader-config.sh[1444]: Restore link: APP to /dev/mmcblk0p1
Sep 28 11:37:00 nvidia-desktop nv-l4t-bootloader-config.sh[1444]: Restore link: kernel to /dev/mmcblk0p2
Sep 28 11:37:00 nvidia-desktop nv-l4t-bootloader-config.sh[1444]: Restore link: kernel-dtb to /dev/mmcblk0p3
Sep 28 11:37:00 nvidia-desktop nv-l4t-bootloader-config.sh[1444]: Restore link: kernel_b to /dev/mmcblk0p12
Sep 28 11:37:00 nvidia-desktop nv-l4t-bootloader-config.sh[1444]: Restore link: kernel-dtb_b to /dev/mmcblk0p13
Sep 28 11:37:01 nvidia-desktop nv-l4t-bootloader-config.sh[1444]: Restore link: recovery to /dev/mmcblk0p15
Sep 28 11:37:01 nvidia-desktop nv-l4t-bootloader-config.sh[1444]: Restore link: recovery-dtb to /dev/mmcblk0p16
Sep 28 11:37:01 nvidia-desktop nv-l4t-bootloader-config.sh[1444]: Restore link: RECROOTFS to /dev/mmcblk0p17
Sep 28 11:37:01 nvidia-desktop nv-l4t-bootloader-config.sh[1444]: Restore link: esp to /dev/mmcblk0p18
Sep 28 11:37:01 nvidia-desktop nv-l4t-bootloader-config.sh[1444]: Restore link: UDA to /dev/mmcblk0p19
Sep 28 11:37:01 nvidia-desktop nv-l4t-bootloader-config.sh[1240]: 3668-100---1--jetson-xavier-nx-devkit-
Sep 28 11:37:02 nvidia-desktop nv-l4t-bootloader-config.sh[1240]: Error. Cannot get valid version information
Sep 28 11:37:02 nvidia-desktop nv-l4t-bootloader-config.sh[1240]: Exiting ...
Sep 28 11:37:02 nvidia-desktop systemd[1]: nv-l4t-bootloader-config.service: Main process exited, code=exited, status=1/FAILURE
Sep 28 11:37:02 nvidia-desktop systemd[1]: nv-l4t-bootloader-config.service: Failed with result 'exit-code'.
Sep 28 13:36:15 nvidia-desktop systemd[1]: Started Configure QSPI bootloader service.
Sep 28 13:36:16 nvidia-desktop nv-l4t-bootloader-config.sh[3191]: 3668-100---1--jetson-xavier-nx-devkit-
Sep 28 13:36:17 nvidia-desktop nv-l4t-bootloader-config.sh[3191]: Error. Cannot get valid version information
Sep 28 13:36:17 nvidia-desktop nv-l4t-bootloader-config.sh[3191]: Exiting ...
Sep 28 13:36:17 nvidia-desktop systemd[1]: nv-l4t-bootloader-config.service: Main process exited, code=exited, status=1/FAILURE
Sep 28 13:36:17 nvidia-desktop systemd[1]: nv-l4t-bootloader-config.service: Failed with result 'exit-code'.

Content of nv_boot_control.conf:

TNSPEC 3668-200-0000-H.0-1-2-jetson-xavier-nx-devkit-
COMPATIBLE_SPEC 3668-100---1--jetson-xavier-nx-devkit-
TEGRA_CHIPID 0x19
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0

What could cause this? And what does not work after this fail?

3

Hi,

Please share the result of

sudo /usr/sbin/nv_bootloader_payload_updater --print-ver

4

Hey @WayneWWW
The result is:

Start running: /opt/nvidia/l4t-bootloader-config/nv-l4t-bootloader-config.sh -c
3668-100---1--jetson-xavier-nx-devkit-
Got update payload: /opt/ota_package/bl_update_payload
Tegra User Block Device: /dev/disk/by-partlabel
Tegra Boot Block Device: /dev/mtdblock0
Tegra GPT Block Device: /dev/mtdblock0
Get SPI boot device size failed
Publish Block Device Failed
/usr/sbin/nv_bootloader_payload_updater --print-ver failed.

I only exchanged the SD card while keeping the QSPI. I am not aware that I changed the QSPI partition table or any files it installs by updating my SD card previously with a custom OS.

5

Could you share the exact steps that to reproduce this error?

6

I am afraid that I don’t know what has to be done to get into this state. But at least you tell me that it’s not normal.

I’ll flash the QSPI again with default settings and will report back if it is gone.

7

@WayneWWW

Okay, I think you should be able to reproduce this:

Is there anything I could have modified inside the L4T directory that could affect the QSPI flash?
I think I did not modify anything, the jetson-xavier-nx-devkit-qspi.conf looks like this:

source "${LDK_DIR}/p3668.conf.common";
EMMC_CFG=flash_l4t_t194_qspi_p3668.xml;
DTB_FILE=tegra194-p3668-0000-p3509-0000.dtb;
NO_ROOTFS=${NO_ROOTFS:-1};
MISC_COLD_BOOT_CONFIG="tegra194-mb1-bct-misc-sd-l4t.cfg";
8

Hi,

I don’t think the “-S 15GiB” here has any effect. Could you remove it and see if that still reproduces the issue?

9

I am sorry, I skipped a line when copying the command that was used to flash.
The actual command was ./flash.sh jetson-xavier-nx-devkit-qspi mmcblk0p1

You don’t have the issue in a freshly installed system?

10

I don’t have any device to check on my side at this moment. So I can only ask you to try and confirm the steps.

There are lots of issue waiting in queue so it is unlikely I would check this issue immediately.

11

Okay, so from my side it looks like I have a 100% unmodified devkit OS and QSPI with the issue.
Unless you think anything else could have an effect on the QSPI flashing.

12

Hi,

Okay. We will try to reproduce issue.

One more thing to ask here. If you prepare another empty sdcard, plugged to the board and flash with jetson-xavier-nx-devkit.conf. Remove the card after flashed and replace with the current “custom rootfs” sdcard, will the issue still there?

13

I currently have:
QSPI flashed normally.

  • 1 SD Card with the 5.0.2 Image from the website
  • 2 SD Card with my custom rootfs

Both show this behavior.
You’d like me to flash an unmodified OS with the jetson-xavier-nx-devkit.conf? I’d have to do some work to flash the normal sample rootFS with the flash.sh as I never added that workflow to my scripts.
Would it alternatively be possible to flash with the SDKManager to produce the same result?

Otherwise if you wanted me to flash my custom rootFS, I already did that because I started from the “Custom” QSPI + Custom RootFS and switched to the “Custom” QSPI + RootFS from the 5.0.2 Image. After that I flashed only the QSPI on the board to see if it makes any difference. I say “Custom” because I am pretty sure that the QSPI that got flashed with my Custom RootFS was not modified from the one which would normally be flashed.

14

Yes, you can flash it with sdkamanger too.

  1. Flash with sdkmanager, check if there is such issue.

  2. Replace the sdcard in (1), with your " SD Card with my custom rootfs" and see if issue coming out or not.

Thanks.

16

Hey @WayneWWW

I am sorry for the late response. I’ve set up a PC with Ubuntu 18.04, installed the SDKManager and flashed the 5.0.2 Image. Unfortunately the result is completely different from the SD Card Image.

If I plug no display the system hangs at “please wait for the auto setup to complete”. If I plug a display it hangs at “please complete system configuration setup on desktop to proceed”…but the display remains black. Actually during the flashing in SDKmanager I selected to use a preselected username and password and skip the configuration process.

Anyway, I removed the not working SD Card from SDKManager and added my SD card with the custom OS:

Apr 21 12:56:10 localhost systemd[1]: Started Configure QSPI bootloader service.
Apr 21 12:56:10 localhost nv-l4t-bootloader-config.sh[2246]: Restore link: APP to /dev/mmcblk0p1
Apr 21 12:56:10 localhost nv-l4t-bootloader-config.sh[2246]: Restore link: kernel-dtb_b to /dev/mmcblk0p14
Apr 21 12:56:10 localhost nv-l4t-bootloader-config.sh[2246]: Restore link: recovery-dtb to /dev/mmcblk0p17
Apr 21 12:56:11 localhost nv-l4t-bootloader-config.sh[2207]: 3668-100---1--jetson-xavier-nx-devkit-
Apr 21 12:56:11 localhost nv-l4t-bootloader-config.sh[2207]: Info: Spec variable TegraPlatformSpec is not found.
Apr 21 12:56:11 localhost nv-l4t-bootloader-config.sh[2207]: Info: Write TegraPlatformSpec with 3668-200-0000-H.0-1-2-jetson-xavier-nx-devkit-.
Apr 21 12:56:11 localhost nv-l4t-bootloader-config.sh[2207]: Info: Spec variable TegraPlatformCompatSpec is not found.
Apr 21 12:56:11 localhost nv-l4t-bootloader-config.sh[2207]: Info: Write TegraPlatformCompatSpec with 3668-100---1--jetson-xavier-nx-devkit-.
Apr 21 12:56:12 localhost nv-l4t-bootloader-config.sh[2207]: Error. Cannot get valid version information
Apr 21 12:56:12 localhost nv-l4t-bootloader-config.sh[2207]: Exiting ...
Apr 21 12:56:12 localhost systemd[1]: nv-l4t-bootloader-config.service: Main process exited, code=exited, status=1/FAILURE
Apr 21 12:56:12 localhost systemd[1]: nv-l4t-bootloader-config.service: Failed with result 'exit-code'.

I am quite sure that you’ll be able to reproduce the issue.

17

Hi,

Sorry that are you talking about even flashing the whole device with sdkmanager, you can still see this kind of issue?

“Cannot get valid version information”

18

Well as I said, after flashing with SDK Manager the rootfs which was flashed by SDK Manager was not working as it got stuck during the oem-config step. So I can’t tell if the SDK Manager rootfs would have shown the issue.

What I can tell is that with the QSPI from SDK Manager and my custom rootfs the issue shows.
It also shows with the official SD Card Image. So I don’t see any chance that you will not observe it when you try it yourself.

Maybe someone else who uses 5.0.2 can check with “systemctl” if the nv-l4t-bootloader-config service fails?

20

Hi Seeky15,

This issue is due to missing kernel driver “mtdblock”. So please manually load it and this issue would be gone.

modprobe mtdblock

21

Added CONFIG_MTD=y and CONFIG_MTD_BLOCK=y and it starts without issues. Thank you.

1 Like
23

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.