Peter Harper
Peter Harper
ok - I am getting callbacks. But the callback happens in the irq. I think you'll have a problem reading a character in an irq as we try and claim...
The inconsistency does seem unfortunate. But presumably it would be too dangerous to fix now?
To me, the function names gpio_set_irq_enabled and gpio_set_irq_enabled_with_callback imply they might both call irq_set_enabled . It seems inconsistent that gpio_set_irq_enabled_with_callback calls irq_set_enabled but gpio_set_irq_enabled does not.
Any comment @andygpz11 ?
Is the alarm_id returned
Glad you found the issue. I guess I can close this unless you think there is a bug in the sdk.
I wonder if it's another case of this https://github.com/raspberrypi/pico-sdk/issues/1552
Yes, you're probably right - it needs to be documented. > I've successfully managed to convert the NTP client example Pico W example from its original LwIP raw API form...
This is a known problem with the WiFi firmware. It should have been documented somewhere (probably not). We're hoping for a fix eventually
No. Infineon are still working on it.