Jonathan Pallant

That's caused by an update to `critical-section` and isn't a flip-link bug (although perhaps we need to bump some dependencies in our example project). The update resolves an unsoundness bug,...

Controversial thought perhaps, but seeing as the module on the top-side already has the Espressif logo on it, you could shrink the Espressif logo on the bottom-side to make room...

Putting the QR code or some other link on the box would be great. How were you planning on shipping/distributing the esp-rust boards?

Ah, I meant in an ESD bag or in a box like the ESP8684-DevKitM-1 pictured above?

I think I'm falling over the same issue, which I wrote up as #77

See also #117

Yes. At worst it should be: ``` let clocks = init_clocks_and_plls( [...] ).ok().unwrap(); let mut delay = cortex_m::delay::Delay::new(core.SYST, clocks.system_clock.into()); ``` Don't forget your example requires I think two traits to...

There's some build failures, and we should pull traits from the source (embedded-hal) rather than the weird duplicate the rustc suggests (something something cortex-m thing-with-underscores). But I really like the...

How do we control which cores get which interrupts? Do all interrupts go to both cores, and it depends on which interrupts are enabled in each of the two NVICs?

Do we expose the unused top 5 interrupts in the `Interrupts` enum? Perhaps we should, just for RTIC purposes.