Initial commit

README.MD

@@ -0,0 +1,32 @@
+Infineon Customized OpenOCD
+===============
+
+### Overview
+
+The Open On-Chip Debugger (OpenOCD) is free software that provides debugging, in-system programming, and boundary-scan testing.
+
+To work with ModusToolbox and Infineon devices and probes, Infineon has modified OpenOCD to support:
+- Devices from PSoC 61/62/63/64 product lines and the corresponding kits
+- Devices from PSoC 4000S, PSoC4100S, PSoC 4100S Plus and PSoC 4500 product lines  and the corresponding kits
+- KitProg3 onboard programmer
+- MiniProg4 standalone programmer
+
+From the [release page](https://github.com/Infineon/openocd/releases), download and unpack the appropriate archive for your OS. Source for these executables are available on the [ModusToolbox FOSS page](https://www.infineon.com/cms/en/design-support/software/free-and-open-source-software-foss/modustoolbox-foss-packages/) 
+
+If you want to update ModusToolbox to use this release, replace the contents of the  */ModusToolbox/tools_2.x/openocd* folder with the downloaded package from the release page. Otherwise just put the tool in any convenient location. 
+
+On the Catalina version of macOS, you may see a dialog what Apple cannot check this package for malicious  software. If this happens, please follow [instructions](https://support.apple.com/guide/mac-help/open-an-app-by-overriding-security-settings-mh40617/10.15/mac/10.15) from Apple.
+
+This software component is licensed under GNU General Public License v2
+
+### FOSS usage
+
+Infineon maintains a collection of [Free and Open Source Software](https://www.infineon.com/cms/en/design-support/software/free-and-open-source-software-foss/modustoolbox-foss-packages/) (FOSS) packages. It includes OpenOCD.
+
+### More Information
+
+[openOCD Release Notes](https://github.com/Infineon/openocd/blob/main/RELEASE.MD)
+
+OpenOCD documentation in [HTML](http://openocd.org/doc/html/index.html) or [PDF](http://openocd.org/doc/pdf/openocd.pdf).
+
+© Cypress Semiconductor Corporation (an Infineon company), 2020-2023.

RELEASE.MD

@@ -0,0 +1,38 @@
+### 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](https://softwaretools.infineon.com/tools/com.ifx.tb.tool.modustoolbox?_ga=2.188424168.1391341860.1691491995-1428656764.1691491995)
+
+### 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 <address>" 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](https://github.com/Infineon/openocd/blob/main/README.MD)
+
+-   [openOCD User Guide](https://www.cypress.com/file/495061/download)
+
+-   [ModusToolbox Software Environment, Quick Start Guide, Documentation, and
+    Videos](https://www.infineon.com/cms/en/design-support/tools/sdk/modustoolbox-software/)
+
+-   [ModusToolbox Device Configurator Tool
+    Guide](https://www.infineon.com/ModusToolboxDeviceConfig)
+
+-   [Cypress Semiconductor, an Infineon Technologies Company](http://www.cypress.com)
+
+© Cypress Semiconductor Corporation (an Infineon company), 2020-2023.