🎉 We're happy to announce new public releases 🎉

  • TriCore v6.2r2 Inspector v1.0r8 - An automated method for identifying toolset issues in compiled output code
  • VX-toolset for Arm - v8.0r1 - A certified compiler toolset for safety critical embedded software development on Arm cores
Contact us to get access

Debug Adapter: Determining maximum cable length

26-Sep-2024

You were attempting to extend the Debug Adapter cable with an additional cable. This extension resulted in a loss of connection to the target and debugging became impossible.


Possible solutions

Active Probe

The functionality of the BlueBox cannot be guaranteed when additional cables are used, which are typically intended for rare situations when the standard debug adapter faces challenges connecting to the target due to physical obstacles.

If longer cable lengths are required for your debugging setup, consider using an alternative solution such as an Active Probe. This setup allows for the use of FNet cables that can be up to 10 meters long, providing greater flexibility in cable length. 


Experimental testing

In case you still consider prolonging the cable, it is often necessary to experiment with cable lengths to determine the maximum allowable length for your specific setup. Start with shorter cables and gradually increase the length while monitoring the connection and debugging performance.


More resources

Was this answer helpful?