-
released this
2026-08-30 22:13:48 +08:00 | 21 commits to main since this release✨ New features
Per-CONN margin profiles for the switch boards
combo_SWB_CONN13_high/_lowthroughcombo_SWB_CONN16_high/_lowreplace the oldcomboA/comboBpair. Each file's per-channel percentages follow the rails on that board, so a CONN13 profile is no longer a rough fit for CONN16.- SWB0 and SWB1 share a profile per CONN — the two boards carry identical rails and differ only by I2C bus.
- A high pass and a low pass are now the same run with
_highswapped for_low. - A profile applied to the wrong CONN margins the wrong rails and says nothing. The percentages are positional, so nothing detects the mismatch.
margin_apply_profile_all.shnow names the right profile per board instead of one name for all nine.
🐛 Bug fixes
VNOMwas the spec value, not what the rails actually sit at- 86 of the 144 channels moved up between +0.8% and +2.5% to the measured median for this platform —
PVDD3_3V_SYNTH_LDO_*3.3 → 3.38,P0V9_AVDD_*0.9 → 0.915,PVDD0_8V_T30.8 → 0.82, and so on. - This is not a display change.
VNOMis the denominator ofmargin_status's deviation %, and the basismargin_setderives high / low / OV / UV from. A rail sitting steady at 0.756 V used to read+0.80%against a nominal 0.75 and now reads0.00%; and asking for+3%now lands on a different absolute voltage than it did last week. - Margin logs from before and after this build cannot be compared directly. The numbers moved because the reference moved, not because the hardware did.
The batch profile script pointed at files that no longer exist
margin_apply_profile_all.shstill namedcomboAfor all nine boards. WithcomboA.confremoved, every board would have stopped atProfile not found— a nine-line wall of errors on a script that is normally left to run.
The channel map CSV was stale
docs/LTC2980_channel_map.csvis generated fromsettings/*.conf, so all 86 changed rails were wrong in it. Regenerated withtools/gen_channel_map.sh. It is output, not source — regenerate it, never hand-edit it.
📦 Downloads
File Contents Script_ABC_Blanton_V1.1.3.zipThe full Tera Term working directory, including Blanton_Script/to copy onto the DUTAfter copying to the DUT:
chmod +x ~/Blanton_Script/*.sh # see below grep -rlU $'\r' ~/Blanton_Script # expect no outputblanton_ber.shandnfc_polling.share invoked by the macros through./or~/, so they need the execute bit along withbmc_monitor.shandusb_target.sh— neither git nor a Windows/USB copy carries it reliably.⚠️ Before you run
- Re-baseline your margin expectations. Any pass/fail limits or golden logs derived from the old
VNOMvalues need redoing against this build. margin_savein any form writes NVM permanently and now writes margin windows derived from the new reference. Runmargin_status_all.shfirst and never call it during a test.- SWB profiles are per-CONN. Applying
combo_SWB_CONN13_highto a CONN16 board is silently wrong. - These three tests cannot share the switch:
blanton_ber.sh,blanton_tr518.shandblanton_traffic_linespeed. - PRBS takes the links down while
blanton_ber.shis armed. ce0keeps running until you stop it.- Two numbers must stay in step: Script C's
sleep 30andblanton_ber.sh'sBER_INTERVAL. FAN_SPEEDis 100 — the fans run flat out unless you changeconfig.ttl.nfc_polling.sh startclears the log, so Script B wipes Script A's NFC baseline file (the numbers are already in the console log).- The NFC tool is written for the customer's tag. It polls Type A / B / F only and parses Type A strictly; a tag of another technology is never discovered and fails as
no RF interface activation notification received. Without--expected-idit does not check identity, so a different tag of the same type still passes. - The three items listed as unverified in v1.1.0 are still unverified: the
ce0ingress mirror, the 120s settle inblanton_tr518.sh, andtest mode nr=noon stop.
🔗 Links
- ARCHITECTURE.md — test flow, data models, constraints
- CLAUDE.md — commands and the bench gotchas
- LTC2980_channel_map.csv — all 144 margin channels with the new
VNOM
Full changelog: V1.1.2...V1.1.3
Downloads