I'm wondering about using the Pico-W's LED as a Wifi activity indicator. Simplest case, as a tx indicator.
First up, I assume that the Cyw43 firmware and driver do not support this out of the box.
i.e. That there's not some (undocumented) way to command the Cyw43 to autonomously use the LED GPIO itself as an activity indicator (rather than expose it simply as a host-controllable GPIO pin).
It's quite unsatisfying to have to use the Cyw43 SPI link for the host to control the LED in response to the device's own activity, but it looks like that's the way it's gotta be.
Given this, as far as I can tell the SDK's packaging and integration of the Cyw43 driver and lwip do not expose any kind of activity callback.
It does look like I might be able to use the trace macro for this purpose - instead of printf-ish, use it to control the LED according to the reported rx/tx activity - but I'd prefer something less hacky.
As a last resort I could modify driver or stack code to implement this, but I'd rather avoid that.
Any thoughts?
First up, I assume that the Cyw43 firmware and driver do not support this out of the box.
i.e. That there's not some (undocumented) way to command the Cyw43 to autonomously use the LED GPIO itself as an activity indicator (rather than expose it simply as a host-controllable GPIO pin).
It's quite unsatisfying to have to use the Cyw43 SPI link for the host to control the LED in response to the device's own activity, but it looks like that's the way it's gotta be.
Given this, as far as I can tell the SDK's packaging and integration of the Cyw43 driver and lwip do not expose any kind of activity callback.
It does look like I might be able to use the trace macro for this purpose - instead of printf-ish, use it to control the LED according to the reported rx/tx activity - but I'd prefer something less hacky.
As a last resort I could modify driver or stack code to implement this, but I'd rather avoid that.
Any thoughts?
Statistics: Posted by jeremyd — Thu Feb 20, 2025 12:56 pm