Signal integrity issue

13-Aug-2024

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 the Target CPU to the BlueBox, signal integrity issues 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 the Trace Line Calibration test.


Possible solutions:

  • Connect the BlueBox Debug Adapter directly to the Target. Additional adapters between BlueBox and Target worsen signal integrity.
  • Use a shorter ribbon cable between the BlueBox connector and the Debug Adapter. We offer ribbon cables in different lengths.
  • Use a stable “noise-free” power supply. 
  • Power the BlueBox, PC, and Target from the same power outlet.

    • Reduce debug clock in Hardware | CPU options | SoC.
    • Select fixed voltage instead of Vref in Hardware | CPU Options | Hardware. 


    Possible solutions for specific configurations

    Arm Cortex, NXP/ST Power Architecture, Renesas RH850 - Parallel Trace Capture method

    Run and rerun the Trace Line Calibration test for longer periods 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.

    Was this answer helpful?