10 Troubleshooting

Top

10.1 General

When attempting to open the Connection Window, I receive the following error message: Could not detect the attached Beagle analyzers for the following reason: Incompatible driver- Please check your CD or the Total Phase website for an updated driver.

A driver newer than version installed is required. Please refer to the Beagle analyzer datasheet for instructions on upgrading the Beagle analyzer USB driver.

I’ve connected my device to a Beagle analyzer. When I try to capture data, no packets are shown.

Please try the following:

• Make sure that you are using the correct protocol tab. At the very least, you should see data in the All tab.

• Reset your filters to make sure you are seeing all the packets.

• For I2C and SPI, make sure that you have selected the correct protocol from the protocol type drop-down menu in the toolbar. You will have to stop your capture in order to change this setting.

• For I2C, make sure that the I2C pullups are set correctly for your target device.

• For SPI, make sure that your capture settings are set to the correct sampling edge, bit order and slave select polarity.

• If the downstream target requires power from the Beagle I2C/SPI/MDIO analyzer, please make sure that target power has been turned on in the settings.

• For USB, if you are testing a high-speed device, make sure you connect the device to the Beagle USB 12 analyzer through a full-speed USB hub or you are using a Beagle USB 480 analyzer.

I’ve set some filters, but the contents of the transaction window have not changed.

Filters are not applied to the transaction window until the Apply Filter button has been pressed. After settings all your filters, make sure you click on the Apply Filter button.

I’ve connected to a Beagle analyzer and I can’t start a capture. The Capture button is disabled, the Capture menu item doesn’t work and neither does the keyboard shortcut.

If only the capture button on the toolbar is disabled, it is most likely that a filtered exported capture has been opened in the Beagle Data Center software. It is not possible to append to a filtered exported capture. In order to capture additional data, please start a new capture or append to a file that is not a filtered exported capture.

Top

10.2 USB

I’ve plugged in a device into the Beagle USB 480 analyzer and it is acting strangely.

Be sure that the analysis end of the Beagle USB 480 analyzer is plugged in prior to plugging in any devices on the target end. This ensures that the devices in the analyzer hardware that isolate the USB bus on the target end are functioning and the target device can communicate properly.

The descriptor information does not appear for my device even though I am able to capture data from the device and it works fine on the host computer.

In order for the Data Center software to correctly parse and display the descriptor data for a target device, the entire enumeration process must be captured. In order to ensure that this entire sequenced is captured, we recommend that the user start the capture before plugging in the target host and the target device.

I’m running a capture with the Beagle USB 480 analyzer and I’m seeing a lot of IN packets with no data or handshake response.

Because the USB protocol is broadcast in the downstream direction, it is possible to see packets from parallel USB links. But only the downstream packets from the host to other USB devices will be observed; upstream packets from other devices to the host will not be seen.

It is possible that the IN packets observed may be directed to the Beagle USB 480 analyzer itself. Methods for dealing with these packets are described in Section 6.4.

I’ve plugged in my target device into the target device port of the Beagle USB 12 analyzer. When I try to capture data, no packets are shown.

The Beagle USB 12 protocol analyzer can only capture full-speed and low-speed USB and cannot capture high-speed USB directly. Please make sure that the target device is not a high-speed USB device.

If it is and you would still like to capture the USB data with the Beagle USB 12 analyzer, the device must be connected to the target device port of the Beagle USB 12 adapter through a full-speed USB hub in order to downgrade the speed of the data.

An article on the Total Phase website outlines the best method for doing this.

Using the Beagle USB 12 Protocol Analyzer to Capture High-Speed USB Data

I get a lot of sync errors when capturing USB data with the Beagle USB 12 analyzer.

Sync errors can be caused by a poor USB connection or an analysis computer that has insufficient resources available for the Beagle Data Center application.

Here are some possible ways to eliminate sync errors:

• Use only USB ports that are mounted directly on the computer’s motherboard. USB ports that are not mounted directly may perform poorly due to cable or connector quality.

• For best performance, it is recommended that the Beagle analyzers are connected to its own USB host controller. All other USB devices should be connected to separate controllers.

• Make sure that your computer has adequate physical memory. The Beagle Data Center software can become unstable if your computer start to swap into virtual memory.

• Make sure that your computer is not running any other performance or resource hungry applications.

• You may want to consider using one computer as the analysis computer and a separate computer as the target host computer.

• It may be possible that the USB signals between the target host and the target device are at the very edge of compliance. If this is the case, the Beagle analyzer may encounter errors when trying to capture the data. One way to test this is to use a USB hub in-line between the Beagle analyzer and the target device. The hub will essentially retransmit the USB data. If this resolves the problem, the electrical signals of the target device should be examined in further detail.

Top

10.3 MDIO

The bit time for the last bit of the frame is zero.

The time displayed for the last bit of the frame is always zero. This is due to the fact that the bit times are measured between rising edges of the MDC line. The first bit time is measured from the first rising edge of the MDC line to the next rising edge. For the last bit of a frame, there may not be a subsequent rising edge of the MDC line until the next frame. Therefore, no bit time value can be determined for final bit of a frame.