Repository navigation
docs(agents): fix the UEFI shell route into recovery in jetson-hil - #165
Merged
Merged
Conversation
On a PAB bench, the shell's `reset -w` booted normally from QSPI after the recovery bit was set, and only `reset -c` reached the BootROM. The same session hit three other things the skill didn't cover: an interrupted initrd flash leaves QSPI without a boot chain, the ST-Link VCP stops passing data, and the flash kernel has no INA3221 driver for reading VDD_IN.
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 jetson-hil skill's UEFI shell route into recovery and adds three bench gotchas from a PAB RMA session.
Problem
The skill said to set
PMC_SCRATCH0_MODE_RCMfrom the UEFI shell and then runreset -w. On a PAB with an Orin NX 16GB on UEFI 36.5.0,reset -wbooted normally from QSPI. The same session also hit three failures the skill didn't describe. An initrd flash interrupted before QSPI finished left the module booting straight into recovery. The ST-Link V3 debug UART stopped passing data. The flash kernel has no INA3221 driver, soVDD_INcan't be read the usual way during a flash.Solution
The recovery step now uses
reset -cand says to cable the device port before the reset. New gotchas cover the QSPI-only legacyflash.shcommand that restores a boot chain without touching the NVMe,usbresetfor the ST-Link, and readingVDD_INwithbusybox i2cgetin the flash kernel.On the PAB bench, setting the bit then running
reset -cbrought the module up as0955:7323within three seconds, whilereset -wdid not. The QSPI-only flash restored a module whose QSPI had been left empty by the interrupted flashes, and it booted to the UEFI menu afterwards.