pyOCD icon indicating copy to clipboard operation
pyOCD copied to clipboard

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

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

RTT support is super-useful, but without support in GDB server it's not available for integration, e.g. in https://github.com/Marus/cortex-debug As I understand, `pyocd rtt` command cannot be used when a debugging...

The target family LPC5500 has a regex `r'LPC55?[0-9]{2}.*'`, which accidently matches all LPC54 series MCUs. While using CMSIS-Pack targets for these MCUs, the sequence for LPC55 will be used instead...

PyOCD v0.32 with python 3.9.6 on Windows 10 Hi, I am trying to flash a binary to my new MicrobitV2 using pyocd, but I get the error below. ![image](https://user-images.githubusercontent.com/6376127/133856110-181f2c1c-15be-425d-8112-d6294d6804f5.png) The...

target
under-investigation

- Intel Hex file used for testing, but should be the same with any other: [CALL_ME_MICROBIT.hex.zip](https://github.com/pyocd/pyOCD/files/7693018/CALL_ME_MICROBIT.hex.zip) - micro:bit V2.0 with the factory 0255 release (the "`Firmware for micro:bit V2`" button):...

This PR adds support for NXP LPC55S16 family devices: Flash algo and SVD: From MDK DFP v14.0.0

### OS Windows ### Pyocd Version 0.33.1 ### DFP info Vendor Pack Version ---------------------------------------- GigaDevice GD32F3x0_DFP 2.0.0 ### Debug probe CMSIS-DAP v1 ### Command pyocd flash -f 1.2m "C:\Users\Documents\Bin\binary.hex" -t...

target
cmsis-pack
under-investigation

When connecting to STM32H730VB, there is problem with coresight rom table readout. In fact, even records which are found do not seem to match [ref. manual](https://www.st.com/resource/en/reference_manual/rm0468-stm32h723733-stm32h725735-and-stm32h730-value-line-advanced-armbased-32bit-mcus-stmicroelectronics.pdf) (65.5.1 page 3140). Debugging...

bug
swo/swv

pyocd/probe/*: Attempt to import libusb-package's `find()` function, else fall back to using pyusb's `find()` function. This allows to use pyusb by just removing the project's requirement on libusb-package, as python-pyusb...

This follows the way in the `jlink_probe` module of getting configs. Fixes the first 2 requirements in #1417