Skip to content

docs(agents): fix the UEFI shell route into recovery in jetson-hil - #165

Merged
dakejahl merged 1 commit into
mainfrom
dakejahl/jetson-hil-bench-fixes
Nov 17, 2026
Merged

dakejahl merged 1 commit into
mainfrom
dakejahl/jetson-hil-bench-fixes

Conversation

@dakejahl

Copy link
Copy Markdown
Collaborator

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_RCM from the UEFI shell and then run reset -w. On a PAB with an Orin NX 16GB on UEFI 36.5.0, reset -w booted 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, so VDD_IN can't be read the usual way during a flash.

Solution

The recovery step now uses reset -c and says to cable the device port before the reset. New gotchas cover the QSPI-only legacy flash.sh command that restores a boot chain without touching the NVMe, usbreset for the ST-Link, and reading VDD_IN with busybox i2cget in the flash kernel.

On the PAB bench, setting the bit then running reset -c brought the module up as 0955:7323 within three seconds, while reset -w did 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.

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.
@dakejahl
dakejahl merged commit 2392274 into main Nov 17, 2026
1 check passed
@dakejahl
dakejahl deleted the dakejahl/jetson-hil-bench-fixes branch November 17, 2026 21:39
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