Hardware & device support

Please, check out the datasheet and application notes of the product. Then, download our eMD firmware from our webpage and look at our examples. Unfortunately, we cannot debug your code, but we can help customers with any questions you might have for a specific register or procedure.

This might be Atmel issue, if your file path is too long it causes an error. Try to place your file in shorter path. Like C:\Users\xxxx\Documents\Atmel Studio\eMD-SmartMotion 

Our Public GitHub page is here: TDK InvenSense · GitHub

You can see our Arduino drivers in GitHub where we also track and solve your issues. 

Or you can download our Official Arduino libraries here: 

ICM42670P - Arduino Reference

ICM42670S - Arduino Reference

ICM45605 - Arduino Reference

ICM45686 - Arduino Reference

ICP101xx - Arduino Reference

ICP201xx - Arduino Reference

ICUX0201 - Arduino Reference

Most of our devices operates in mode 0 and mode 3 or mode 1 and mode 2. One can find more information in our product datasheets on how to set it up by doing key word search of “SPI mode”.

I2C slave addresses can be 0x68 or 0x69 and can be configured by the logic level of the pin AP_AD0. 

In order to achieve that, one needs to make sure that the MCU on our DK board should not act as a master device. The way to accomplish that is to erase the preprogrammed Microchip/Atmel firmware. After that, one can connect the sensor pins on the DK board to another board.

You can see the terms LSB/dps and LSB/g relatively in our datasheet Gyroscope Specifications and Accelerometer Specifications sections. You need to look at your Full-Scale Range setting for accelerometer and gyroscope, then find the corresponding sensitivity scale factor values from table. Those sensitivity scale factors used for converting from LSB to dps (degrees per second) and g units. 

Most of our devices operates in mode 0 and mode 3 or mode 1 and mode 2. One can find more information in our product datasheets on how to set it up by doing key word search of “SPI mode”.

MotionProcessing is a term that collectively refers to 1) the integration of hardware sensors, such as the gyroscope, accelerometer, and compass 2) A computation engine for combining data from the individual sensors 3) Algorithms for calibration of sensor data.

The motion algorithms has two major components to it, sensor fusion and calibration. Sensor fusion runs on the DMP (in hardware), while calibration runs on the micro. The hardware sensors (Gyro, and Accel) detect motion, while the BSP has manages the I2c, Timer, and Non volatile memory interfaces. The hardware does perform 6-axis (dof) sensor fusion through the dedicated DMP computation engine. The next release of Embedded MPL software will enable 9-axis sensor fusion that runs in a fully self contained fashion on the DMP. Currently the DMP does not support 9-axis sensor fusion due to a degraded performance. We are planning to eventually push full 9-axis operation to the DMP.
10 axis (altitude) sensor fusions can be performed on the MCU by taking the 9-axis sensor fusion results from hardware, and combining with altitude information from a pressure sensor.