CW1200 and ChipShouter glitch trigger setup problem

Hello,

I want to glitch a specific target using the ChipShouter in combination with the CW1200. I’ve the following setup in mind:

+---------------+                   +---------------+                     +----------------+
|               | Trigger       IO4 |               | AUX?           TrgIn|                |
|   Target      |                   |   CW1200      |                     |    ChipShouter |
|               +------------------>+               | +-----------------> |                |
|               |                   |               |                     |                |
+-------+-------+                   +---------------+                     +---------+------+
        ^                                                                           |
        |                                                                           |
        |                                                                           |
        |                                                                           |
        +---------------------------------------------------------------------------+

                                      EM-Glitch

The target generates a trigger signal. After that trigger, the CW1200 has to generate a precise delay for this signal, and trigger the ChipShouter after that delay.
I couldn’t make this setup work by using the Crowbar GlitchOut of the CW1200 as Trigger for the CS.
If I look at the Trigger Routing Screen of the CW1200, it looks like it’s possible to route the glitch out signal to AUX.
How can this be done in the software?

Or is there a different, better way to generate the trigger signal for the ChipShouter by the CW1200?

Thanks for you help,
Nils

Hello,

The crowbar glitchout “should” work - actually that is what I’m using as a triggering method for 80% of my ChipSHOUTER usage! So could troubleshoot that… although due to the MOSFET in the way with the crowbar it doesn’t go as narrow (or requires some effort in mapping commanded glitch width --> actual width). I assume that is the problem you are seeing (and not that it doesn’t work at all). If you aren’t getting it to work at all let me know, as it should work ‘fairly’ well.

As a quick work-around - are you using the CLKOUT (HS2) right now? You can definitely route a glitch out to that, and if you’ve got a CW1200 it should have come with the breakout board that has the SMA on the HS2. That should “cleanly” connect through as you want…

But on the aux signal - I’ll double check. I know we had some issue w/ the FPGA build, so I think it was removed (I see some of the SMAUX logic commented out - the FPGA code is all in the git repo). The FPGA tools tend to not like when we route these clocks all over the place with muxes. We may end up just needing to offer multiple bitstreams you switch between when you want to use different features, which have more fixed clock routing. This actually isn’t too bad to do, as the bitstreams get reloaded on connect anyway. And I think 99% of the time you’re using the SMAAUX for a specific use given your setup - that is there isn’t a need to switch half-way through your analysis for SMAAUX being the glitch out to SMAUX being the clock input for example.

Thanks,

-Colin

Hi Colin, thank you very much for your answer. We could resolve our problems in the meantime. We were able to use the glitch out on cw1200. We reversed your youtube video about Bam Bam for that :wink: so we could find the proper output settings.

Thanks a lot.

Nils