Troubleshooting communications problems

This section explains how to troubleshoot communications problems between the debugger and the Ethernet TAP probe.

If the debugger is unable to communicate with the Ethernet TAP probe:

• Check the cable and connections between the network cable and the Ethernet TAP probe.

  The Ethernet TAP probe connects directly to networks that use twisted pair (10/100BaseT) cables.

• Make sure communication was configured correctly for your network.
• Make sure the Ethernet TAP probe is receiving power.

  See Ethernet TAP probe status indicators topic for a description of the status LEDs. For more information on connecting the Ethernet TAP probe to the external power supply, see Connecting external power supply topic.

• Make sure the Ethernet TAP probe is running the core software.

  See Ethernet TAP probe status indicators topic for a description of the status LEDs. For more information on loading the core software, see Ethernet TAP probe firmware (core) topic.

• Use the communications troubleshooting utilities of Ethernet TAP probe to verify that it is recognized on your network, or to help diagnose problems connecting to your network.

  To troubleshoot communications, see Basic troubleshooting topic.

  To list all the CodeWarrior probes on your local subnets, use the efind host utility. See Using efind to discover Ethernet TAP probes topic.

• Make sure the debugger is set up correctly for Ethernet communications with the Ethernet TAP probe.

If all the settings are correct and the debugger cannot communicate to the Ethernet TAP probe, contact Customer Support for assistance.