STM32F4 RDP downgrade with #chipwhisperer Husky. You guys made it before me, but i knew it would be SAD trigger due to STM32F4 jitter :)

Orig tweet: https://twitter.com/marunmagesh/status/1652203313201397760

Last trigger on #chipwhisperer tried out, ETM trace parallel capture on K82F target.

Though the connection is wonky given how the ETM trace+debug connector on K82F target board needs to be connected to USERIO header.

Kinda surprised it worked given how sensitive parallel trace and clock are and how precisely it usually needs to be routed on boards with ETM trace+debug connector.

Got the results, but noticed a few bugs in the ETM trace notebooks:

- K82F has one address wrong for the precompiled binary, 0x3ef0 is right for SubBytes, but AddRoundKey should be 0x3eb8, not 0x3f1c
- `pc_sample_annotate` notebook tries to program for `simpleserial-ecc` not `simpleserial-trace` (then shows incorrect assert)
- orbuculum invocations has parameters like -P that are in none of my orbuculum builds (old one, v2.0.0, some devel version)

Wasn't really succesful with raw trace+orbuculum, letting CW to decode seemed to work. (But AddRoundKey address on the first graph is not entered correctly, I just found out now)

Trying out TraceWhisperer from #chipwhisperer Husky. I had to resort to STM32F303 over SWO instead of parallel trace, since the STM32F303 UFO target doesn't have the TRACED and TRACECLK pins exposed.

Though with non-raw trace it seems to do something - need to re-check later with raw+orbuculum.

Unfortunately can't use JTrace for the check due to the missing TRACE pins, but there's some data that look like screenshots from the example.

Debugging #chipwhisperer SAD multiple trigger. Finally got a slight understanding what is wrong eith demo code not matching up to my build, different compliler.

So trying to set up the reference wave correctly to match my build

Finally figured out how to make #chipwhisperer work with bokeh graphs in PyCharm Professional.

So now you can also debug/step/inspect variables in cells and have graphs working.

Fix to make bokeh graphs work is changing this line in notebooks:

output_notebook(INLINE)

to

output_notebook()

(don't forget to mark notebook trusted - javascript won't work otherwise)

Finally got #chipwhisperer Husky.

Lot of features to check out, but also some things I wasn't very aware about before. E.g. didn't expect to not have USB 3 (it's documented but only found out after having device), which limits streaming capture (can't find example notebook for it either).

Now on second demo 02 husky triggers, but I keep getting scope.errors I don't see explained in docs in both demos I tried. The scope.errors.clear() sometimes works weird.

With both CW308 and CW313 it has lot of opportunities, trying to work through it to get all the potential.