pico w isn't supported?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c, cmake
- Domain
- build-system, embedded-iot
Research direction
Start with src/picoprobe_config.h and src/led.c, then inspect the CMake configuration that defines PICOPROBE_LED. Compare the required LED and SWD pin settings for Pico W with the current picoprobe configuration. Done means picoprobe builds for Pico W without the undefined PICO_DEFAULT_LED_PIN or PICOPROBE_LED errors.
Written by the indexing model from the issue text.
Description
Hi,
I tried to compile picoprobe for the pico w. Anyways, the pins for LED and SWD have changed on the pico w. Is there already a common solution for this? Else I would change the picoprobe source to be compatible with the pico w.
C:\pico\picoprobe\src\picoprobe_config.h:68:2: error: #error PICO_DEFAULT_LED_PIN is not defined, run PICOPROBE_LED=<led_pin> cmake
68 | #error PICO_DEFAULT_LED_PIN is not defined, run PICOPROBE_LED=<led_pin> cmake
| ^~~~~
C:\pico\picoprobe\src\led.c: In function 'led_init':
C:\pico\picoprobe\src\led.c:39:15: error: 'PICOPROBE_LED' undeclared (first use in this function); did you mean 'PICOPROBE_H_'?
39 | gpio_init(PICOPROBE_LED);
| ^~~~~~~~~~~~~
| PICOPROBE_H_
C:\pico\picoprobe\src\led.c:39:15: note: each undeclared identifier is reported only once for each function it appears in
C:\pico\picoprobe\src\led.c: In function 'led_task':
C:\pico\picoprobe\src\led.c:49:18: error: 'PICOPROBE_LED' undeclared (first use in this function); did you mean 'PICOPROBE_H_'?
49 | gpio_put(PICOPROBE_LED, !((led_count >> LED_COUNT_SHIFT) & 1));
| ^~~~~~~~~~~~~
| PICOPROBE_H_
C:\pico\picoprobe\src\led.c: In function 'led_signal_activity':
C:\pico\picoprobe\src\led.c:55:18: error: 'PICOPROBE_LED' undeclared (first use in this function); did you mean 'PICOPROBE_H_'?
55 | gpio_put(PICOPROBE_LED, 0);
| ^~~~~~~~~~~~~
| PICOPROBE_H_
NMAKE : fatal error U1077: "C:\PROGRA~2\ARMGNU~1\1142DA~1.3RE\bin\AR19DD~1.EXE": Rückgabe-Code "0x1"
Stop.
NMAKE : fatal error U1077: ""C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.33.31629\bin\HostX86\x86\nmake.exe"": Rückgabe-Code "0x2"
Stop.
NMAKE : fatal error U1077: ""C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.33.31629\bin\HostX86\x86\nmake.exe"": Rückgabe-Code "0x2"
Stop.
Thx
Kind regards,
Pingu
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 363
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/debugprobe
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
raspberrypi/debugprobe#210 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
raspberrypi/debugprobe#206 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
raspberrypi/debugprobe#202 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
raspberrypi/debugprobe#196 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
raspberrypi/debugprobe#185 · 2 comments ·
All issues in raspberrypi/debugprobe
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zephyrproject-rtos/zephyr#119726 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
api7/lua-resty-saml#63 ·
-
[Bounty proposal] fix(web): memory insights count an evening memory on the next day ($25 proposed) Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BasedHardware/omi#15320 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·