MIPI Interactive Flicker Test Report
Generated: 2026-04-17 14:48:47 |
Model: claude-opus-4-6
Stop reason: Flicker confirmed by operator at capture 0368 [20260417_144749]
1 confirmed flicker(s)
44 false alarm(s)
24 Claude said no
D-PHY Configuration
Pixel clock: 72.0 MHz |
Bit rate: 432.0 Mbit/s per lane |
Byte clock: 54.000 MHz
(18.519 ns/byte) |
UI: 2.315 ns
| Field | Spec (ns) | Rnd Best | Rnd Up |
Extra | Final | Actual (ns) | Status |
lpx | ≥ 50.0 | 3 | 3 | +0 | 3 | 55.56 | ✓ |
hs_prepare | 49.3 – 98.9 | 3 | 3 | +1 | 4 | 74.07 | ✓ |
hs_zero | ≥ 94.1 | 5 | 6 | +0 | 6 | 111.11 | ✓ |
hs_trail | ≥ 69.3 | 4 | 4 | +1 | 5 | 92.59 | ✓ |
hs_exit | ≥ 100.0 | 5 | 6 | +0 | 6 | 111.11 | ✓ |
clk_prepare | 38.0 – 95.0 | 2 | 3 | +0 | 3 | 55.56 | ✓ |
clk_zero | ≥ 244.4 | 13 | 14 | +3 | 17 | 314.81 | ✓ |
clk_post | ≥ 180.4 | 10 | 10 | +0 | 10 | 185.19 | ✓ |
clk_trail | ≥ 60.0 | 3 | 4 | +0 | 4 | 74.07 | ✓ |
✓ All D-PHY v1.1 Table 14 constraints satisfied.
Samsung DSIM Registers
| Register | Address | Value | Field breakdown |
| PHY_TIMING | 0xb4 |
0x00000306 |
lpx=3 hs_exit=6 |
| PHY_TIMING1 | 0xb8 |
0x03110a04 |
clk_prepare=3 clk_zero=17
clk_post=10 clk_trail=4 |
| PHY_TIMING2 | 0xbc |
0x00040605 |
hs_prepare=4 hs_zero=6
hs_trail=5 |
u-boot Commands
# D-PHY PHY timing registers (pixel clock 72.0 MHz, 432.0 Mbit/s, byte clock 54.000 MHz)
#
# PHY_TIMING (0xb4) = 0x00000306 lpx=3 hs_exit=6
# PHY_TIMING1 (0xb8) = 0x03110a04 clk_prepare=3 clk_zero=17 clk_post=10 clk_trail=4
# PHY_TIMING2 (0xbc) = 0x00040605 hs_prepare=4 hs_zero=6 hs_trail=5
# Enable Round-Up rounding (dsi-tweak bit 2)
setenv flb_dtovar "${flb_dtovar} dsi-tweak=4"
# Extra PHY cycles above Round-Up minimum
setenv flb_dtovar "${flb_dtovar} dsi-phy-extra-hs-prepare=1"
setenv flb_dtovar "${flb_dtovar} dsi-phy-extra-hs-trail=1"
setenv flb_dtovar "${flb_dtovar} dsi-phy-extra-clk-zero=3"
saveenv
boot
Event Log
| Capture | Timestamp | Channel |
LP-low plateau | LP exit→HS | LP-11 voltage |
Claude: flicker? | Outcome |
| 0001 | 20260417_112836 | dat | 379.5 ns | 384.6 ns | 1.016 V | NO | Claude said NO — user not asked |
| 0006 | 20260417_113037 | dat | 107.6 ns | 2.8 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0010 | 20260417_114925 | dat | 6.9 ns | 0.8 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0013 | 20260417_115424 | dat | 108.0 ns | 2.1 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0031 | 20260417_120132 | dat | 108.2 ns | 3.4 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0041 | 20260417_120537 | dat | 12.9 ns | 3.2 ns | 1.017 V | YES | ✓ FALSE ALARM |
| 0043 | 20260417_120637 | dat | 107.9 ns | 113.0 ns | 1.016 V | NO | Claude said NO — user not asked |
| 0054 | 20260417_121057 | dat | 379.6 ns | 384.8 ns | 1.016 V | NO | Claude said NO — user not asked |
| 0058 | 20260417_121236 | dat | 107.6 ns | 3.5 ns | 1.015 V | YES | ✓ FALSE ALARM |
| 0059 | 20260417_121318 | dat | 108.0 ns | 2.9 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0062 | 20260417_121439 | dat | 379.6 ns | 384.7 ns | 1.017 V | NO | Claude said NO — user not asked |
| 0065 | 20260417_121555 | dat | 107.8 ns | 2.9 ns | 1.015 V | YES | ✓ FALSE ALARM |
| 0072 | 20260417_121850 | dat | 379.6 ns | 384.8 ns | 1.016 V | NO | Claude said NO — user not asked |
| 0080 | 20260417_122200 | dat | 22.0 ns | 1.2 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0089 | 20260417_122821 | dat | None ns | 0.0 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0092 | 20260417_125020 | dat | 107.8 ns | 2.8 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0095 | 20260417_125144 | dat | 107.8 ns | 2.5 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0096 | 20260417_125223 | dat | 108.0 ns | 113.0 ns | 1.015 V | NO | Claude said NO — user not asked |
| 0098 | 20260417_125316 | dat | 107.6 ns | 2.4 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0101 | 20260417_125442 | dat | 108.0 ns | 2.9 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0104 | 20260417_125605 | dat | 107.7 ns | 2.9 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0105 | 20260417_125642 | dat | 108.0 ns | 1.0 ns | 1.017 V | YES | ✓ FALSE ALARM |
| 0114 | 20260417_130019 | dat | 107.7 ns | 2.4 ns | 1.015 V | YES | ✓ FALSE ALARM |
| 0119 | 20260417_130226 | dat | 107.8 ns | 2.1 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0120 | 20260417_130301 | dat | 108.2 ns | 1.7 ns | 1.015 V | YES | ✓ FALSE ALARM |
| 0131 | 20260417_130727 | dat | 379.5 ns | 384.7 ns | 1.016 V | NO | Claude said NO — user not asked |
| 0136 | 20260417_130928 | dat | 107.8 ns | 2.5 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0137 | 20260417_131006 | dat | 379.7 ns | 384.8 ns | 1.016 V | NO | Claude said NO — user not asked |
| 0141 | 20260417_131144 | dat | 108.0 ns | 2.8 ns | 1.015 V | YES | ✓ FALSE ALARM |
| 0143 | 20260417_131243 | dat | 107.6 ns | 1.3 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0148 | 20260417_131452 | dat | 58.7 ns | 1.7 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0149 | 20260417_131527 | dat | 379.6 ns | 384.9 ns | 1.015 V | NO | Claude said NO — user not asked |
| 0153 | 20260417_131707 | dat | 107.6 ns | 0.7 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0165 | 20260417_132157 | dat | 107.6 ns | 2.9 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0166 | 20260417_132234 | dat | 379.6 ns | 384.7 ns | 1.016 V | NO | Claude said NO — user not asked |
| 0170 | 20260417_132412 | dat | 107.8 ns | 3.9 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0187 | 20260417_133058 | dat | 108.0 ns | 3.9 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0189 | 20260417_133222 | dat | 27.0 ns | 2.9 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0191 | 20260417_133322 | dat | 193.7 ns | 2.4 ns | 1.016 V | NO | Claude said NO — user not asked |
| 0193 | 20260417_133416 | dat | 108.2 ns | 3.4 ns | 1.015 V | YES | ✓ FALSE ALARM |
| 0217 | 20260417_134343 | dat | 107.8 ns | 2.9 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0226 | 20260417_134724 | dat | 107.6 ns | 3.2 ns | 1.015 V | YES | ✓ FALSE ALARM |
| 0248 | 20260417_135604 | dat | 379.8 ns | 384.8 ns | 1.015 V | NO | Claude said NO — user not asked |
| 0257 | 20260417_135942 | dat | 27.3 ns | 3.4 ns | 1.014 V | YES | ✓ FALSE ALARM |
| 0264 | 20260417_140237 | dat | 108.2 ns | 2.7 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0270 | 20260417_140510 | dat | 379.5 ns | 384.7 ns | 1.014 V | NO | Claude said NO — user not asked |
| 0272 | 20260417_140604 | dat | 379.5 ns | 384.6 ns | 1.017 V | NO | Claude said NO — user not asked |
| 0278 | 20260417_140829 | dat | 107.6 ns | 112.8 ns | 1.016 V | NO | Claude said NO — user not asked |
| 0280 | 20260417_140922 | dat | None ns | None ns | 1.015 V | YES | ✓ FALSE ALARM |
| 0281 | 20260417_140958 | dat | 108.2 ns | 3.5 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0282 | 20260417_141108 | dat | 107.8 ns | 1.0 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0284 | 20260417_141207 | dat | 108.0 ns | 3.0 ns | 1.015 V | YES | ✓ FALSE ALARM |
| 0294 | 20260417_141626 | dat | 108.0 ns | 113.0 ns | 1.016 V | NO | Claude said NO — user not asked |
| 0295 | 20260417_141657 | dat | 379.5 ns | 384.6 ns | 1.015 V | NO | Claude said NO — user not asked |
| 0296 | 20260417_141726 | dat | 107.8 ns | 3.2 ns | 1.017 V | YES | ✓ FALSE ALARM |
| 0300 | 20260417_141915 | dat | 379.6 ns | 384.7 ns | 1.015 V | NO | Claude said NO — user not asked |
| 0306 | 20260417_142140 | dat | 379.2 ns | 384.6 ns | 1.015 V | NO | Claude said NO — user not asked |
| 0313 | 20260417_142428 | dat | 107.8 ns | 3.0 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0318 | 20260417_142636 | dat | 379.5 ns | 384.8 ns | 1.016 V | NO | Claude said NO — user not asked |
| 0320 | 20260417_142728 | dat | 379.6 ns | 384.7 ns | 1.016 V | NO | Claude said NO — user not asked |
| 0322 | 20260417_142822 | dat | 379.3 ns | 384.8 ns | 1.015 V | NO | Claude said NO — user not asked |
| 0323 | 20260417_142851 | dat | 107.9 ns | 3.2 ns | 1.015 V | YES | ✓ FALSE ALARM |
| 0326 | 20260417_143017 | dat | 194.0 ns | 1.2 ns | 1.015 V | YES | ✓ FALSE ALARM |
| 0331 | 20260417_143240 | dat | 379.6 ns | 384.6 ns | 1.016 V | NO | Claude said NO — user not asked |
| 0339 | 20260417_143551 | dat | 108.0 ns | 0.9 ns | 1.016 V | YES | ✓ FALSE ALARM |
| 0341 | 20260417_143654 | dat | 107.6 ns | 2.8 ns | 1.015 V | YES | ✓ FALSE ALARM |
| 0355 | 20260417_144230 | dat | 108.0 ns | 2.0 ns | 1.015 V | YES | ✓ FALSE ALARM |
| 0359 | 20260417_144415 | dat | 379.6 ns | 384.6 ns | 1.015 V | NO | Claude said NO — user not asked |
| 0368 | 20260417_144749 | dat | 107.8 ns | 2.0 ns | 1.016 V | YES | ✖ CONFIRMED FLICKER |
Claude Assessments
Capture 0006 [20260417_113037] — FALSE ALARM
YES
The LP-low plateau at ~108 ns comfortably exceeds the 50 ns SN65DSI83 requirement, so that alone would not cause a missed SoT. However, the LP exit → HS transition duration of only 3 ns is critically below the 50 ns minimum specification, meaning the LP-01/LP-00 state machine likely completed too fast for the bridge's LP receiver to properly detect and latch the SoT sequence. Additionally, the HS amplitude of only 28 mV is far below the normal 105–122 mV range and falls under the 50 mV "absent" threshold, indicating the bridge almost certainly failed to achieve differential lock on the HS data. The combination of an essentially undetectable LP-to-HS transition and absent HS signaling amplitude makes this a genuine flicker event where the SN65DSI83 missed the packet entirely.
Capture 0010 [20260417_114925] — FALSE ALARM
YES
The LP-low plateau of 6.9 ns is dramatically below the SN65DSI83's 50 ns minimum detection threshold, and the LP exit-to-HS transition of only 1 ns confirms the LP-01/LP-00 SoT preamble states were essentially absent. Additionally, the HS amplitude of 43 mV is well below the normal 105–122 mV range and falls under the 50 mV "absent" threshold, indicating the bridge almost certainly failed to lock onto the HS data burst. Taken together — a near-nonexistent LP-low plateau, sub-spec LP exit timing, and collapsed HS amplitude — this is a textbook case of a missed SoT that would cause visible flicker on the display.
Capture 0013 [20260417_115424] — FALSE ALARM
YES
The HS amplitude of 33 mV is critically low—well below the SN65DSI83's differential detection threshold (normal range 105–122 mV), meaning the bridge almost certainly cannot reliably decode the HS data burst even if SoT is detected. Additionally, the LP exit → HS transition of only 2 ns is far below the required 50 ns minimum, indicating the LP-01/LP-00 preamble states are effectively absent or too brief for the bridge's LP receiver to register the start-of-transmission sequence. While the LP-low plateau itself measures 108 ns (above the 50 ns threshold), the combination of a near-absent LP exit duration and severely attenuated HS amplitude strongly indicates the SN65DSI83 either missed the SoT entirely or cannot recover valid data from this burst, making visible flicker virtually certain.
Capture 0031 [20260417_120132] — FALSE ALARM
YES
The LP-low plateau of 108 ns meets the ≥50 ns requirement, but the LP exit→HS transition of only 3.4 ns is critically below the 50 ns minimum specification. This means the LP-01 and LP-00 states that constitute the SoT preamble are essentially absent or far too brief for the SN65DSI83 to properly detect and synchronize to the start-of-transmission. Additionally, the HS amplitude of 30.5 mV is well below the normal 105–122 mV range and falls under the 50 mV "absent" threshold, indicating the bridge almost certainly failed to lock onto the HS data burst. The combination of a near-instantaneous LP exit and effectively absent HS signaling makes this a genuine flicker event.
Capture 0041 [20260417_120537] — FALSE ALARM
YES
The LP-low plateau of 12.9 ns is dramatically below the SN65DSI83's required ≥ 50 ns minimum, giving the bridge only ~26% of the time it needs to reliably detect the LP-01/LP-00 SoT preamble. The LP exit-to-HS transition of just 3.2 ns further confirms the LP-01 and LP-00 states are essentially being skipped, making SoT detection virtually impossible. Additionally, the HS amplitude of 87 mV is below the normal 105–122 mV range, which compounds the problem by reducing the bridge's ability to lock onto the HS data even if it did somehow detect the truncated SoT. All three anomalies together make this a high-confidence flicker event.
Capture 0058 [20260417_121236] — FALSE ALARM
YES
The HS amplitude of 31 mV is critically low — well below the SN65DSI83's differential receiver threshold (normal range 105–122 mV, and flagged absent at <50 mV) — meaning the bridge almost certainly cannot resolve valid HS data even if the SoT were properly detected. Additionally, the LP exit → HS transition of only 4 ns is far below the 50 ns minimum specification, indicating the LP-01/LP-00 preamble states were too brief for the bridge's LP receiver to reliably detect the start-of-transmission sequence. While the LP-low plateau itself measured 108 ns (adequate), the combination of a near-absent LP exit duration and severely attenuated HS amplitude means the SN65DSI83 will either miss the SoT entirely or fail to decode the subsequent HS burst, resulting in visible flicker.
Capture 0059 [20260417_121318] — FALSE ALARM
YES
The LP-low plateau of 108 ns meets the ≥50 ns requirement, but the LP exit → HS transition of only 3 ns is critically below the 50 ns minimum specification. This means the LP-01/LP-00 SoT preamble states were not held long enough for the SN65DSI83 to properly detect the start-of-transmission. Additionally, the HS amplitude of 30 mV is far below the normal 105–122 mV range and falls under the 50 mV "absent" threshold, indicating the bridge almost certainly failed to lock onto the HS data. The combination of a nearly instantaneous LP exit and effectively absent HS signaling makes this a clear flicker event.
Capture 0065 [20260417_121555] — FALSE ALARM
YES
The HS amplitude of only 24 mV (single-ended) is critically below the normal 105–122 mV range and well under the 50 mV threshold for a valid HS signal — the SN65DSI83 almost certainly cannot reliably detect or decode HS data at this level. Additionally, the LP exit-to-HS transition time of only 3 ns is far below the 50 ns specification minimum, indicating the LP-01/LP-00 preamble states were essentially absent or too brief for the bridge's LP receiver to properly recognize the SoT sequence. While the LP-low plateau itself measured 108 ns (above the 50 ns requirement), the combination of a near-absent LP exit duration and severely attenuated HS amplitude means the bridge very likely missed this transmission entirely, producing a visible flicker event.
Capture 0080 [20260417_122200] — FALSE ALARM
YES
The LP-low plateau of 22 ns is less than half the SN65DSI83's required ≥ 50 ns minimum for reliable SoT detection, and the LP exit-to-HS transition of only 1 ns confirms the LP-01/LP-00 preamble states were essentially absent. With these timing violations, the bridge almost certainly failed to recognize the start-of-transmission, causing it to miss the subsequent HS burst. The HS amplitude of 126 mV indicates the transmitter did drive a valid HS burst, so the data was sent but the bridge had no properly-timed SoT to latch onto, which is the classic mechanism for visible flicker on this platform.
Capture 0089 [20260417_122821] — FALSE ALARM
YES
The LP-low plateau is completely absent (reported as `None` / 0 ns), far below the SN65DSI83's 50 ns minimum requirement for SoT detection. Additionally, the HS amplitude is only 0.5 mV—effectively zero against the normal 105–122 mV range—confirming that no valid HS data burst was established after the LP exit. The combination of a missing LP-01/LP-00 preamble and absent HS signaling means the bridge almost certainly failed to recognize the start-of-transmission, which would produce a visible flicker or blank frame on the display.
Capture 0092 [20260417_125020] — FALSE ALARM
YES
The HS amplitude of 23 mV is critically low — well below the SN65DSI83's differential detection threshold (normal range 105–122 mV, and flagged absent at <50 mV). This means the bridge almost certainly cannot resolve valid HS data from this burst, regardless of LP timing. Additionally, the LP exit → HS transition of only 3 ns is far below the 50 ns minimum required for the bridge to properly detect the LP-01/LP-00 SoT preamble states, even though the LP-low plateau itself measured 108 ns. The combination of an essentially absent HS signal and a grossly non-compliant LP exit timing makes it virtually certain the SN65DSI83 missed this SoT, resulting in visible flicker.
Capture 0095 [20260417_125144] — FALSE ALARM
YES
The HS amplitude of 28 mV is critically low—well below the SN65DSI83's differential detection threshold (normal range 105–122 mV, and flagged absent at <50 mV)—meaning the bridge almost certainly cannot reliably detect the HS data burst even if the LP sequencing were perfect. Additionally, the LP exit → HS transition of only 2 ns is far below the 50 ns minimum specification, indicating the LP-01/LP-00 preamble states are essentially absent or too brief for the bridge's LP receiver to properly parse the SoT sequence. While the LP-low plateau itself measures 108 ns (above the 50 ns threshold), the combination of a virtually nonexistent LP exit duration and an HS amplitude so low it qualifies as "absent" makes it nearly certain the SN65DSI83 missed this SoT, resulting in visible flicker.
Capture 0098 [20260417_125316] — FALSE ALARM
YES
The HS amplitude of only 24 mV (single-ended) is critically below the normal 105–122 mV range and well under the 50 mV "absent" threshold, indicating the HS data burst was essentially not received by the SN65DSI83. Additionally, the LP exit-to-HS transition time of just 2 ns is far below the 50 ns minimum specification, meaning the LP-01/LP-00 states were too brief for the bridge to properly recognize the SoT sequence. Although the LP-low plateau itself measured ~108 ns (adequate), the combination of a nearly absent HS burst and a grossly non-compliant LP exit duration means the bridge almost certainly failed to lock onto this transmission, resulting in a missed frame and visible flicker.
Capture 0101 [20260417_125442] — FALSE ALARM
YES
The LP-low plateau itself at 108 ns is adequate (≥ 50 ns), but the LP exit-to-HS transition of only 3 ns is critically below the 50 ns minimum specification. This means the LP-01 and/or LP-00 states that form the SoT preamble are essentially absent or too brief for the SN65DSI83 to reliably detect, even though the overall LP-low region measured long enough. Additionally, the HS amplitude of 38 mV is far below the normal 105–122 mV range and falls under the 50 mV "absent" threshold, indicating the bridge almost certainly failed to lock onto valid HS data. Taken together — a 3 ns LP-exit violating the 50 ns spec and a sub-threshold HS amplitude — this capture strongly represents a genuine flicker event where the SN65DSI83 missed the SoT.
Capture 0104 [20260417_125605] — FALSE ALARM
YES
The critical issue here is the **LP exit → HS transition time of only 3 ns**, which is far below the 50 ns minimum required by the SN65DSI83. While the LP-low plateau itself measures 108 ns (above the 50 ns threshold), the 3 ns LP-exit duration indicates the LP-01/LP-00 preamble states are essentially absent or too brief for the bridge to properly detect the SoT sequence. Additionally, the **HS amplitude of 36 mV** is drastically below the normal 105–122 mV range and falls below the 50 mV "absent" threshold, meaning even if the bridge detected SoT, the HS data would be unreadable. The combination of a collapsed LP-exit transition and effectively absent HS signaling makes it nearly certain the SN65DSI83 missed this transmission, causing visible flicker.
Capture 0105 [20260417_125642] — FALSE ALARM
YES
The LP-low plateau of 108 ns is above the 50 ns threshold, but the LP exit → HS transition time of only 1 ns is critically below the 50 ns minimum specification. This means the LP-01/LP-00 states were essentially absent or too brief for the SN65DSI83 to properly detect the SoT sequence. Additionally, the HS amplitude of 34 mV is far below the normal 105–122 mV range and falls under the 50 mV "absent" threshold, indicating the bridge almost certainly failed to lock onto the HS data burst. The combination of a near-zero LP exit duration and effectively absent HS signaling strongly indicates a missed SoT event that would produce visible flicker.
Capture 0114 [20260417_130019] — FALSE ALARM
YES
The HS amplitude of 22 mV is critically below the normal 105–122 mV range and well under the 50 mV "absent" threshold, indicating the HS data burst was essentially not driven or not properly received. Additionally, the LP exit → HS transition time of only 2 ns is far below the 50 ns minimum specification, meaning the LP-01/LP-00 preamble states were too brief for the SN65DSI83 to reliably detect the Start-of-Transmission. Although the LP-low plateau itself measures 108 ns (above the 50 ns threshold), the combination of an effectively absent HS burst and a collapsed LP-exit duration strongly indicates the bridge failed to lock onto the SoT sequence, making visible flicker virtually certain.
Capture 0119 [20260417_130226] — FALSE ALARM
YES
The HS amplitude of 28 mV is critically below the normal 105–122 mV range and well under the 50 mV threshold, indicating the HS data burst was essentially absent or undetectable by the SN65DSI83 receiver. Additionally, the LP exit → HS transition of only 2 ns is far below the 50 ns minimum specification, meaning the LP-01/LP-00 preamble states were not held long enough for the bridge to recognize the SoT sequence. Although the LP-low plateau itself measured ~108 ns (above the 50 ns threshold), the combination of a near-zero HS amplitude and a 2 ns LP-exit duration strongly indicates the bridge failed to lock onto the HS burst, resulting in a missed frame and visible flicker.
Capture 0120 [20260417_130301] — FALSE ALARM
YES
The HS amplitude of only 26 mV (well below the normal 105–122 mV range and under the 50 mV "absent" threshold) indicates the HS data burst was essentially not driven or severely attenuated, meaning the bridge almost certainly could not recover valid data from this packet. Additionally, the LP exit → HS transition of only 2 ns is far below the 50 ns minimum specification, indicating the LP-01/LP-00 preamble states were truncated to the point of being undetectable by the SN65DSI83. Although the LP-low plateau itself measured 108 ns (above the 50 ns threshold), the combination of a near-absent HS burst amplitude and a critically short LP-exit-to-HS transition strongly suggests the bridge missed this SoT entirely, resulting in a dropped frame and visible flicker.
Capture 0136 [20260417_130928] — FALSE ALARM
YES
The HS amplitude of only 26 mV is far below the normal 105–122 mV range and falls under the 50 mV "absent" threshold, indicating the HS data burst was essentially not driven or severely attenuated—this alone would cause the SN65DSI83 to fail to decode the video packet. Additionally, the LP exit → HS transition time of only 2 ns is well below the 50 ns minimum specification, meaning the LP-01/LP-00 SoT preamble states were too brief for the bridge's LP receiver to reliably detect the start-of-transmission. Although the LP-low plateau itself measured 108 ns (above the 50 ns threshold), the combination of a near-absent HS signal and a critically short LP-exit duration strongly indicates the bridge missed or could not properly lock onto this HS burst, resulting in a visible flicker event.
Capture 0141 [20260417_131144] — FALSE ALARM
YES
The LP-low plateau of 108 ns meets the ≥50 ns requirement, but the LP exit → HS transition of only 3 ns is critically below the 50 ns minimum specification. This means the LP-01/LP-00 preamble states were essentially absent or collapsed into a single transient that the SN65DSI83 cannot reliably detect as a valid SoT sequence. Additionally, the HS amplitude of ~20 mV is far below the normal 105–122 mV range and falls under the 50 mV threshold, indicating the bridge almost certainly failed to lock onto the HS data burst. The combination of a missing LP exit transition and absent/negligible HS signaling strongly indicates a missed SoT event that would produce visible flicker.
Capture 0143 [20260417_131243] — FALSE ALARM
YES
Although the LP-low plateau itself measures ~108 ns (well above the 50 ns minimum), the LP-exit-to-HS transition time of only 1.0–1.3 ns is critically below the 50 ns specification minimum, indicating that the LP-01/LP-00 SoT preamble states are essentially absent or collapsed into an undetectable glitch. Additionally, the HS amplitude of 31 mV is far below the normal 105–122 mV range and falls under the 50 mV "absent" threshold, meaning the SN65DSI83 likely cannot reliably sample the HS data even if it did detect the SoT. The combination of a virtually instantaneous LP-exit transition and an abnormally low HS swing strongly indicates the bridge missed or failed to lock onto this transmission, making visible flicker highly probable.
Capture 0148 [20260417_131452] — FALSE ALARM
YES
Although the LP-low plateau itself measures 58.7–59 ns (above the 50 ns minimum), the LP exit → HS transition duration is only 1.7–2 ns, far below the 50 ns spec minimum. This means the LP-01/LP-00 states that form the SoT preamble are essentially absent or too brief for the SN65DSI83 to reliably detect. Additionally, the HS amplitude of 40 mV is well below the normal 105–122 mV range and falls under the 50 mV "absent" threshold, indicating the bridge likely never locked onto the HS data. The combination of a near-absent LP exit transition and sub-threshold HS amplitude strongly indicates the SN65DSI83 missed the SoT, making this a genuine flicker event.
Capture 0153 [20260417_131707] — FALSE ALARM
YES
The HS amplitude of only 30 mV (single-ended) is far below the normal 105–122 mV range and falls under the 50 mV "absent" threshold, indicating the SN65DSI83 likely cannot reliably detect the HS data burst at all. Additionally, the LP exit → HS transition time of just 1 ns is dramatically below the 50 ns minimum specification, meaning the LP-01/LP-00 SoT preamble states were essentially absent or too brief for the bridge's LP receiver to register the start-of-transmission. Although the LP-low plateau itself measured 108 ns (above 50 ns), the combination of a near-zero LP-exit duration and severely attenuated HS signaling strongly indicates the bridge missed this packet, producing a visible flicker event.
Capture 0165 [20260417_132157] — FALSE ALARM
YES
The HS amplitude of only 25 mV (single-ended) is critically below the normal 105–122 mV range and well under any reasonable detection threshold (~50 mV), meaning the SN65DSI83's HS receiver almost certainly cannot reliably detect the data payload even if the SoT were properly recognized. Additionally, the LP exit-to-HS transition of only 3 ns is far below the 50 ns minimum specification, indicating the LP-01/LP-00 states were essentially absent or too brief for the bridge's LP detector to properly sequence through the SoT preamble. While the LP-low plateau itself measured ~108 ns (above 50 ns), the combination of a near-absent LP exit duration and severely attenuated HS amplitude makes it virtually certain the bridge failed to lock onto this transmission, resulting in visible flicker.
Capture 0170 [20260417_132412] — FALSE ALARM
YES
The LP-low plateau itself measures 108 ns (≥ 50 ns), but the critical failure is the **LP exit → HS transition of only 4 ns**, far below the 50 ns minimum required for the SN65DSI83 to properly detect the LP-01/LP-00 SoT preamble states. Additionally, the **HS amplitude of 32 mV** is well below the normal 105–122 mV range and falls under the 50 mV "absent" threshold, indicating the bridge almost certainly did not lock onto the HS data burst. These two defects together — an essentially absent LP-to-HS transition time and a sub-threshold HS swing — mean the SN65DSI83 would miss the start-of-transmission, producing a visible flicker event.
Capture 0187 [20260417_133058] — FALSE ALARM
YES
The LP-low plateau of 108 ns meets the ≥50 ns requirement, but the LP exit → HS transition of only 4 ns is critically below the 50 ns minimum specification. This means the LP-01/LP-00 state machine progression is too compressed for the SN65DSI83 to properly recognize the SoT preamble. Additionally, the HS amplitude of ~30 mV is far below the normal 105–122 mV range and falls under the 50 mV "absent" threshold, indicating the bridge almost certainly failed to lock onto the HS data burst even if SoT were detected. The combination of a near-absent LP exit duration and effectively missing HS signaling makes this a clear flicker event.
Capture 0189 [20260417_133222] — FALSE ALARM
YES
The LP-low plateau of 27 ns is well below the SN65DSI83's required ≥ 50 ns minimum for reliable SoT detection, and the LP exit-to-HS transition of only 3 ns (versus the 50 ns spec minimum) confirms the LP-01/LP-00 preamble states were far too brief. Additionally, the HS amplitude of 40 mV is critically low—below the 50 mV "absent" threshold and far under the normal 105–122 mV range—indicating the bridge almost certainly failed to lock onto the HS data burst. Together, these three failures (insufficient LP-low dwell time, near-zero LP-to-HS transition, and sub-threshold HS swing) make it virtually certain the SN65DSI83 missed this SoT, resulting in a dropped video line or frame and visible flicker.
Capture 0193 [20260417_133416] — FALSE ALARM
YES
The HS amplitude of only 24 mV (single-ended) is critically below the normal 105–122 mV range and well under the 50 mV threshold for a valid HS signal, meaning the SN65DSI83's HS receiver almost certainly cannot reliably detect the data burst. Additionally, the LP exit-to-HS transition of only 3 ns is far below the 50 ns minimum specification, indicating the LP-01/LP-00 preamble states were not properly held long enough for the bridge to recognize the SoT sequence. Although the LP-low plateau itself measured 108 ns (above the 50 ns threshold), the combination of the essentially absent HS amplitude and the drastically short LP-exit duration means the bridge would fail to lock onto the HS transmission, producing a missed frame and visible flicker.
Capture 0217 [20260417_134343] — FALSE ALARM
YES
The HS amplitude of 30 mV is critically low—well below the normal 105–122 mV range and under the 50 mV threshold that indicates an essentially absent or failed HS burst. Additionally, the LP exit → HS transition duration of only 3 ns is far below the 50 ns minimum required by the SN65DSI83, meaning the bridge almost certainly cannot recognize the LP-01/LP-00 state transitions needed to detect start-of-transmission. Although the LP-low plateau itself measures 108 ns (above the 50 ns threshold), the combination of a near-absent HS signal and an impossibly short LP exit transition strongly indicates the SoT was not properly received by the bridge, making visible flicker virtually certain.
Capture 0226 [20260417_134724] — FALSE ALARM
YES
The HS amplitude of 29 mV is critically low — well below the SN65DSI83's differential detection threshold (normal range 105–122 mV), meaning the bridge almost certainly cannot reliably recover HS data from this burst. Additionally, the LP exit → HS transition of only 3 ns is far below the 50 ns minimum required for the bridge to properly recognize the LP-01/LP-00 SoT preamble states, even though the LP-low plateau itself measured 108 ns. The combination of a near-absent HS signal and an illegally fast LP-to-HS transition makes it virtually certain the SN65DSI83 missed this SoT entirely, producing a dropped frame and visible flicker.
Capture 0257 [20260417_135942] — FALSE ALARM
YES
The LP-low plateau of 27.3 ns is well below the SN65DSI83's required 50 ns minimum for reliable SoT detection, and the LP exit-to-HS transition of only 3.4 ns (versus the ≥50 ns spec) confirms the LP-01/LP-00 preamble states were far too brief for the bridge to properly recognize. Together, these two violations mean the SN65DSI83 almost certainly missed this start-of-transmission event. While the HS amplitude (118 mV) and LP-11 voltage (1.014 V) are within normal bounds—indicating the PHY itself is electrically healthy—the timing of the LP signaling sequence is critically deficient, making visible flicker on this frame highly likely.
Capture 0264 [20260417_140237] — FALSE ALARM
YES
The HS amplitude of 30 mV is critically low—well below the SN65DSI83's differential detection threshold (normal range 105–122 mV, and flagged absent at <50 mV)—meaning the bridge almost certainly cannot reliably detect or decode the HS data burst even if the LP-to-HS entry were perfect. Additionally, the LP exit → HS transition of only 3 ns is far below the 50 ns minimum specification, indicating the LP-01/LP-00 preamble states were not held long enough for the bridge's LP receiver to properly recognize the SoT sequence. While the LP-low plateau itself at 108 ns meets the ≥50 ns requirement, the combination of a near-absent HS signal and a collapsed LP exit timing makes it virtually certain the SN65DSI83 missed this transmission, producing a visible flicker event.
Capture 0280 [20260417_140922] — FALSE ALARM
YES
The DAT0 LP-low plateau is reported as **None** (absent/undetectable), which falls critically below the SN65DSI83's minimum 50 ns requirement for reliable SoT detection. Although the LP→HS sequence is marked "valid ✓" at the protocol level and LP-11 voltage is within spec at 1.015 V, the absence of a measurable LP-low plateau means the bridge's SoT detector almost certainly missed the HS entry event. Additionally, the HS amplitude is reported as **None**, suggesting the bridge never locked onto the HS burst, which is fully consistent with a missed SoT causing a dropped frame and visible flicker.
Capture 0281 [20260417_140958] — FALSE ALARM
YES
The critical failure here is the **LP exit → HS transition of only 4 ns**, far below the 50 ns minimum required by the SN65DSI83. Although the LP-low plateau itself measures 108 ns (above spec), the bridge needs to see distinct LP-01 and LP-00 states each held for adequate duration, and the 4 ns LP exit time indicates these states are being blown through too rapidly for reliable detection. Additionally, the **HS amplitude of 33 mV** is drastically below the normal 105–122 mV range and falls below the 50 mV "absent" threshold, meaning even if the bridge did detect SoT, the HS data would be unreadable. The combination of a non-compliant LP exit duration and effectively absent HS signaling makes this a clear flicker event.
Capture 0282 [20260417_141108] — FALSE ALARM
YES
The HS amplitude of 25 mV is critically below the normal 105–122 mV range and well under the 50 mV threshold, indicating the HS data burst is essentially absent or undetectable by the SN65DSI83 receiver. Additionally, the LP exit → HS transition time of only 1 ns is far below the 50 ns minimum specification, meaning the LP-01/LP-00 preamble states were not properly established even though the LP-low plateau measurement of ~108 ns appears nominally compliant. The combination of a near-zero HS amplitude and a missing LP exit sequence strongly indicates the bridge failed to detect and lock onto the SoT, making visible flicker virtually certain on this frame.
Capture 0284 [20260417_141207] — FALSE ALARM
YES
The LP-low plateau of 108 ns meets the ≥50 ns requirement, but the LP exit → HS transition of only 3 ns is critically below the 50 ns minimum specification. This means the LP-01/LP-00 states were not held long enough for the SN65DSI83 to properly recognize the SoT preamble. Additionally, the HS amplitude of 38 mV is well below the normal 105–122 mV range and falls under the 50 mV "absent" threshold, indicating the bridge likely failed to lock onto the HS data burst even if SoT were partially detected. The combination of a near-instantaneous LP-to-HS transition and essentially absent HS signaling amplitude strongly indicates a missed SoT event that would produce visible flicker.
Capture 0296 [20260417_141726] — FALSE ALARM
YES
The HS amplitude of 28 mV is critically low — well below the SN65DSI83's minimum differential detection threshold (typically ~70 mV single-ended equivalent), meaning the bridge cannot reliably distinguish HS data from noise even if the SoT is otherwise valid. Additionally, the LP exit → HS transition of only 3 ns is far below the 50 ns minimum specification, indicating the LP-01/LP-00 preamble states are essentially absent or too brief for the bridge's LP receiver to properly decode the start-of-transmission sequence. While the LP-low plateau itself measures 108 ns (above the 50 ns threshold), the combination of a near-zero LP-exit duration and severely attenuated HS amplitude means the SN65DSI83 almost certainly missed this HS burst, producing a flicker event.
Capture 0313 [20260417_142428] — FALSE ALARM
YES
The HS amplitude of only 24 mV (single-ended) is critically below the normal 105–122 mV range and well under the 50 mV threshold for a valid HS signal — the SN65DSI83 almost certainly cannot reliably detect or decode the HS data burst. Additionally, the LP exit-to-HS transition of only 3 ns is far below the 50 ns minimum specification, indicating the LP-01/LP-00 SoT preamble states were essentially absent or too brief for the bridge's LP receiver to properly recognize the start-of-transmission sequence. While the LP-low plateau measurement of 108 ns technically meets the ≥50 ns requirement, the combination of a near-absent LP exit duration and an unusable HS amplitude strongly indicates the bridge missed this packet, causing a visible flicker event.
Capture 0323 [20260417_142851] — FALSE ALARM
YES
The HS amplitude of only 30 mV (single-ended) is critically below the normal 105–122 mV range and well under the SN65DSI83's differential input threshold, meaning the bridge almost certainly cannot resolve valid HS data even if the SoT were detected. Additionally, the LP exit → HS transition of 3 ns is far below the 50 ns minimum specification, indicating the LP-01/LP-00 states were essentially absent or too brief for the bridge's LP receiver to properly track the SoT preamble. While the LP-low plateau itself measured 108 ns (above 50 ns), the combination of a nearly non-existent LP exit duration and severely attenuated HS signaling strongly indicates a failed or corrupt SoT handshake, which would cause the SN65DSI83 to lose packet synchronization and produce visible flicker.
Capture 0326 [20260417_143017] — FALSE ALARM
YES
The LP-low plateau of 194 ns is well above the 50 ns SN65DSI83 requirement, so by itself it should be sufficient for SoT detection. However, the critical failure here is the **LP exit → HS transition of only 1.2 ns** (spec ≥ 50 ns), meaning the LP-01/LP-00 states were traversed so rapidly that the bridge likely could not properly sample and recognize the SoT preamble. Additionally, the **HS amplitude of only 37.5–38 mV** is far below the normal 105–122 mV range and below the 50 mV "absent" threshold, indicating the HS data burst is essentially undetectable by the bridge receiver. The combination of a sub-spec LP exit duration and a critically weak HS signal makes it highly probable the SN65DSI83 failed to lock onto this transmission, causing a visible flicker event.
Capture 0339 [20260417_143551] — FALSE ALARM
YES
The LP-low plateau at 108 ns is above the 50 ns minimum, so that alone would be fine — but the LP exit → HS transition time of only 1 ns is critically below the 50 ns specification minimum. This indicates the LP-01/LP-00 states were either absent or so brief that the SN65DSI83 could not properly detect the SoT preamble. Additionally, the HS amplitude of 32 mV is far below the normal 105–122 mV range and falls below the 50 mV "absent" threshold, meaning even if the bridge detected SoT, the HS data would be unreadable. The combination of a near-absent LP exit duration and effectively missing HS signaling makes this a clear flicker event.
Capture 0341 [20260417_143654] — FALSE ALARM
YES
The LP-low plateau itself at ~108 ns is adequate (≥ 50 ns), but the LP exit → HS transition time of only 3 ns is critically below the 50 ns minimum specification. This means the LP-01/LP-00 states that constitute the SoT preamble are essentially absent — the lane jumps from LP-11 almost directly into HS mode, giving the SN65DSI83 no time to recognize the start-of-transmission sequence. Additionally, the HS amplitude of 36 mV is well below the normal 105–122 mV range and falls under the 50 mV "absent" threshold, indicating the bridge likely cannot reliably detect the HS data burst even if it did recognize SoT. The combination of a nearly instantaneous LP exit and severely attenuated HS signaling makes it highly probable the bridge missed this packet, causing visible flicker.
Capture 0355 [20260417_144230] — FALSE ALARM
YES
The LP-low plateau of 108 ns meets the ≥50 ns requirement, but the LP exit-to-HS transition of only 2 ns is critically below the 50 ns spec minimum, meaning the LP-01/LP-00 states were essentially absent or unresolvable by the SN65DSI83. Additionally, the HS amplitude of 32 mV is far below the normal 105–122 mV range and falls under the 50 mV "absent" threshold, indicating the bridge almost certainly failed to lock onto the HS data. The combination of a nearly instantaneous LP exit (2 ns vs. 50 ns required) and effectively absent HS signaling means the SN65DSI83 would not detect a valid SoT, producing a missed packet and visible flicker.
Capture 0368 [20260417_144749] — CONFIRMED FLICKER
YES
The HS amplitude of 32 mV is critically low — well below the SN65DSI83's minimum differential detection threshold (typically ~70 mV single-ended equivalent), meaning the bridge almost certainly cannot reliably distinguish HS data from noise. Additionally, the LP exit-to-HS transition of only 2 ns is far below the 50 ns minimum specification, indicating the LP-01/LP-00 preamble states were essentially absent or too brief for the bridge's LP receiver to properly sequence through the SoT detection state machine. While the LP-low plateau itself measures 108 ns (above the 50 ns threshold), the combination of a near-absent LP exit duration and severely attenuated HS amplitude strongly indicates the SN65DSI83 either missed the SoT entirely or could not lock onto the subsequent HS burst, resulting in a lost video line and visible flicker.