etwenandClaude Opus 5
1fbdcc23d6
5_Blanton_Script_Reboot_Cycle.ttl loops: login -> sudo -i -> date -s -> fan speed -> wait_init -> Check Pt1..Pt13 -> show uptime -> reboot -> wait for the next boot. The cycle number is printed in the banner of every round. Like Script 4 it is standalone: it does not chain to A -> B -> C and does not use hw-test-session. Every cycle is a fresh boot, so there is nothing to carry over and nothing to tear down. The cdc_ncm probe was copied out of Script B without its :skip_ping label, so 'goto skip_ping' had no target. Tera Term does not check labels at load time - it raises the error only when it actually jumps, i.e. only when the NCM interface is missing, which is exactly the run where something is already wrong. The label is now there, and timeout is restored BEFORE the branch so one line covers both paths: the ping block waits on a 'sleep 10', already two thirds of the 15 s cap on a loaded DUT. Dmesg_i2c and PCIE Error Counters both announced themselves as Check Pt12; the second is now Pt13. Not verified on hardware yet. Two things to confirm on the bench: that wait "Booting in blind mode" really appears in this build's boot output (it has no timeout guard, so a changed string waits forever), and that re-running bmc-first-enroll every cycle is safe. Also ignore tmp/ - scripts not yet run on a DUT stage there, so an unverified script cannot reach the publish bundle where the tester cannot tell it apart from the rest. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014RetWKFZFG1ZHcitQAyhwM