> For the complete documentation index, see [llms.txt](https://docs.arkelectron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arkelectron.com/products/flight-controller/jetson-pabs/ark-jetson-pab-carrier/developer/release-notes.md).

# Release Notes

## 6.2.2.9 - 2026-11-20

* Added support for the FLIR Hadron 640R's EO camera through the ARK Hadron Adapter, with a jetson-io overlay for each of CAM0 to CAM3
* Added support for the MIPI FLIR Boson+ through the ARK Boson Adapter, with a jetson-io overlay for each of CAM0 to CAM3
* ARK-OS updated to v1.5.1: on modules with a hardware video encoder, the camera stream uses it instead of the CPU, and saving a config on the Services page no longer corrupts it
* The ARK UI's Connections page loads in under a second and network stats update every 2 s. Both had waited 15 s on a Wi-Fi scan, which the radio cannot run while it hosts the hotspot
* The unit no longer hangs when a UEFI variable is read or written, for example by `efibootmgr` or a bootloader update, while the firmware TPM is in use
* jtop and the ARK UI's System page show the JetPack version: jetson-stats updated to 7.3.0
* SSH no longer stays dead when power is cut in the first 30 s after the flash reports the first boot complete
* `apt upgrade` no longer replaces the initrd, which carries the NVMe and PCIe modules the ARK kernel boots with
* `apt upgrade` no longer fails in `nvidia-l4t-initrd`, which had left every later apt command failing too
* rpcbind no longer listens on port 111

## 6.2.2.8 - 2026-10-30

* The UEFI boot order is re-sorted on every boot with the NVMe first: a boot without the SSD detected no longer moves it to the end of the order, where the unit stopped in the UEFI shell instead of booting
* A boot order changed in the UEFI menu now resets on the next boot; use the F11 boot menu for a one-time boot from another device

## 6.2.2.7 - 2026-10-19

* SuperSpeed devices on J33 no longer fall back to USB 2.0: its VBUS now comes up with the USB host instead of at power-on
* J33's load-switch over-current shutoff now works
* ARK-OS updated to v1.3.1: adds a Logs page and PointPerfect client fixes
* Boots the NVMe first: network boot (HTTP/PXE) no longer runs before the SSD, and NVMe outranks USB storage
* `apt upgrade` no longer replaces the ARK kernel and device tree with NVIDIA's stock ones, and `apt install nvidia-jetpack` now works
* A root filesystem on a UAS USB drive now mounts
* SSH no longer stays dead if power is cut while the first boot generates host keys
* The serial console prints errors only, so a burst of kernel warnings can no longer stall boot into a watchdog reset
* Boot is about 2 s faster: the unconnected PCIe controller C7 is no longer brought up

## 6.2.2.6 - 2026-07-23

* ARK-OS updated to v1.2.0

## 6.2.2.5 - 2026-07-21

* The camera userspace (Argus, `nvarguscamerasrc` and the NVIDIA multimedia libraries) is pinned to the L4T 36.4.4 packages and held from `apt upgrade`, fixing nvargus-daemon crashes and dropped frames when a camera pipeline is restarted
* The kernel now includes WireGuard VPN support as the `wireguard` module

## 6.2.2.4 - 2026-07-09

* Quad IMX219 is still the default camera setup, but selecting another camera in jetson-io now works; before, the built-in default collided with it
* jetson-io now lists the CSI camera overlays, which were missing from its menu in 6.2.2.1
* Added IMX708 (Raspberry Pi / Arducam Camera Module 3) support with an IMX708 Quad camera overlay
* Removed the single-camera IMX219 and IMX477 overlays, and the jetson-io camera names drop the ARK prefix (for example `Camera IMX219 Quad`)
* `nvarguscamerasrc` and the other NVIDIA GStreamer camera plugins are now preinstalled
* The I2S0 connector pins now boot as GPIO inputs idling high on the carrier pull-ups instead of being driven low, so the ARK I2S to GPIO overlay is no longer needed and was removed
* MAVSDK is no longer installed system-wide: ARK-OS bundles its own under `/usr/lib/ark-os/mavsdk`, so install MAVSDK yourself if your code links against it
* Preinstalled gpiod, i2c-tools, usbutils, pciutils, v4l-utils, uhubctl, inxi, xdotool and x11-xserver-utils, plus the Python packages spidev, pyserial, dronecan, smbus2 and Jetson.GPIO
* The system clock now starts at the image build time, so desktop autologin works on a first boot without network time
* ARK-OS updated to v1.1.0
* The flasher is now fetched from the main branch and flashes any release; it is no longer attached to each release

## 6.2.2.1 - 2026-06-10

* Initial release on JetPack 6.2.2 (L4T R36.5.0): one NVMe image with Super mode for every Orin Nano and Orin NX module
* Quad IMX219 cameras are enabled by default
* Ships with ARK-OS v1.0.0, MAVSDK 3.17.1 and jtop preinstalled


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.arkelectron.com/products/flight-controller/jetson-pabs/ark-jetson-pab-carrier/developer/release-notes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
