I’m using the V4 to perform some clock glitching on an external target, i.e. non-tutorial targets, using the approach discussed here with the CW1200.
I have a couple of questions:
In the script aux_reset_cw1173.py, # Delay between arming and resetting, in ms, is delay_ms = 1500. Suppose my CW1200 resets after arming, how does this delay_ms affect the glitching process?
What causes the CW1200 to reset the target? Upon completion of the glitch? Or is this configure by some timeout or delay?
Will there by a problem if the reset point and trigger point are 5 ms apart?
I also encountered the following intermittent warnings:
WARNING:Trigger not found in ADC data. No data reported!
WARNING:Captured trace in “ChipWhisperer/OpenADC - Channel 1” has len=0
WARNING:Trace too short (length=0) This MAY SUGGEST DATA CORRUPTION
WARNING:Padding with 5000 zero points
Please correct me if I’m wrong. I understand the CW1200 glitch process as follows:
a. Starts with the arming of CW1200, then wait delay_ms. (If I shortened this to say 100ms, will there be a problem?)
b. Resets target, then wait for external trigger (Does the CW1200 wait infinitely or is there like a timeout defined?)
c. Execute glitch parameters, then reset (Does the CW1200 reset the target immediately after the glitch or it waits for some defined delay?)
Is clock glitching even possible on a target that has an external crystal oscillator with internal PLL? E.g. STM32 system clock running at 120MHz derived using PLL from external crystal 8MHz.
Thanks in advance =)