This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
resources:eval:user-guides:inertial-mems:evaluation-systems:eval-adis-fx3-setup-troubleshooting [11 Feb 2021 17:53] – Ioana Chelaru | resources:eval:user-guides:inertial-mems:evaluation-systems:eval-adis-fx3-setup-troubleshooting [17 Feb 2021 03:10] – Added links to the EVAL-ADIS-FX3 product page Juan Chong | ||
---|---|---|---|
Line 56: | Line 56: | ||
===== Downloading and Installing the FX3 Drivers and Software ===== | ===== Downloading and Installing the FX3 Drivers and Software ===== | ||
- | The EVAL-ADIS-FX3 includes a laundry list of hardware and software features designed to enable in-depth test and characterization of iSensor IMUs. To get started, we suggest you first download the [[https:// | + | The [[adi>EVAL-ADIS-FX3|EVAL-ADIS-FX3]] |
Once downloaded, double click on '' | Once downloaded, double click on '' | ||
Line 82: | Line 82: | ||
{{: | {{: | ||
- | <note important> | + | <note important> |
{{ : | {{ : | ||
Line 92: | Line 92: | ||
{{: | {{: | ||
- | <note warning> | + | <note warning> |
{{: | {{: | ||
Line 98: | Line 98: | ||
</ | </ | ||
- | Once at the main window, click on “Connect to FX3” to enable all GUI features. If the connection to the EVAL-ADIS-FX3 was successful, all of the Evaluation GUI utilities would activate. The iSensor FX3 Eval software assesses IMU Status by writing a randomly-generated number to the sensor module and reading it back. | + | Once at the main window, click on “Connect to FX3” to enable all GUI features. If the connection to the [[adi>EVAL-ADIS-FX3|EVAL-ADIS-FX3]] |
{{: | {{: | ||
Line 113: | Line 113: | ||
==== " | ==== " | ||
- | These errors occur when the FX3 Evaluation GUI cannot detect or somehow loses connection with an active EVAL-ADIS-FX3 board. | + | These errors occur when the FX3 Evaluation GUI cannot detect or somehow loses connection with an active |
{{: | {{: | ||
=== Is the USB cable plugged in? === | === Is the USB cable plugged in? === | ||
- | The EVAL-ADIS-FX3 must be plugged into a USB Type-A port capable of at least USB 2.0 speeds. USB hubs should be avoided since the USB protocol imposes artificial power limits when connecting through one. | + | The [[adi>EVAL-ADIS-FX3|EVAL-ADIS-FX3]] |
=== Is the USB cable capable of transmitting data? === | === Is the USB cable capable of transmitting data? === | ||
- | Many USB cables that ship with mobile phones are **not** capable of transferring USB data and are designed for high-speed charging. We suggest using a high-quality USB C cable (like the one included with the EVAL-ADIS-FX3) to ensure reliable, robust communication. | + | Many USB cables that ship with mobile phones are **not** capable of transferring USB data and are designed for high-speed charging. We suggest using a high-quality USB C cable (like the one included with the [[adi>EVAL-ADIS-FX3|EVAL-ADIS-FX3]]) to ensure reliable, robust communication. |
=== Does Windows detect the EVAL-ADIS-FX3? | === Does Windows detect the EVAL-ADIS-FX3? | ||
- | The Analog Devices FX3 bootloader is flashed to the onboard EEPROM as part of the EVAL-ADIS-FX3 manufacturing process. It can be verified by looking for a USB device named “Analog Devices FX3 Bootloader” in the Windows Device Manager. | + | The Analog Devices FX3 bootloader is flashed to the onboard EEPROM as part of the [[adi>EVAL-ADIS-FX3|EVAL-ADIS-FX3]] |
{{: | {{: | ||
- | If you’re unable to find the device, try resetting the FX3 by either unplugging the USB cable or pressing the reset button on the EVAL-ADIS-FX3. If this still doesn’t solve the issue, try pressing and holding the “RECOVERY” button while plugging the board into your PC. This will force the board to connect in recovery mode. | + | If you’re unable to find the device, try resetting the FX3 by either unplugging the USB cable or pressing the reset button on the [[adi>EVAL-ADIS-FX3|EVAL-ADIS-FX3]]. If this still doesn’t solve the issue, try pressing and holding the “RECOVERY” button while plugging the board into your PC. This will force the board to connect in recovery mode. |
{{: | {{: | ||
=== Is the ribbon cable orientation correct? Are the ribbon cable or sensor connections shifted or offset? === | === Is the ribbon cable orientation correct? Are the ribbon cable or sensor connections shifted or offset? === | ||
- | The EVAL-ADIS-FX3 includes short-circuit protection on the sensor supply pins when using the onboard (USB) supply. Even so, it is still possible to exceed the USB current limits and force the EVAL-ADIS-FX3 to brownout. A connection issue like this can be harmful to both the EVAL-ADIS-FX3 and the host PC and may permanently damage either if not corrected immediately. | + | The [[adi>EVAL-ADIS-FX3|EVAL-ADIS-FX3]] |
=== Was the EVAL-ADIS-FX3 exposed to extreme environments? | === Was the EVAL-ADIS-FX3 exposed to extreme environments? | ||
- | The EVAL-ADIS-FX3 was designed for bench evaluation, data capture, and characterization. Even though most iSensor portfolio devices are designed and validated to operate in extreme environments, | + | The [[adi>EVAL-ADIS-FX3|EVAL-ADIS-FX3]] |
=== Did you try to send the FX3 several commands during a long execution process? === | === Did you try to send the FX3 several commands during a long execution process? === | ||
Line 151: | Line 151: | ||
=== Is the power selection jumper correctly set? === | === Is the power selection jumper correctly set? === | ||
- | The EVAL-ADIS-FX3 can either supply power to the sensor using an onboard linear regulator or bypass the onboard regulator and use an external power source. The jumper must be set to " | + | The [[adi>EVAL-ADIS-FX3|EVAL-ADIS-FX3]] |
{{ : | {{ : | ||
=== Is the ribbon cable orientation correct? === | === Is the ribbon cable orientation correct? === | ||
- | It's common to invert (flip) the ribbon cable orientation when connecting the EVAL-ADIS-FX3 to a sensor coupon or breakout board. The correct cable orientation is shown below. | + | It's common to invert (flip) the ribbon cable orientation when connecting the [[adi>EVAL-ADIS-FX3|EVAL-ADIS-FX3]] |
{{ : | {{ : | ||
Line 165: | Line 165: | ||
{{ : | {{ : | ||
- | === Was the correct profile for the sensor connected to the EVAL-ADIS-FX3 loaded? Was the correct register map loaded? === | + | === Was the correct profile for the sensor connected to the [[adi>EVAL-ADIS-FX3|EVAL-ADIS-FX3]] |
The name of the active profile and register map can always be found on the main form, as shown below. | The name of the active profile and register map can always be found on the main form, as shown below. | ||
Line 173: | Line 173: | ||
=== Is the active SPI configuration valid for the sensor connected to the EVAL-ADIS-FX3? | === Is the active SPI configuration valid for the sensor connected to the EVAL-ADIS-FX3? | ||
- | It's possible to change the EVAL-ADIS-FX3 configuration such that it exceeds the SPI specifications listed on the sensor' | + | It's possible to change the [[adi>EVAL-ADIS-FX3|EVAL-ADIS-FX3]] |
=== Are the SPI pins on the EVAL-ADIS-FX3 forced high/low? === | === Are the SPI pins on the EVAL-ADIS-FX3 forced high/low? === | ||
- | Some logic analyzers and in-circuit debuggers will hold GPIO lines at specific states such that either the EVAL-ADIS-FX3 or the sensor cannot source/sink enough current to force a transition. | + | Some logic analyzers and in-circuit debuggers will hold GPIO lines at specific states such that either the [[adi>EVAL-ADIS-FX3|EVAL-ADIS-FX3]] |
=== Is the ribbon cable connected to the FX3 too long? === | === Is the ribbon cable connected to the FX3 too long? === | ||
- | The EVAL-ADIS-FX3 was not designed to drive long cable lengths without adding additional driver circuitry. As cable length increases, the SPI signal integrity will quickly deteriorate. Variables such as SPI SCLK rate and stall time will also influence the overall cable length. A long cable will usually result in zeros intermittently inserted in random registers and incomplete register writes. | + | The [[adi>EVAL-ADIS-FX3|EVAL-ADIS-FX3]] |
===== Reporting Errors and Generating Crash Reports ===== | ===== Reporting Errors and Generating Crash Reports ===== | ||
Line 185: | Line 185: | ||
==== Generating a firmware error log ==== | ==== Generating a firmware error log ==== | ||
- | The EVAL-ADIS-FX3 firmware includes an error logging feature that stores any exceptions generated during operation into the onboard EEPROM. When reporting an issue, it’s helpful to provide this file since it will help us recreate and diagnose the issue' | + | The [[adi>EVAL-ADIS-FX3|EVAL-ADIS-FX3]] |
- | To extract the firmware log, connector to the EVAL-ADIS-FX3 in question, navigate to the " | + | To extract the firmware log, connector to the [[adi>EVAL-ADIS-FX3|EVAL-ADIS-FX3]] |
{{: | {{: | ||
- | This window will list the number of errors logged in the EVAL-ADIS-FX3 EEPROM and allow you to extract a log file. This file contains firmware metadata and the exact line in the FX3 firmware where the error was generated. Providing this information greatly speeds up the debug process and plays a crucial role in determining the error' | + | This window will list the number of errors logged in the [[adi>EVAL-ADIS-FX3|EVAL-ADIS-FX3]] |
==== Locating the Eval GUI error log ==== | ==== Locating the Eval GUI error log ==== | ||
Line 199: | Line 199: | ||
{{: | {{: | ||
- | Click [[resources: | + | Click [[resources: |