Björn Quentin
Björn Quentin
You should be able to pass `&mut` into the input pin driver and then drop the driver before using it as the wakeup pin I guess - on mobile right...
I think we at least need to document the general pattern (which applies to all drivers) somewhere. It's really not obvious how to do those things
One thing that probably would work right now already is using our internal implementation details (I'm not sure if those should be kept public in future) ```rust struct HoldGpioPin where...
Not sure if we should implement the more or less deprecated `IoPin` or better wait for its return in EH-1.x
It's at least not very unexpected. Users currently could use the `custom-halt` feature to implement their own halt functionality. I could also imagine this to be a common enough case...
I can reproduce it and the problem is halting core 0 (pro-cpu) I currently don't see a way to stop core 0 from continuing when an exception/panic occurs on core...
For me (on Windows, esptool 4.7) it cannot reset the board in that situation
I remember we had interrupts and gpio working in January or February already
Suggestion for an additional topic: TLS - preferably via embedded-tls Q: What DevKit to use? RustBoard is probably still a good choice since it includes a temperature sensor
Thanks for the detailed outline - pretty much what I had in mind. I am wondering if the order of "Wi-Fi Provisioning" and "Publishing Data to an MQTT Broker" should...