I am currently voltage glitching a custom target (mostly unsuccessfully), however, I have what I consider to be a dangerous problem! With some specific glitch settings, the crowbar gets stuck and I cannot reset it without unplugging the CW-Lite from the USB port.
So much so that it burnt out the shunt resistor and melted the target’s power wires.
The glitch log:
19:31:43.734 [45269/450000] w=27 o=1 ext=905361 | 7.5/s ETA 53731s | 496 hits 1042 resets 0 errs
CMD $01 response (10 bytes):
0000: 01 01 FF FF FF FF 57 15 19 3F
.......................................................................
19:31:52.550 HIT [45341/450000] w=27 o=1 ext=906801: OK
0000: 06 06 00 00 00 00 00 00 00 00 3F
...........
19:31:53.857 [45352/450000] w=27 o=1 ext=907021 | 7.5/s ETA 53712s | 497 hits 1042 resets 0 errs
CMD $01 response (10 bytes):
0000: 01 01 FF FF FF FF 57 15 19 3F
........................
19:31:57.251 HIT [45377/450000] w=27 o=1 ext=907521: TIMEOUT
(empty)
19:32:04.333 [45377/450000] w=27 o=1 ext=907521 | 7.5/s ETA 53772s | 498 hits 1042 resets 0 errs
CMD $01 response (0 bytes):
(empty)
19:32:08.408 ERR [45378/450000] w=27 o=1 ext=907541: got 0B: empty
19:32:10.477 ERR [45379/450000] w=27 o=1 ext=907561: got 0B: empty
19:32:12.518 ERR [45380/450000] w=27 o=1 ext=907581: got 0B: empty
19:32:14.562 ERR [45381/450000] w=27 o=1 ext=907601: got 0B: empty
19:32:16.634 ERR [45382/450000] w=27 o=1 ext=907621: got 0B: empty
19:32:48.176 HIT [45399/450000] w=27 o=1 ext=907961: TIMEOUT
(empty)
19:32:48.567 [45399/450000] w=27 o=1 ext=907961 | 7.5/s ETA 54137s | 499 hits 1042 resets 21 errs
CMD $01 response (3 bytes):
0000: 01 01 00
19:32:48.966 HIT [45400/450000] w=27 o=1 ext=907981: TIMEOUT
(empty)
19:32:49.579 HIT [45401/450000] w=27 o=1 ext=908001: TIMEOUT
(empty)
The settings:
scope.glitch.clk_src = “clkgen”
scope.clock.adc_src = “clkgen_x1”
scope.glitch.output = “glitch_only”
scope.glitch.repeat = 1
scope.glitch.trigger_src = “ext_single”
scope.clock.clkgen_freq = 10.25e6
WIDTH_RANGE = range(27,28,1)
OFFSET_RANGE = range(1,45,5)
EXT_RANGE = range(1, 1000000, 20)
ATTEMPTS = 1
scope.io.glitch_hp = True
scope.io.glitch_lp = True
I first noticed it happening when the width setting was set to 0, but never figured out why. So I avoided that value but then it happened again with the above (w=27 o=1 ext=907521).
Has anyone seen this before? Anyone know why this might happen?