I designed some custom target for a MCU and currently having the problem, that I can’t use the predefined U(S)ART pins to go into the CW.
So, I guess there is no chance to use the simpleserial.
The goal is to glitch some complex computation, so I was thinking about doing the following in abstract:
- set trigger high
- to some computation
- set trigger low
- check if computation is erroneous
4.1) if it is, set GPIO3 high
- Waits for glitching trigger
1.1) Glitch on trigger high
1.2) Afterwards checks gpio3 (attempt to glitch successful / failed)
Well, I just found out the hard way you cant use the GPIOs as inputs to the CW.
So, I was searching around and found, that there may be a workaround in using the scope.trigger.triggers() to combine gpio4 (real trigger) and gpio3 (success indicator) with some logical combination:
How would you then at the CW side differentiate between both these events, as both simple trigger the CW-Lite.
Is it somehow necessary to disarm the CW in between?
I hope someone finds the time for a short reply.