Failed to initialize debug session / Emulation start failed

The error means that the debugger failed to connect to the target CPU. This can be for different reasons. 

Possible problems and solutions

BlueBox is not properly connected to the target debug connector

Check:

• Connection via Debug Adapter or Active Probe.
• Pinout of the target debug connector matches with the one from the Debug Adapter or Active Probe.
• Active Probe DAP/DAPE:
  • DAP target debug connector is connected to the Active Probe DAP connector and not accidentally to the Active Probe DAPE connector.
  • DAPE target  debug connector is connected to the Active Probe DAPE connector and not DAP connector

Necessary voltage is not connected to the target LPD debug connector orm JTAG/Nexus debug connector

Refer to Setting debug interface voltage levels (Vref).  

BlueBox hardware can be damaged (Connector on the BlueBox, Debug Adapter, Active Probe)

Try to confirm this with another working BlueBox system. In case you confirm that the BlueBox hardware is damaged, contact iSYSTEM support. 

The Target CPU can be damaged or permanently locked (e.g. by programming wrong UCB data)

Try to test the BlueBox on another target or try to replace the CPU with a new one.

Active Watchdog prevents establishing a debug session

Disable all reset sources during debugging. See further explanation.

Incorrect JTAG Scan speed configuration

Open Hardware / CPU Options / JTAG  and configure the Scan speed.

ARM Cortex-M: Failed to initialize debug session

Infineon TriCore: Failed to initialize debug session / DAP Initialization failed