-
I got a new patch of rp2040 (03-22). After flashing FW it does not boot at all( No LED flashing, no usb emulation). That FW is running fine on older RP2040 (04-20).
Rebuild the FW with lower CPU cl…
phb98 updated
9 months ago
-
I'm trying to run the example programs on my **Raspberry Pi Pico W** using a Picoprobe setup, as described in the RPi Pico [manual](https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pd…
cshaa updated
11 months ago
-
I am trying to compile yapicoprobe for the Raspberry Pi Pico, on the following build system:
- OS: Ubuntu 20.04.6 LTS x86_64
- CPU: Intel i7-8750H (12) @ 4.100GHz
- Memory: 16GB
- Toolchain: arm-n…
-
## Description
I have an STM32H7xx target configured as an RTT target which I would like to monitor via `yapicoprobe`. I have confirmed with a SEGGER JLINK cable that RTT works on the target, but I w…
-
see https://mcuoneclipse.com/2023/08/11/assigning-nicknames-to-debug-probes/
Should be no big thing: DAP_GetSerNumString() could return a config parameter
-
It appears that versions rg-1.12 and upward are unable to successfully establish a connection from OpenOCD to an STM32 target. I am attempting to use a Raspberry Pi Pico H to debug a Nucleo board with…
-
Without a target connected to the pico with yapicoprobe:
[13072.639849] usb 1-5.4: new full-speed USB device number 13 using xhci_hcd
[13072.903394] usb 1-5.4: New USB device found, idVendor=2e8…
-
- sigrok interface on/off
- mix Target/Probe debug output into one CDC (three CDCs are actually too confusing)
-
I tried to compile but cmake fails:
( My guess is that ${PROJECT} is not defined )
Could there be a how to build this section somewhere in the documentation?
CMake Error at CMakeLists.txt:23 …
-
After following the "Getting started with Raspberry Pi Pico" and following Appendix A, I still can't manage to debug the samples to test the the debugger.
Currently I'm getting these errors.
…