Flashing Hang/Freeze

Good day,

I’m not sure if this is an actual issue or not. I’ve modified my device tree to include the UART RTS/CTS. When I run

sudo ./flash.sh jetson-nano-qspi-sd mmcblk0p1

in order to complete the process, which is supposedly supposed to take 10m, but I’ve waited more than 1h and the process still hasn’t completed. After receiving the messages below, no new messages appear in the window. Has something gone wrong or do I just need to keep waiting? Please advise

[ 0.0047 ] Signing RCM messages
[ 0.0057 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0066 ] Assuming zero filled SBK key
[ 0.0110 ]
[ 0.0110 ] Copying signature to RCM mesages
[ 0.0145 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[ 0.0167 ]
[ 0.0167 ] Boot Rom communication
[ 0.0176 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml --skipuid

hello Vernon.Naidoo,

there’s Boot Rom communication logs without feedback,
you may refer to To determine whether the developer kit is in Force Recovery mode.
please using command $ lsusb to check your board has enter forced-recovery mode before flashing process.
for example, you should found below message.

Bus <bbb> Device <ddd>: ID 0955: <nnnn> Nvidia Corp.

Thank you. I have verified that with lsusb. It should be noted I’ve passed through that usb conencton into my vm where I’m doing the flashing, not sure if this could be causing issues. I have found an alternate method to resolve my initial issue using the built in gpio reconfiguration tool in the new jetpack. Was much easier to enable rts/cts by using this. I’m not sure if I’ll have time to revisit the flashing issue atm, will revisit at a later stage should the problem persist. Your assistance is much appreciated

hello Vernon.Naidoo,

the root-cause should be your VM environment settings.
we’re always using ubuntu host machine to flash the board with success.

The reason why VMs are not officially supported is that during a flash USB disconnects and reconnects multiple times. The host to the VM is probably not passing through the USB after a disconnect and reconnect, and the configuration for guaranteeing 100% pass through to VM is entirely under the control of the VM setup (the Jetson software has no way of adjusting this).

Thanks for the explanation. I Did add the usb to the pass through list for the vm (using virtualbox). This did work when I setup my TX2 a while back, that was half a year ago and a different vm though, and using the SDK manager instead of the flash.sh script. Perhaps a setting is different or some step in the setup for the nano is different. My obstacle is resolved for now though, even though this issue isn’t resolved. I’m not sure how I should close off the topic though? Or should I leave it open and a mod will close it?

hello Vernon.Naidoo,

thanks for confirmation,
you may click the icon in the bottom right to make a comment as solution to close this thread.