Hi Andy, the most recent version of balenaOS for Jetson devices, 2.82.11, does actually correspond to Jetpack 4.5.1, so you should be fine. Good catch on the Docs, we’ll have to get that updated.
As for the timeline, I think what you might be referring to is a rather peculiar situation where devices get their QSPI firmware updated when a user flashes and uses a “regular” Nvidia JetPack 4.6 SD Card, but then later on decides to try out balena. In that particular situation, the Nvidia JetPack 4.6 creates an incompatible boot scenario for balena, and the board has to be attached via USB to a Linux computer, and the Nvidia SDK Manager software must be used to re-flash it back to a 4.4 or 4.5 firmware. Once complete, you can just pop in the balena (4.5) SD Card, and it will boot right up.
We are currently working on just supporting 4.6 natively, in order to avoid the hassle of reverting the firmware for folks that have booted and played around with Nvidia 4.6. Unfortunately I don’t have a specific ETA for you though.
On the other hand, it’s worth noting that I just recently purchased a new Nano, and it came from the factory with 4.5 on the firmware. I wrote my balena SD Card and it booted right up, straight out of the box. So, if you happen to NOT have used Nvidia 4.6, you might be just fine on a new Nano, ha. Hope that helps!
In my case, i flashed the Jetson Nano with JP4.5.1, upgrading it from 4.4.
When I then wrote the newest Balena version to SD and tried to boot, the jetson nano failed. I got around this by using the jetson flash repo and flashing the Balena OS via USB while in forced recovery mode.