Non-optimal Target PCB design (different line lengths, vias, stubs etc.) and other hardware accessories (connectors, power supply etc.) can degrade the electrical signals. Therefore while transferring information at high-frequencies from Target CPU to the BlueBox, signal integrity issue can be indicated in winIDEA as follows:
- Corrupted data visible in the Trace Window (e.g. different addresses than the actual variable).
- Renesas RH850: Error 250: Cannot connect to the CPU Debug Unit. Possible signal integrity issue.
- Infineon TriCore: Error. Debug communication error.
- ARM Cortex, NXP/ST Power Architecture, Renesas RH850 - Parallel Trace Capture method: Error. Please perform the Trace port calibration. or small data eye after performing Trace Line Calibration test.
- Connect the BlueBox Debug Adapter directly to the Target. Additional adapters between BlueBox and Target worsen signal integrity.
- Use shorter ribbon cable between BlueBox DTM connector and the Debug Adapter. iSYSTEM offers ribbon cables in different lengths.
- Use stable “noise free” power supply.
- Power the BlueBox, PC and Target from the same power outlet.
- Reduce debug clock in Hardware menu / CPU options / SoC.
- Select fixed voltage instead of Vref in Hardware menu / CPU Options / Hardware.
Possible solutions for specific configurations:
ARM Cortex, NXP/ST Power Architecture, Renesas RH850 - Parallel Trace Capture method:
Run and rerun Trace Line Calibration test for longer periods of time to find an optimal sampling position.
NXP/ST Power Architecture, Renesas RH850:
Check if all MDO (Message Data Out) signals are correctly connected to Mictor Debug Adapter.