pyOCD icon indicating copy to clipboard operation
pyOCD copied to clipboard

Open source Python library for programming and debugging Arm Cortex-M microcontrollers

Results 207 pyOCD issues
Sort by recently updated
recently updated
newest added

For the STM32 builtin targets, I noticed many of the targets are at the high end with lots of flash and RAM. I think it would be more useful to...

**Issue:** When calling ConnectHelper.get_all_connected_probes() multiple times memory consumption increases indefinitely. **System:** - Linux - libusb-1.0.24-2 - python3.8, python3.9 - pyocd-0.28.3, pyocd-0.29.0 **Steps to reproduce:** `>>> from pyocd.core.helpers import ConnectHelper` `>>>...

bug

Hi I'm using mbed studio and when trying to debug on a stm32l4r5zitx with a STLink. I'm getting the following log when trying to debug: ``` Selected port 50000 for...

bug

I encountered a problem when using the Microchip PACK for the atsamd51 series MCU's. The first issue appears to be that pyOCD cannot determine the RAM layout. The second problem...

bug
target
under-investigation

The correct flag is `under-reset`, but passing `under_reset` or indeed `asdf` does nothing, rather than giving an error. This confused me for a while 🙃

improvement

I installed the PACK for RT1011 and then downloaded the HEX file using the Flash command, prompting me for the following information: 0000344:WARNING:cmsis_pack:Overlapping memory regions in file , deleting outer...

Hi, Alongside @ksigurdsson I've been using pyOCD to test an M3 in a custom ASIC, via a SEGGER JLink debugger. During this we've noticed that loading and dumping regions of...

new feature
probe/jlink

When a probe server client disconnects, it will perform the target disconnect procedure even if there are still other remote clients connected, or a local client using the probe (such...

bug
probeserver

I can't get `pyocd gdbserver` to work. When I try to connect with `arm-none-eabi-gdb`, gdb says `Reply contains invalid hex digit 120` and drops the connection. Since debugging the same...

bug
gdbserver

the b-l4s5i-iot0a1, when I try to connect and debug I get the rw_IRAM1 outside of segment. Then of course the gdbserver gets the exception individual must not cross memory region...