Infineon OpenOCD v5.20

Infineon OpenOCD v5.20.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 Programming Tools v2.0.0.

New Features

• Updated default adapter speed to 16 or 12 MHz for SWD and to 8 MHz for JTAG for all targets.
• Switched to libusb 1.30.
• Added support for Ubuntu 26.04.

Supported Devices/Probes Added

• Added CYT2B6/CYT2B7 target configuration.
• Added PSC3M3/P5 targets support.
• Added PSoC 4100SL series support.

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 a limitation of the hidapi library used on Linux. macOS and Windows are not impacted.	If you have a debug session running, do not use the Firmware Loader tool.
PROGTOOLS-2388	PSoC 64 Secure MCUs do not support programming and debugging via the JTAG interface. This is due to the specifics of PSoC 64 MCUs — JTAG pins are configured after an unpredictable amount of time, which causes warnings during programming via JTAG.	Use the SWD interface with PSoC 64 Secure MCUs.
PROGTOOLS-2238	Unable to acquire PSoC 4 target with a J-Link probe if the target is in PROTECTED state. The 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.	Unprotect/erase the chip using a MiniProg4 or KitProg3 probe.
PROGTOOLS-2099	A "Failed to read memory at <address>" message may appear in the "Memory View" of the IDE when connected via the MiniProg4 probe and attempting to read memory from an invalid address.	You can safely ignore this error.
PROGTOOLS-3495	When programming or debugging, the following error message may appear: Error connecting DP: cannot read IDR This occurs if the debug port is disabled in the BSP for the specific project.	Enable the debug port for the specific project, or safely ignore this message if the debug port is intentionally disabled.

More Information

• OpenOCD README.md
• ModusToolbox Software Environment, Quick Start Guide, Documentation, and Videos
• ModusToolbox Device Configurator Tool Guide
• Infineon Technologies AG

© Infineon Technologies AG, 2020-2026. This document is the property of Infineon Technologies AG and its affiliates ("Infineon").

Infineon OpenOCD v5.19

Infineon OpenOCD v5.19.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™ Programming tools v1.9.0

New Features

• Add KitProg3 bridge_control and transfer hooks to improve programming performance. (PROGTOOLS-8098)
• Add faster CRC-based verify/checksum using CMSIS flashloader CalcCRC. (PROGTOOLS-7481)

Supported Devices/Probes Added

• Add TRAVEO™ II C-2D 6M DDR (CYT4EN) target configuration. (PROGTOOLS-8112)
• Add PSOC™ 4 HVPA SPM 2.0 targets support. (PROGTOOLS-8060)
• Add PSC3x6, PSC3x7, PSC3x8 PSOC™ Control C3 series support.

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

• openOCD
  README.md

• ModusToolbox Software Environment, Quick Start Guide, Documentation, and
  Videos

• ModusToolbox Device Configurator Tool
  Guide

• Infineon Technologies AG

© Infineon Technologies AG, 2020-2026. This document is the property of Infineon Technologies AG and its affiliates ("Infineon").

Infineon OpenOCD v5.16.1

Infineon OpenOCD v5.16.1 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™ Programming tools v1.8.1

New Features

• Resolved an application crash that occurred when modifying protection settings.
• Updated flash loaders to support PSE84 devices.

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

• openOCD
  README.md

• ModusToolbox Software Environment, Quick Start Guide, Documentation, and
  Videos

• ModusToolbox Device Configurator Tool
  Guide

• Infineon Technologies AG

© Infineon Technologies AG, 2020-2026. This document is the property of Infineon Technologies AG and its affiliates ("Infineon").

Infineon OpenOCD v5.16.0

Infineon OpenOCD v5.16.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™ Programming tools v1.8.0

New Features

• Adds support of TRAVEO™ T2G 16M (CYT2CL) MCUs.
• Extends support of CCG7S, XMC5xxx, and PSE8X6 with new MCUs.
• Support only ARM CPUs on macOS.

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

• openOCD
  README.md

• ModusToolbox Software Environment, Quick Start Guide, Documentation, and
  Videos

• ModusToolbox Device Configurator Tool
  Guide

• Infineon Technologies AG

© Infineon Technologies AG, 2020-2026. This document is the property of Infineon Technologies AG and its affiliates ("Infineon").

Infineon OpenOCD v5.12.0

Infineon OpenOCD v5.12.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™ Programming tools v1.7.0

New Features

• Adds support of TRAVEO™ T2G Cluster Entry 4M (CYT2CL) MCUs.
• New PSOC 4100T Plus, PSOC4100T Plus 256KB, PSOC 4100T, and PSOC4A-S3 MPNs.

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

• openOCD
  README.md

• ModusToolbox Software Environment, Quick Start Guide, Documentation, and
  Videos

• ModusToolbox Device Configurator Tool
  Guide

• Cypress Semiconductor, an Infineon Technologies Company

© Cypress Semiconductor Corporation (an Infineon company), 2020-2025.

Infineon OpenOCD v5.11.0

Infineon OpenOCD v5.11.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™ Programming tools v1.6.0

New Features

• Adds support of TRAVEO™ T2G Cluster 4M MCUs.

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 unacceptable.
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 a limitation of the 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 programming and debugging via JTAG interface. This is due to the specifics of PSoC 64 MCUs, where JTAG pins are configured after an unpredictable amount of time, which causes numerous warnings during programming via JTAG.	Use the 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 the invocation of the SROM API, making it impossible to reprogram or erase the chip in PROTECTED state.	The workaround is to unprotect/erase the chip using the 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 trying to read memory from an 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

• openOCD
  README.md

• ModusToolbox Software Environment, Quick Start Guide, Documentation, and
  Videos

• ModusToolbox Device Configurator Tool
  Guide

• Cypress Semiconductor, an Infineon Technologies Company

© Cypress Semiconductor Corporation (an Infineon company), 2020-2025.

Infineon OpenOCD v5.8.0

Infineon OpenOCD v5.8.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™ Programming tools v1.5.0

New Features

• Adds support of PSOC™ Edge E84 product lines and the corresponding kits
• Adds support of new part numbers in the PMG1-B2, CYW20829, CCG6_CFP & CCG8_CFP, and PSOC 4 HVPA SPM 1.0 devices
• Kill mode support for PSOC 4, CCG, PMG and PAG2S devices

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

• openOCD
  README.md

• ModusToolbox Software Environment, Quick Start Guide, Documentation, and
  Videos

• ModusToolbox Device Configurator Tool
  Guide

• Cypress Semiconductor, an Infineon Technologies Company

© Cypress Semiconductor Corporation (an Infineon company), 2020-2025.

Infineon OpenOCD v5.7.0

Infineon OpenOCD v5.7.0

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™ Programming tools v1.4.0

New Features

• Adds support of PSOC™ 4100T Plus product line.
• Adds new manufacture part numbers of the CCG7S, CYW20829, PSOC™ 4000T and PSOC™ 62 product lines.

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

• openOCD
  README.md

• ModusToolbox Software Environment, Quick Start Guide, Documentation, and
  Videos

• ModusToolbox Device Configurator Tool
  Guide

• Cypress Semiconductor, an Infineon Technologies Company

© Cypress Semiconductor Corporation (an Infineon company), 2020-2025.

Infineon OpenOCD v5.6.1

Infineon OpenOCD v5.6.1

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™ Programming tools v1.3.1

New Features

• Adds new manufacture part numbers of the CCG7S product line.
• Updated OpenOCD to address known issue about the PSOC™ Control C3 device being permanently disabled if flash row 0 contains uncorrectable ECC errors.

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

• openOCD
  README.md

• ModusToolbox Software Environment, Quick Start Guide, Documentation, and
  Videos

• ModusToolbox Device Configurator Tool
  Guide

• Cypress Semiconductor, an Infineon Technologies Company

© Cypress Semiconductor Corporation (an Infineon company), 2020-2025.

Infineon OpenOCD v5.6.0 Release Notes

Infineon OpenOCD v5.6.0 Release Notes

lease refer to the README.md for a complete description of the Infineon customized version of OpenOCD. This version of openOCD is released with ModusToolbox™ Programming tools v1.3.0

New Features

• Adds support of XMC5xxx and PSC3 product lines and the corresponding kits.

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

• openOCD
  README.md

• ModusToolbox Software Environment, Quick Start Guide, Documentation, and
  Videos

• ModusToolbox Device Configurator Tool
  Guide

• Cypress Semiconductor, an Infineon Technologies Company

© Cypress Semiconductor Corporation (an Infineon company), 2020-2024.