Thank you Alex! Actually, an update is also coming out really soon (within days) to accommodate the latest crates versions and changes.

Regarding your question, one thing you can do is check each global GPIO button wrapper individually with if statements in the GPIO handler. This means that just like there is a clear_interrupt method being used on G_BUTTON, ' there is also anis_interrupt_set` method you can use that tells you if this particular GPIO was the one firing the interrupt. So, when entering the handler, you would check each button individually to determine the source of the interrupt. Within the if statement body, you would associate the code for each button.

Omar Hiari

First of all, thank you for reading and reacting to feedback. This is rare and highly appreciated.

I would like to share some thoughts... .

First of all, I would like to suggest to add an additional mentoring subscription, to allow office hours or short video-calls. I understand this will require additional time from you, but it would be beneficial to developers, like myself, who are facing problems, which are serious bottlenecks. I am not talking about solving our problems for us, but more like mentoring and pointing out directions.

I for one, would be prepared to pay a subscription of USD75 to USD100 per month, to get a direct line to you as a mentor, during my learning process. I think this would require 2 to 4 - 15mins mentoring interventions per month. I am open to your suggestions as well.

I don't know about other people learning Rust embedded and what issues they face, but in my situation I see the following:

• the Rust embedded eco-system is changing at a fast pace, and code and examples, are outdated almost immediately. (as an example I have an esp32s3, and the examples don't work ... and I have been **ing to get embassy to simply compile:). In the end I just ordered a esp32c3 to simply try.

• too many books and tutorials focus on explaining libraries, instead of teaching patterns, though-processes and giving you the tools to build libraries yourself.

You already have a few blogs where you go deeper into developing your own pac, hal, ... . Although this is more advanced, this is what I am looking for the most. Because by understanding how to build a hal-driver, you can actually get the skills to deeply understand Rust embedded.

I also think that debugging using probe-rs and gdb are essential skills, needed for embedded. At this moment the information and docs about that, is really lacking. I use neovim with probe-rs, gdb, and it's been hell to make this work:(.

Another suggestion is to create a 3rd book, debugging embedded rust apps. I for one would be happy to pay an additional subscription for that.

Apart from additional income, this would also enable you to improve the books on Rust, and make them state-of-art teaching ressources.

Kind regards, Alex K