and diffed the output, noticed some 'Error' lines in the first 2 runs:
run 1:
Warn : Unexpected idcode after end of chain: 85 0xfffffa20
Error: double-check your JTAG setup (interface, speed, ...)
Error: Trying to use configured scan chain anyway...
Error: xc6s.tap: IR capture error; saw 0x03 not 0x01
Warn : Bypassing JTAG setup events due to errors
DNA = 110000001100000011000000110000001100000011000000110000001 (0x181818181818181)
run 2:
Info : JTAG tap: auto3.tap tap/device found: 0xffffffd1 (mfg: 0x7e8 (<unknown>), part: 0xffff, ver: 0xf)
Error: xc6s.tap: IR capture error; saw 0x03 not 0x01
Warn : Bypassing JTAG setup events due to errors
DNA = 110000001100000011000000110000001100000010011011011000010 (0x1818181818136c2)
run3: (no 'error')
Info : This adapter doesn't support configurable speed
Info : JTAG tap: xc6s.tap tap/device found: 0x44028093 (mfg: 0x049 (Xilinx), part: 0x4028, ver: 0x4)
DNA = 100110110110000100011001100011000111100000011111101011000 (0x136c23318f03f58)
(Error: double-check stood out as maybe a clue to why f--lash-image needs 3 runs ((it seems to always be 3 on my test rig)))
I power cycle the opsis, run this 3 times,
hdmi2usb-mode-switch -v --by-type opsis --flash-image image-gateware+bios+firmware.v0.0.4-489-geaab51f.opsis.hdmi2usb.lm32.bin
and diffed the output, noticed some 'Error' lines in the first 2 runs: run 1:
run 2:
run3: (no 'error')
Here are some nice diff vizs: https://www.diffchecker.com/iGUEqTq8 https://www.diffchecker.com/cvbn3Wnz
and all the outputs:
1.log 2.log 3.log