Help! I am at a complete loss here making my first steps with the Pi Pico WH 2040 board. I am following the instructions in the Getting Started Guide (https://datasheets.raspberrypi.com/pico ... h-pico.pdf) to debug a project using the Debug Probe and every example gets stuck in the same place - calls, some layers down the call stack in time.c, which in turn executes the inline in time.h and there execution gets stuck. It never returns.
The code I am using is the unmodified blink example from GitHub (https://github.com/raspberrypi/pico-exa ... wifi/blink), as created by the VS Code extension as described in the docs. The board is set to pico_w, all other settings are default. Really, I am following the docs as closely as I can manage. I am debugging using VS Code extension as in the docs.
This is running on an Intel Mac, macOS Sonoma 14.6.1 using a new Pi Debug Probe straight out of the box, I only updated the firmware following the instructions. Compiling, running, and debugging all seem to work fine - can run, set breakpoints, single step. I have tested with two 2040 boards, with same results on each.
Putting the 2040 into BOOTSEL mode by pressing the button while connecting USB and then simply running the executable using the Run Project (USB) option in the Raspberry Pi Pico extension works fine. Running openocd from the command line also works -The issue seems to be some strange interaction between OpenOCD in VS Code and the clocks on the target board, not the code or build. What is going wrong?
Code:
cyw43_arch_gpio_put(CYW43_WL_GPIO_LED_PIN, 1);Code:
sleep_untilCode:
timer_time_reachedThe code I am using is the unmodified blink example from GitHub (https://github.com/raspberrypi/pico-exa ... wifi/blink), as created by the VS Code extension as described in the docs. The board is set to pico_w, all other settings are default. Really, I am following the docs as closely as I can manage. I am debugging using VS Code extension as in the docs.
This is running on an Intel Mac, macOS Sonoma 14.6.1 using a new Pi Debug Probe straight out of the box, I only updated the firmware following the instructions. Compiling, running, and debugging all seem to work fine - can run, set breakpoints, single step. I have tested with two 2040 boards, with same results on each.
Putting the 2040 into BOOTSEL mode by pressing the button while connecting USB and then simply running the executable using the Run Project (USB) option in the Raspberry Pi Pico extension works fine. Running openocd from the command line also works -
Code:
sudo openocd -f interface/cmsis-dap.cfg -f target/rp2040.cfg -c "adapter speed 5000" -c "program ./blink/build/blink.elf verify reset exit"Statistics: Posted by hellesangel — Thu Oct 10, 2024 7:35 am — Replies 1 — Views 77