I had, which is why I was able to say it suggested it should be easy - https://github.com/rgrr/yapicoprobe/blo ... led.c#L128I don't think it's using "the WLED", but you can check that.
Code:
static void led(uint8_t state){#ifdef TARGET_BOARD_PICO_W cyw43_arch_gpio_put(CYW43_WL_GPIO_LED_PIN, state);#elif defined(PICOPROBE_LED) ... gpio_put(PICOPROBE_LED, state);#endif} // ledThat was one of my concerns but, if it's okay for 'yapicoprobe', it should equally be okay for 'debugprobe'. Especially as 'yapicoprobe' is interacting with the LED a lot more than 'debugprobe' would. If not there's that fall back to turning the LED on with the first connection and then disabling the driver and/or chip.The problem with CYW43 driver is that is using PIO and DMA, which can interfere with SWD, ADC, logic analyzer etc.
I guess the thing to do is try it. I have been meaning to get to grips with SWD debugging and this appears to be ideal motivation. It also seems the perfect project to get to grips with FreeRTOS as well. Two birds with one stone, and maybe three if I can adopt the 'yapicoprobe' multi-state LED concept to make that more useful than just a USB connected indicator.
I'll let you know how I get on.
Statistics: Posted by hippy — Sun Feb 23, 2025 1:28 am