Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 8037

General • Re: Using the Pico 2 W as a Debug Probe

$
0
0
Thnaks, but there is also - https://github.com/raspberrypi/pico-sdk/blob/master/src/boards/include/boards/pico2_w.h#L88 -

Code:

#ifndef CYW43_WL_GPIO_LED_PIN#define CYW43_WL_GPIO_LED_PIN 0#endif
I would expect the application code to be able to handle both GPIO connection and via CYW43 with something like -

Code:

#ifdef PICO_DEFAULT_LED_PIN     ... / Via GPIO#else    #ifdef CYW43_WL_GPIO_LED_PIN         ... / Via CYW43    #endif#endif
I couldn't find any reference to either "PICO_DEFAULT_LED_PIN" or "CYW43_WL_GPIO_LED_PIN" in the 'debugprobe' source but that handling could be part of Pico SDK functions.

But there is simply doesn't support Pico W, Pico 2W or any third-party boards -

Code:

CMake Error at CMakeLists.txt:66 (message):  Unsupported board pico_w

Code:

CMake Error at CMakeLists.txt:66 (message):  Unsupported board pico2_w
So currently one has to build for Pico or Pico 2 and that will expect the LED to be controlled by the GPIO, which it won't be when those images are run on a Pico W or Pico 2W, as the OP notes, but the code should still run and work as expected.

That's a hard-check in 'CMakeLists.txt' so can be edited to allow Pico W, Pico 2W, and third-party boards to be built. Those build but whether they can and do control the LED I don't know. I would guess not or the 'CMakeLists.txt' would have allowed building for anything. It may be that they don't even load the CYW43 firmware to allow the LED to be controlled.

Maybe that simply wouldn't work with the code as is, and hence the hard-check. It would require more investigation. I might take a closer look later.

Statistics: Posted by hippy — Sat Feb 22, 2025 12:57 pm



Viewing all articles
Browse latest Browse all 8037

Trending Articles