1b8d5a8e911ac97a31a0ef69765ec6e0e6b4052f
New Blanton_Script/usb_target.sh reports a USB mass-storage device's node, mount point or by-id path. It excludes whatever disk backs / and /host -- this platform can boot from a USB DOM, which also reports TRAN=usb -- refuses to guess when several USB disks are present, falls back to the whole device for superfloppy media, and when mounting, checks the result is actually writable rather than trusting that mount succeeded. Script B asks it for the device node and builds the stress command from the answer, so a stick that enumerates as sdb no longer sends the write test at whatever /dev/sda1 happens to be. The device is carried back through an echo marker, split in the shell literal as "<<D""EV=..." so the command echo cannot satisfy the pattern the macro waits for -- the same false-match guard used for PORTS0= and NCMIF=, arranged differently. Script B: DDR memtester drops its 100-pass limit and runs until stopped, matching the other soak loads. Fix: Script C ran `bgctl reset --yes` while killing processes, which is before the job logs are copied to USB. Moved to after the archive and after hw-test-session finish, so the run's own logs are collected before anything clears them. Script A -> V1.0.8 history updated. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014RetWKFZFG1ZHcitQAyhwM
Description
Blanton Tera Term TTL reliability test
4.2 MiB