Closed eMUQI closed 1 week ago
In the Pico W the LED is not connected to the microcontroller (RP2040 or RP2350) but to the WiFi/BT chip (CYW43439 ), so you cannot control it by accessing the microcontroller registers (as digitalWriteFast does). The normal digitalWrite tests this special case and instead of using the normal digital IO it sends a command to the CYW43439.
You can try undefining LED_BUILTIN before including IRRemote:
#define SEND_PWM_BY_TIMER
#undef LED_BULTIN
#include <IRremote.hpp>
You still get a warning that LED feedback is disabled.
Thanks, @dquadros . This is a code issue with the IR library using a call that's not legal on the Pico W because the LED is not accessible by the RP2040 chip directly. You could try undefining the value as suggested, or simply replacing digitalWriteFast
with digitalWrite
would work. (Also, because the LED is connected to the WiFi chip, it is relatively slow to update compared to the real GPIOs.)
Hi there,
I tried running the following code on Raspberry Pi Pico, Pico W, and Pico 2:
The code compiled and ran successfully on both Pico and Pico 2. However, when compiling on Pico W, I encountered the following warnings:
I’m surprised to see this difference between the Pico and Pico W, as I expected them to behave similarly when no networking features are involved (please correct me if I’m wrong).
I’ve raised a related discussion in the IRremote repository, where one of the maintainers suggested that this might be a design oversight. Hence, I’m submitting it here for further clarification.
Link to the discussion: https://github.com/Arduino-IRremote/Arduino-IRremote/discussions/1267#discussioncomment-10974259
Is there a way to suppress this warning, or could this be an unintended design issue?
Thanks in advance for your assistance!