Skip to content

docs(camera): say when the Hadron full-array mode fits a Nano 4GB - #161

Merged
dakejahl merged 3 commits into
mainfrom
dakejahl/hadron-full-array-nano4gb
Nov 12, 2026
Merged

dakejahl merged 3 commits into
mainfrom
dakejahl/hadron-full-array-nano4gb

Conversation

@dakejahl

@dakejahl dakejahl commented Nov 11, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Corrects the Hadron page's note on the full-array mode for an Orin Nano 4GB, and updates the jetson-hil skill with what the first flash run through it showed.

Problem

docs/hadron.md said Argus runs out of memory in mode 3 on an Orin Nano 4GB. That is only true at full-size output. The jetson-hil skill said build.sh and flash.sh always need the user to run them, and that every flash needs someone holding Force Recovery.

Solution

Full array. The note now says what fits and why. Bench, JAJ with an Orin Nano 4GB on the image from b697c62, Hadron on CAM1:

  • Where the memory goes: the kernel's nvmap accounting shows nvargus-daemon holding twelve buffers of 123.6 MB in mode 3, 1484 MB, and twelve of 31.4 MB in mode 0. Everything else it holds is about 70 MB.
  • Scaled output: with width=1280,height=960 in the caps, mode 3 ran to EOS. Available memory bottomed out between 260 and 480 MB with the desktop running, and at 817 MB with gdm stopped.
  • Full-size output: it failed with InsufficientMemory, also with gdm stopped and 2579 MB available at the start.
  • Demo: mode 3 held 13.0 fps with 200 MB available.

Skill. Recovery is now entered from the running image, and the button is only for a unit whose UEFI does not start. The three bullets that say so are the JetPack 7 branch's wording, so #157 rebases over them cleanly. On this bench sudo reboot --force forced-recovery on the JetPack 6 image brought the Nano 4GB up as 0955:7623, and echo y | ./flash.sh JAJ from that state ran to a booting image with nobody at the bench. Where sudo runs unprompted, ./build.sh JAJ also ran unattended. systemctl isolate multi-user.target took the USB network down until a power cycle, so the skill now warns against it. The notice at the top keeps console and the cold-boot loop as untested.

The page said Argus runs out of memory in mode 3 on an Orin Nano 4GB. On the bench that holds only at full-size output. Argus keeps twelve raw frames, 1.5 GB in mode 3, and a smaller picture in the caps adds almost nothing to that, so it runs.
The flash steps ran on the bench for the first time. Where sudo runs unprompted the build and the flash both run unattended, which the skill said they could not. It also names the one command that cut the USB link.
The skill asked for a held Force Recovery button on every flash. A running image reboots into recovery by itself, so the button is only needed when UEFI does not start. The wording is the JetPack 7 branch's, which found this first.
@dakejahl
dakejahl merged commit deacc74 into main Nov 12, 2026
1 check passed
@dakejahl
dakejahl deleted the dakejahl/hadron-full-array-nano4gb branch November 12, 2026 00:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant