Dániel Buga

Why would you allow overriding the handler of the async API? Why would you require the async api to allow registering an irq handler? And thirdly, why would you need...

So what I have in mind: - Allow unsafely replacing the global irq handler by calling `io.set_interrupt_handler`. This needs to be done before moving out the first pin, so it's...

This also means that RTIC, when it sits on the GPIO interrupt, is incompatible with a significant portion of our API (any async GPIO, any GPIO interrupt handling). How can...

We can add a `bind_io_interrupts: IoInterrupt` to `esp_hal::Config` where `IoInterrupt` is an `enum` and move the IO_MUX initialisation into `esp_hal::init`. That way we can remove `Io::new` completely and just expose...

Are you really asking why I want to hide something that the users need to type out currently, but don't really need?

GPIOs can't really follow suit. To do so would require the ability to set a handler for each pin, which we can't really do (well, unless hackery, but that again...

IMO this should be part of the book and/or future guides, not HAL documentation. We should mention what bootloader we use/expect, but it's somewhat tangential here.

The VA106 is a custom target, right? You might need to write a custom debug sequence to support it fully. It's interesting that we can read incorrect IDCODE register values...

> J-Link found 2 JTAG devices, Total IRLen = 9 Do you know why there are two devices? Maybe the one you're looking for isn't even the first one. It's...

probe-rs tries to connect to the first JTAG device it finds. In this case it's whatever the `Silicon Space Technology` IP is. The datasheet offers us a few hints: ...