Adam Greig

I double checked this in https://github.com/rust-embedded/cortex-m/issues/325#issuecomment-1421809232 and indeed we currently only delay half the required time on CM7; the fix in #312 doesn't fully account for the core being able...

The nuisance is that it does change with architecture, in particular Cortex-M7 has a dual-issue pipeline which means two instructions may be retired per clock cycle in some cases. As...

Those two examples were the exact same binary on the same target - the CPU isn't something we know at compile time. Possibly we should just document that it will...

I did finally get my wch-link probe so in principle I'm now in a position to try and get that working too, but it might be worth getting this PR...

I've rebased onto master. I'll see if I can try and get wch-link working this weekend...

On my wch-link, I have a different USB descriptor, that has an interface association with a function "CMSIS-DAP" but sadly no CMSIS-DAP in any interface strings, which means I need...

In the end we merged #1142 to get it in 0.14 for orbtrace and similar probe support, but it still doesn't work with wchlink. Though it seems like we might...

It's not currently implemented. It would be simple to spread out encoding or decoding of entire codewords between cores, and since any single codeword will encode or decode pretty quickly...

I guess we could have `TryFrom for core::time::duration` while we're about it, too. Probably can't make either infallible since I guess you could have a fugit Duration that's u64 backed...

What do we think about making fugit -> core infallible? In principle an fugit's HoursDurationU64 can express a longer duration than core's Duration, which would have to fail or saturate,...