oh noes, error reading IMU!

[chenste]

Hello,

We are getting the following error from the OVC1 when we are trying to launch the driver:

We have not seen this error before. Do you have any idea on what would be causing it?

Best,
Steven

[codebot]

Only on a single device? Happens every time or only sometimes? Happens even after a full cold boot?

…

On Wed, Dec 12, 2018, 4:31 AM Steven Chen ***@***.*** wrote: Hello, We are getting the following error from the OVC1 when we are trying to launch the driver: [image: image] <https://user-images.githubusercontent.com/8302617/49828382-b8413d00-fd59-11e8-9429-851c0191dab8.png> We have not seen this error before. Do you have any idea on what would be causing it? Best, Steven — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#8>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFBR2vkuGPZyxmW4oEpdq7H6uHQBz_H-ks5u4BYpgaJpZM4ZOL1m> .

[chenste]

Thanks for the response. It happened when we plugged in a VLP-16 into it, and also by itself. This also happens after a full cold boot.

We originally did not have this problem and was able to launch the driver, but had to replace the lens mounts. After we replaced the lens mounts, we now get this error every time. We have run the reconfigure_fpga.sh and init_fpga.sh scripts in separate boots but still have this error.

[codebot]

Interesting. Was it powered when the VLP-16 was pluged in, or unpowered? I'm hoping static discharge didn't zap anything during the lens mount exchange, but it sounds suspicious.

Any chance that the new lens mounts or VLP wiring could be somehow shorting some pins or connector headers? If everything other than power+ethernet is unplugged, does anything change? If not, how about removing lens mounts?

Otherwise, the next level of debug would be to probe the IMU header (on bottom edge of board, underneath "AWESOMECAM") with a logic analyzer or oscilloscope and see if stuff is happening there. During the driver node startup, you should see some SPI traffic as it configures a few register settings, and after driver node startup, ideally you would see a 200 Hz pulse train on the SYNC_OUT pin and regular SPI traffic on {CS, SCK, MOSI, MISO} as it polls the readings.

The goal is just to try to figure out if the problem is "upstream" or "downstream" of the IMU.