===============================================================================
> Known issues and limitations in Infineon DFP for IAR EW-ARM
===============================================================================

* ID: PROGTOOLS-1884
  Issue: The application does not start (e.g. LED is not blinking) after
  executing of the "Download active application" operation.
  Workaround: Press the reset button on a kit to start the application.

* ID: PROGTOOLS-1935
  Issue: Attach to Running Target does not work with Jlink and PSoC™ 4 targets.
  Workaround: This limitation is caused by PSoC™ 4 targets support implementation
  inside SEGGER software. To avoid this, use a generic Cortex-M0 target for the??
  Attach operation: General Options->Target->Core->Cortex-M0+

* ID: PROGTOOLS-2248
  Issue: The program / debug step may fail for PSoC™ 6 projects if the
  application image contains the XIP region of the SMIF memory for programming.
  The error messages may be either "Reading memory at 0x18000000 failed while
  verifying download" or "Flash memory checksum verification failed for range
  0x18000000-0x181FFFFF". The reason - the debugger is trying to
  read from the XIP region that hasn't been activated yet by the application
  after the Program/Reset step.
  Workaround: Turn off the "Verify download" option in section Debugger->
  Download of project setting.

* ID: PROGTOOLS-2379
  Issue: A running application may cause problems during programming or may
  disrupt the normal operation of the debugger. For example, disable the debug
  subsystem, repurpose SWD pins, change clock settings, overwrite flash
  algorithms or buffers in RAM, active watchdog timers, etc. This may be caused
  by the fact that EW-ARM uses J-Link aliases for PSoC™ 64 MCUs that do not
  implement the Infineon Test Mode connection method.
  Workaround: To make the debugger's operations more stable, use the Test Mode
  connection method: change the JLinkScriptFile parameter for PSoC™ 64 MCUs
  device aliases without the _tm suffix to the same with the _tm suffix
  (for example, change "CYB06xx7_CM4" to "CYB06xx7_CM4_tm").

* ID: PROGTOOLS-3450
  Potential issues using the J-Trace probe for ETM Tracing:
  Issue 1: The "Trace restart after FIFO overflow" message may display.
  Workaround: Turn on the "Stall processor on FIFO full" option in the ETM
  Trace Settings dialog box.
  Issue 2: The message "Trace sync point" may display in the long run.
  Workaround: Increase "Trace buffer size" up to its maximum value - 0x400000
  in the ETM Trace Settings dialog box.

* ID: PROGTOOLS-3525
  Issue: The ETM trace does not work with XMC7000 devices with the SEGGER J-Trace probe.
  This is a known limitation in EW-ARM, which supports ETM for Cortex-M3/M4
  only when using J-Trace.
  Workaround: Use the native I-jet Trace probe.

* ID: PROGTOOLS-3585
  Issue: For the XMC7200 Evaluation Kit, there may be issues with crosstalk
  related to ETM data capturing with the I-jet Trace probe.
  Workaround 1: Decrease the trace clock frequency by specifying a trace clock
  divider value of 1 or greater in the "Extra Options" tab of debugger options,
  e.g. "--macro_param _TRACE_div_value=1".
  Workaround 2: Reduce the trace port width to 2 bits or 1 bit in the
  "ETM Trace Settings" dialog.

* ID: PLATLIBS-3509
  Issue: Flash erase operation will fail for PSC3 targets if secure flash access is restricted by the policy used for provision.
  Workaround: Use non-secure flash loader for erase (Project->Download->Erase memory and select *_NS.flash checkbox only).

* ID: PLATLIBS-4653
  Issue: Issue: When using 2-bit and 4-bit trace data mode with I-jetTrace via JTAG on PSC3 targets, ETM Tracing may not function correctly.
  Workaround: Use ETM tracing on PSC3 targets with I-jetTrace via JTAG in 1-bit trace data mode or via SWD in 1-bit, 2-bit, or 4-bit trace data.
