Jacob Rosenthal

Took a look. PWM (tc4 tcc0) pygamer looked consistent. But timer tc3 panics ``` 18:51:35.272 panicked at 'internal error: entered unreachable code', /home/jacob/Downloads/atsamd/hal/src/common/thumbv7em/timer.rs:107:22 ``` I havent dug in further yet

embedded-time got some nice cleanups after rtic started implementing it . Might be worth another look

I'm getting this as well with daplink so its not just jilnk. That said switching back to a jilnk and a basic nrf-hal blinky example, even on nightly, I cant...

@Tiwalun Ubuntu 21.10 `Linux j 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 08:59:28 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux`

I believe this is fixed as well by https://github.com/probe-rs/vscode/issues/26#issuecomment-1016870363 but perhaps @Dirbaio wants to confirm

Sorry for the noise, I guess this is still something unrelated

Couple things in the pipeline im paying attention to that could clean up our terrible memory usage https://github.com/fdehau/tui-rs/pull/349 https://github.com/fdehau/tui-rs/pull/361

Instead of onerous and impossible configuration, presumably we could do something like japaric's zero cost deferred formatting for logging thing (only link I could find) https://github.com/rtic-rs/rfcs/issues/31. We could configure the...

Obviously the naive and maybe even a good initial solution would be to just deserialize some graphing config struct over the wire first that explains all that configuration.

I guess cortex-debug in vscode has graphing support via itm and json configuration https://github.com/Marus/cortex-debug/wiki/SWO-Output