Repository navigation
docs(camera): say when the Hadron full-array mode fits a Nano 4GB - #161
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Corrects the Hadron page's note on the full-array mode for an Orin Nano 4GB, and updates the
jetson-hilskill with what the first flash run through it showed.Problem
docs/hadron.mdsaid Argus runs out of memory in mode 3 on an Orin Nano 4GB. That is only true at full-size output. Thejetson-hilskill saidbuild.shandflash.shalways 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:
nvargus-daemonholding 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.width=1280,height=960in 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.InsufficientMemory, also with gdm stopped and 2579 MB available at the start.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-recoveryon the JetPack 6 image brought the Nano 4GB up as0955:7623, andecho y | ./flash.sh JAJfrom that state ran to a booting image with nobody at the bench. Where sudo runs unprompted,./build.sh JAJalso ran unattended.systemctl isolate multi-user.targettook the USB network down until a power cycle, so the skill now warns against it. The notice at the top keepsconsoleand the cold-boot loop as untested.