Hey,
I did normal work, OpenCV build and sudo update and upgrade, after it and reboot, system cannot boot anymore.
In debug console I have bash access and some log info. I did a change in file like here Boots into black screen with a blinking cursor after auto update - #4 by WayneWWW but it still do not boot. boot log attached
there is chance to fix it ? and how to avoid that error in future ?
boot log.txt (35.4 KB)
Wrong post got referred. You should refer to this one.
thanks it helped me a bit but I’ve connected CSI camera and is selected as primary boot option, I need manually set it to option 0 0: primary kernel . then it boot fine.
Q1: How to set this ?
log
L4TLauncher: Attempting Direct Boot
L4T boot options
0: primary kernel
1: Custom Header Config: <CSI Camera IMX219 Dual>
Press 0-1 to boot selection within 3.0 seconds.
Press any other key to boot default (Option: 1)
L4TLauncher: Unable to boot via extlinux: Device Error
L4TLauncher: Attempting Kernel Boot
Failed to boot image: Device Error
Failed to boot kernel:0 partition
▒▒▒▒Shutdown state requested 1
hello kamil.nonckiewicz,
according to kernel init messages as below.
I don’t think it’s related to IMX219 camera sensor but your system configuration.
[ 17.937856] OTA work directory /mnt/ota_work is not found on /dev/nvme0n1p1
mount: /mnt: special device /dev/mmcblk3 does not exist.
[ 17.945482] Finding OTA work dir on internal storage device
[ 17.946883] mount /dev/mmcblk3 /mnt
[ 17.950061] Failed to mount /dev/mmcblk3 on the /mnt
[ 17.951439] Failed to run "mount_ota_work_partition /dev/mmcblk3 /mnt"
[ 17.952908] OTA work directory is not found on internal and external storage devices
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
bash-5.1#
are you using OTA for moving forward? may I know which Jetpack release version you’re working with?
and, please share your steps in details which reproduce such boot-up failure.
I am using Jetson System firmware version 36.2.0-gcid-34956989 date 2023-11-30T18:35:35+00:
I am not sure what OTA is and what it do. I want just boot my device and play with my cameras. anyway.
as @WayneWWW wrote to me I set L4T Configuration → OS chain A status toNormal and it will boot when I will click 0 and choose 0: primary kernel
full log of first boot is in my first message and I will try to put here second log of boot soon
here is second boot log with wrong L4T boot options
bootlog2.txt (73.2 KB)
Is hard to say how to reproduce it. I was using my jetson normally and after some reboot it just stopped to boot. Did change in UEFI Menu to boot normally and then this menu L4T boot options appear
hello kamil.nonckiewicz,
it looks like an unresolved issue we’ve met to boot from USB, by using dtbo which has the file size larger than 12kb.
may I know where is your root file system, or, which device (USB or NVMe) you’re used for booting-up?
if you’re now boot from USB, please try re-flash the target to boot from NVMe for confirmation.
besides,
you may also give it try by using smaller dtbo binary file, (smaller than 12kb) for verification.
hey, thanks for replay. I use sdcard to boot and nvme drive only as storage in the system.
ps. I tried boot from nvme time ago using but without success so I decide to stay with sdcard and use nvme as storage
hello kamil.nonckiewicz,
BTW,
according to your 1st comment, everything works at first place, right?
L4T boot options
0: primary kernel
1: Custom Header Config: <CSI Camera IMX219 Dual>
when I choose option 0 it boot ok, but is not a default option
this custom header is created by running Jetson-IO.
did you meant after configure CSI connector to select dual IMX219 you cannot booting up the target?
not exactly, I had boot with imx219 before with success. but when the jetson went to recovery mode from this time i cannot boot without manually select option 0
all right, please share what you have done for reference.
otherwise, please re-flash the target to have confirmation.
@JerryChang here is more or less what i did with my device:
L4T boot options menu at boot and require manually action to choose correct boot option.I want to avoid refleash all the time when any issue is with Jetson. Build and install software, opencv etc is not just a few mins and I want save time as possible.
at this moment board is on my desk and is easy to reflash, but finnally it will be in in the vehicle.
Is there any config file or UEFI setting for this L4T boot options
hello kamil.nonckiewicz,
since we don’t reproduce this locally, it might be an issue with your step-5 to upgrade the system.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.