I am in the midst of my first attempts with the ChipShouter, and I’m using a CW Lite for trigger. For some reason I keep getting fault_trigger_glitch fault. I am not sure how to address that at the moment. Here’s my code:
for i in range(0, 1):
scope.glitch.ext_offset = 2000
scope.glitch.repeat = 1
cs.armed = 0
cs.clr_armed = 1
scope.io.glitch_lp = True
scope.arm()
shift_jtag_pwd_under_reset(jprog, FALSE_PASSWORD, attempts=1, reset=True) # Trigger toggled here
scope.io.glitch_lp = False
if ret:
print('Timeout - no trigger!')
Update: Managed to get the device working. If someone is interested, I will post a minimal working script.
However what happens now is that the CS latches fault_temp_sensor very often. Glitching frequency is about 2 times per second; after about a minute I get that temperature error. Is there a minimal glitching rate? Two glitches per second appear to be very limited, I hope that’s not a hardware limitation. I am not using air cooling.
Here’s the device setup. Take a look at the temperature fields:
EDIT: Also, what ChipSHOUTER firmware verison are you on? The original trigger_safe implementation was bugged, but has since been fixed. I can get some new firmware to you if necessary.
@Alex_Dewar Hi, can you let me know if I am using the most recent CS firmware? I am experiencing a lot of faults, and the temperature values do not seem right.