Thank you, I will try this out. I will guess that this is for all of the Jetson Nanos.
I have two cases for the QSPI-NOR flash. The first is for when I have a project SD card with an earlier version of JetPack. Flashing a new empty SD card with the older JetPack (which also flashes the QSPI) so I can use the project SD card is a lot of work. Also, it’s not very intuitive to many folks why their older project SD cards don’t work once you switch over to JP 4.5+, or why a newly flashed JetPack 4.4+ SD image doesn’t work on an upgraded machine.
The second case comes from another little project. I had been trying to boot a Nano 2GB from a SSD USB drive, but depending on how the drive was connected to the Jetson (connected directly or through a powered USB hub) the device was not being recognized. My guess was that the ‘usb start’ in UBoot did not wait long enough for the SSD to come online before enumeration. I changed the UBoot environment variables to wait a little while after starting, and then ‘usb reset’ which causes a USB renumeration. The drive appears as expected.
However it’s easy to make a mistake and put the UBoot system in a bad state since this is not an area I frequent much. If it’s just a matter of a quick flash of the QSPI-NOR to get back to the default state in UBoot, life be good. If you have to flash the whole system again (which takes more than 10 minutes in my dev environment on top of the amount of time it takes to download all the source material) this significantly effects development time.