sudo ./flash.sh -r jetson-agx-xavier-devkit mmcblk0p1
hello pngstar777,
suggest you delete the image completely and try again,
since we’ve confirmed JetPack-4.6_Rev.2 to flash Jetson AGX Xavier DevKit without failures.
you may use the native ubuntu OS as your development environment.
your advice is use native Ubuntu(not VMware)? correct?
hmm… how to format AGX Xavier DevKit’s default storage?
I wanna format default storage.
hello pngstar777,
there’re two steps to dig further. first, please delete ~/nvidia/nvidia_sdk/JetPack_<version>_<platform>/Linux_for_Tegra/ completely, re-download the image with SDKManager and test again to flash the board manually. if the re-download image still having the same failure, please consider to use the native ubuntuOS.
the default image flashing process will erase the internal storage. you may check the flashing messages to obtain the details.
I tried it on native Ubuntu 18.04.
Install status is 100%, but device can’t boot again, too.
here’s my log, and I will try this cmd ( sudo ./flash.sh -r jetson-agx-xavier-devkit mmcblk0p1 ) on native Ubuntu.
SDKM_logs_JetPack_4.6_(rev.2)_Linux_for_Jetson_AGX_Xavier_modules_2021-11-08_16-47-38.zip (463.0 KB)
hello pngstar777,
the image flash process has complete, please gather the bootloader logs via port J501 for the details.
I attach log file from UART console.
and device can boot. but can’t display X window. because I can’t use this device. why…?
Please check attached file.
xavier_boot_log.txt (33.1 KB)
hello pngstar777,
due to below errors.
may I know what’s your display monitor, do you have other display monitor for testing?
[0010.121] E> tegrabl_linuxboot_add_disp_param, du 1 failed to get display params
[0010.128] E> tegrabl_linuxboot_add_disp_param, du 1 failed to get display params
did you boot from nvme?
could you please revise the boot order to make it boot from internal emmc?
[0009.966] I> Loading ramdisk from rootfs ...
[0009.969] I> Loading ramdisk binary from rootfs ...
[0009.974] I> rootfs path: /nvme/boot/initrd
[0010.016] I> Loading ramdisk sig file from rootfs ...
[0010.016] I> rootfs path: /nvme/boot/initrd.sig
may I know what’s your display monitor, do you have other display monitor for testing?
portable monitor, but I have more monitor for test.
did you boot from nvme?
I don’t know.
could you please revise the boot order to make it boot from internal emmc?
how can I change? or remove nvme and flash again?
hello pngstar777,
please have a try with other display monitor.
besides, here’s developer guide to Changing Boot Order with CBoot.
1 Like
I’m trying remove nvme and re-install now.
some msg is different from before.
If I’m already done, I will reply here.
and I have a question for you.
If the problem is caused by nvme, what should I do?
I don’t want to physically remove nvme from my xavier device anymore.
please refer to developer guide to update the boot order, please configure eMMC with higher priority as workarounds.
1 Like
I solved this issue!
Thank you for your guidance and support.
Have a good day.
I have a last question for you, I changed boot-order and reboot.
and then, boot-order is change default again.
Can I change the boot order permanently?
hello pngstar777,
could you please share the complete steps and the bootloader logs for reference,
don’t you interrupt cboot to change boot order in the cboot environment, i.e. $ setvar boot-order <dev1> <dev2> <dev3> ...
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.