If there is a current best recommended method to flash Orin Nano 8gb developer kit?
I’ve tried sdkmanager dp6 and 5.1.2, flash.sh, l4t_initrd_flash.sh to both sd card and nvme0n1.
I’ve also tried l4t_initrd_flash.sh with ----no-systemimg and that at least finally appeared to succeed at flashing bootloader/generic/cfg/flash_t234_qspi.xml. But OrinNano still won’t boot even with dp6 sdcard. or JetPack_6.0_DP.zip (51.8 KB) jetson_board_spec.cfg.txt (7.0 KB) flash_1-6.1_0_20240215-141451.log (9.2 KB)
This was emitted by flash.sh
Board ID(3767) version(300) sku(0005) revision(L.1)
Chip SKU(00:00:00:D5) ramcode(00:00:00:02) fuselevel(fuselevel_production) board_FAB(300)
ECID is 0x80012344705E36436400000009018040
and that does not seem to match the orin nano 8gb from JetPack_6.0_DP_Linux_DP_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/ jetson_board_spec.cfg
I did everything discussed in the referenced postings and finally got a result “target generic has been flashed successfully”. I’ve attached that flash log.
Then booted the orin nano and no display. So I’ve attached serial console log that shows that boot attempt. That boot froze on the last line in that log.
Went back in with serial console and the boot was set to ‘Normal’ so I did not experiment there. I believe everything looks like my running Orin AGX developer kit.
I tried without and with Fumiya Fujinaka’s tegra-xudc.ko file but it made no difference.
If you have a more recently compiled tegra-xudc.ko file with the updated tegra-xudc.c I’ll try it. The one linked above is 5 times the size of the original which seems a large difference for a few lines of code.
I am trying to get orin nano running with dp6.2 so that I can install ros.org/iron.
Yes I did first try initrd_flash over the time period since your reply to my initial post. I succeeded with qspi flash --no-systemimg. but every other initrd_flash failed. I’ve attached 4 logs showing some of those failures.
I also tried several of the versions for initrd_flash that are listed here FlashingSupport.html and they too failed.
Please note that I’ve tried everything twice that is suggested in your cited post. I had actually done everything referenced in it before I posted my first thread above.
Thanks for suggestion. I’ll plug some different usb devices than what has been previously attached and see if it will boot and if not will again try initrd_flash with the higher load.
Thank you. Attached to my first post tonight is a serial console log titled 021924_initialboot.txt
I’ll post a new one tomorrow if my nano doesn’t boot. I also found the information to manually rebuild the kernel
and will do that if the usb devices doesn’t work.
You don’t need to post the same log again. I already saw that and that one is based on a wrong flash. Thus, we don’t consider checking that log for now.
Added a external usb ssd, a usb Astra-pro camera to my usb keyboard and mouse.
initrd_flash’ed the Nano. Initial boot never made it past the last line in this console log. flash_1-8_0_20240220-141324.log (9.5 KB) 022024_consolelog.txt (116.4 KB)
This console log made it one more line than others before it stopped.
I have tried many variations of sdkmanager, flash.sh, and I4t_initrd_flash.sh over the last couple of weeks. orinFLASH.txt (4.2 KB)
Here’s the logs from todays attempt. Lots of activity in console flash log. The usb-c to usb-a cable I am using is the one included with the orin nano developer kit.
Your attempt to toggle the power is failed due to permission denied…
Add[ ev/nvme0n6] LUN
emovable file: (no medium)
[ 70.002362] LUN: removable file: (no medium)
/bin/nv_enable_remote.sh: line 223: /sys/bus/usb/devices/usb2/power/control0: Permission denied
[ 70.005492] usb0: HOST MAC d6:47:00:95:16:00
[ 70.005497] usb0: MAC f2:9d:18:2e:04:af
Thus, the situation I saw here is
Your previous try seems mostly in vain because your flash command is wrong or the flash totally didn’t happen.
Please just keep in this situation that the board really get into flash state, recover every software change you added back to default. Just connect a usb device like mouse or keyboard to the usb hub to make it always power on and start the flash process…
Another question here. Does this board ever get flashed with jetpack5.1.2 or not?
I notice you mentioned jp5 in the beginning and we didn’t focus too much on it.
If even your jetpack5 is not able to get flashed with initrd flash, then the issue could be something else.
If the issue is something else, then waiting for next release might not help. Thus, please clarify this too.
Yes I have usb keyboard, mouse and added an astra_pro usb camera. This time tegra_xudc.ko did not error out.
Would it make any sense to try this usb3-recovery-mode What stopped me from trying it was it is unreversable.
When I tried jetpack5.1.2 it failed. I’ll try it again tomorrow with my ubuntu20.04 computer using sdkmanager5 and also a plain l4t_initrd_flash.sh with flash and console logs.