Hopefully you will see something in the voluminous logs.
Using this command fails to flash orin agx developer kit.
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml
–showlogs --network usb0 jetson-agx-orin-devkit internal
serial_console_log.txt (144.8 KB)
flash_1-6.1_0_20240504-173835.log (6.9 KB)
So I re-setup nfs and flashing got further but still failed. Tomorrow I’ll do it again and get another serial log;
This command produced the attached console log
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml --showlogs --network usb0 jetson-agx-orin-devkit internal
gotfurther.log (358.7 KB)
that shows it flashing to internal mmc drive.
ROOTFS_AB= ROOTFS_ENC= /home/scott/nvidia/nvidia_sdk/JetPack_6.0_Linux_JETSON_AGX_ORIN_TARGETS/Linux_for_Tegra/flash.sh --no-flash --rcm-boot jetson-agx-orin-devkit mmcblk0p1
Formatting APP partition /dev/mmcblk0p1 …
Formatting APP partition /dev/mmcblk0p1 …
Hi,
- Could you use this command to flash?
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" \
--showlogs --network usb0 jetson-agx-orin-devkit internal
- If above command fails, could you directly run the simplest flash.sh command to flash internal emmc first?
flash.sh to mmc and l4t_initrd_flash.sh to nvme, command above, both reported success.
Nvme reset boot gives video/display that is barely readable in that monitor is flashing and when I attempt completing OEM config it fails and that program crashes.
Mmc reset boot gives No video/display at all.
I tried to run sudo tools/l4t_create_default_user.sh -u scott -p AnythingWork123 -n chiorin --accept_license=true and it failed. Then removed accept_license and it still failed.
I can’t ssh into it and minicom connection wants a user/password but the defaults nor using scott/AnythingWork123 are accepted and can’t login.
Any suggestion to login via minicom? Or to fix video/display via bios? Here’s probably too many logs that don’t to my untrained eye show a resolution.
nvme_boot_Video_flashing_cant_see_it.txt (39.2 KB)
mmc_boot_NO_Video.txt (39.8 KB)
reset_boot.txt (39.3 KB)
minicom.txt (149.8 KB)
Thank you for your help.
How did it fail?
Did you run sudo ./apply_binaries.sh before it?
Which log is after running the script? I see none of them applies this.
run sudo tools/l4t_create_default_user.sh -u scott -p AnythingWork123 -n chiorin --accept_license=true and it failed. Then removed accept_license and it still failed.
When you see “[ 17.493721] Please complete system configuration setup on desktop to proceed…” in your log, it means l4t_create_default_user.sh didn’t apply or you didn’t flash the board.
Wayne,
minicom.txt is serial log of l4t_initrd_flash.sh command you provided above.
The last two lines of minicom.txt are:
[ 17.547306] Please complete system configuration setup on desktop to proceed…
��RmDeInit completed successfully
When I reset the Orin is when I got this:
-
Nvme reset boot gives video/display that is barely readable because the monitor is flashing and when I enter the
system configuration setup GUI and enter name/userid/password english /english and timezone when I click the last OK the application crashes and tries to send a system error report to ubuntu or nvidia but that process crashes too. nvme_boot_Video_flashing_cant_see_it.txt -
When I ran plain vanilla flash.sh and flashed mmc the flash.sh it too reported successful flashing mmc. After reset Orin gives No video/display at all. mmc_boot_NO_Video.txt
Hi,
Are you able to understand my questions here?
What I am telling is you said you ran “l4t_create_default_user.sh” but I see none of the log provided by you indicates you ever ran this tool.
I stated above I tried, it failed.
I am now going to run the l4t_initrd_flash.sh command from my ubuntu 20.04 workstation. If it gives me the same distorted - flashing video/display then tomorrow I’ll get another monitor out and go direct into that monitor skipping my otherwise fully functional kvm device.
Thanks,
Scott
Hi,
What does that mean “fail”? Could you just run below only and reflash the board?
sudo tools/l4t_create_default_user.sh -u scott -p AnythingWork123
No need to try anything else. Follow what we said first.
Also, please be aware that I am not helping you to get the display GUI for now.
What I am doing now is help you bypass the configuration so that you can use minicom to login into the board by using command line first.
Thank you. I just tried l4t_create_default_user.sh on my 20.04 workstation with no command line arguments and it popped up a graphical License. I accepted it and now have the required info to logon via minicom.
Thanks for your patience and assistance.
Sorry, could your really try to share more info in your comment?
Are you saying that your Jetson is able to login in console now? Just happened in 14 min since my last comment?
Running the following from my ubuntu 20.04 workstation successfully flashed the AGX Orin devkit:
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml”
–showlogs --network usb0 jetson-agx-orin-devkit internal
On graphical OEM Config logon I was able to complete setting up userid and hostname.
The video/display is still corrupt and flashing.
Based on other agx orin forum posts by you and kayccc in the morning I will first try directly connecting the Orin to another monitor going dp to dp. If that works then I’ll continue using it via ssh for a day.
I’ve also ordered a ugreen 4k displayport to hdmi cable that I’ll receive Tuesday. I’ll try it to hopefully fully resolve my problem.
xorg.conf looks fine/normal.
I’ll double check /var/log/Xorg.0.log too to look for errors.
AGX Orin is now happy.
Direct dp to dp monitor fixed display problem.
ugreen 4k displayport to hdmi cable also fixed display problem.
Issue is resolved. Thanks for your help from jp6dp to date.
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.