Infineon OpenOCD v5.0.0 Release Notes
Please refer to the README.md for a complete description of the Infineon customized version of OpenOCD. This version of openOCD is released with ModusToolbox™ v3.1.0 Tools Package
New Features
- Adds support of varios new devices from the existing product lines
- Delivers fixes for various defects
Known Issues
| ID | Known Issue | Workaround |
|---|---|---|
| PROGTOOLS-1425 | A "JTAG-DP STICKY ERROR" message may appear in the IDE when connected via the JTAG interface of a MiniProg4 probe in CMSIS-DAP HID mode. | You can safely ignore this error, or switch the MiniProg4 to CMSIS-DAP bulk mode. |
| PROGTOOLS-1429 | JTAG performance on MiniProg4 may be significantly slower than SWD. | Use the SWD interface if JTAG performance is not acceptable. |
| PROGTOOLS-1869 | In Linux OS, with KitProg3 in CMSIS-DAP HID mode, a debug session in ModusToolbox can be destroyed if you use the Firmware Loader --device-list command while debugging. This is limitation of hidapi library used on Linux. MacOS and Windows OSs are not impacted. | If you have a debug session running, don't use the firmware loader tool. |
| PROGTOOLS-2388 | PSoC 64 Secure MCUs do not support the programming and debugging via JTAG interface. It is because of the specifics of PSoC 64 MCUs - JTAG pins are configured after unpredictable amount of time after what causes a lot of warnings during programming via JTAG. | Use SWD interface with PSoC 64 Secure MCUs. |
| PROGTOOLS-2238 | Unable to acquire PSoC4 target with J-Link probe if target is in PROTECTED state. J-Link probe does not support device acquisition in Test Mode. This prevents invocation of SROM API making it impossible to re-program or erase the chip in PROTECTED state. | The workaround is to unprotect/erase the chip using MiniProg4 or KitProg3 probe. |
| PROGTOOLS-2099 | A "Failed to read memory at " message may appear in "Memory View" of IDE when connected via the MiniProg4 probe and try to read memory from invalid address. | You can safely ignore this error. |
| PROGTOOLS-3495 | When programming or debugging, you see the following error message: Error connecting DP: cannot read IDR. This occurs if the debug port is disabled in the BSP for the specific project. | You can enable the debug port for the specific project, or safely ignore this message if the debug port is still disabled. |
More information
© Cypress Semiconductor Corporation (an Infineon company), 2020-2023.