Setting pulse width when using hardware trigger from ChipWhisperer-Lite

[itewqq]

I am using chipwhisperer and chipsohuter jointly and I would like to know how to modify the output pulse width of the chipshouter?

I have tried to modify the scope.glitch.repeat parameter on the chipwhisperer side and the cs.pulse.width parameter on the chipshouter side, but it doesn't look like this is working from the oscilloscope.

[colinoflynn]

What widths are you testing? FYI the pulse width gets highly limited by the physical coil parameters. Page 20/21 has this graph of the user manual that shows the limits you can expect.

I have tried to modify the scope.glitch.repeat parameter on the chipwhisperer side and the cs.pulse.width parameter on the ? chipshouter side

Using the mode as glitch.output = enable_only then modifying repeat should give a longer & longer input signal which translates to a longer output. Trying modifying the repeat to extremes as well (e.g., 10 vs 10000).

The cs.pulse.width parameter only takes effect if you call the glitch on the ChipSHOUTER API itself, the cs.pulse.width is ignored for the external input. The external input is a fully hardware path that basically mirrors the input on the external input (the MCX input on the ChipSHOUTER) to the MOSFET gate itself.

[itewqq]

Thanks for the fast reply!

Using the mode as glitch.output = enable_only then modifying repeat should give a longer & longer input signal which translates to a longer output. Trying modifying the repeat to extremes as well (e.g., 10 vs 10000).

This is very important information and much appreciated. I'll give it a shot :smiling_face_with_tear: