vitorsousa

With DMP software, and the last byte as 0x01 - 200 khz I can see with a scope connected to the interrupt pin, a signal with a 200khz and in the middle, a not sistematic pulse. Is it possible that the configuration gives an interrupt for the data ready and another one for dmp ready, or magnetometer ready, or something like this? This happens before and after freezing. https://drive.google.com/open?id=0B1Wy4bjpCqH-YlZhR3hQTVNYS20ydkh0UTZmaFdDd3cwYlpF https://drive.google.com/open?id=0B1Wy4bjpCqH-TDE3YWM3SEpUWTY5bkFlb1poeUVOblRhVlBz in file motion_driver_test.c I can read the following at lines 578 to 589 Can be this the problem? /* * Known Bug - * DMP when enabled will sample sensor data at 200Hz and output to FIFO at the rate * specified in the dmp_set_fifo_rate API. The DMP will then sent an interrupt once * a sample has been put into the FIFO. Therefore if the dmp_set_fifo_rate is at 25Hz * there will be a 25Hz interrupt from the MPU device. * * There is a known issue in which if you do not enable DMP_FEATURE_TAP * then the interrupts will be at 200Hz even if fifo rate * is set at a different rate. To avoid this issue include the DMP_FEATURE_TAP */ How can I set DMP to obtain only one interrupt signal ? My last test with very last byte 0x01 set to 0x09 and setRate(9) doesn't stopped after 125 minutes and continues running