Openimu300ZI SPI communication using TX2 spidev

@cek
looking forward for your help.
Sincerely

@Li-YiFan
Sincerely looking forward for your help.

My SN number is 2008400344

@cek @Li-YiFan
Sincerely looking forward for your help.
My SN number is 2008400344

I have now recovered the whole EEPROM bin which I backed up.
Everything works fine, including all single reads and 0x3E burst read.
So maybe it confirms that the INS app from https://developers.aceinna.com/code/apps is having some problem(?
Or maybe the way I uploaded the firmware is incorrect.

Following the ST-link method instruction.
I did the folowing:

  1. download the bin file of firmwares
  2. start uploading from the address 0x08010000

Do I have to set the ending address or something?
If this is not the problem, then perhaps I 'll need to ask for a customized bin file with my SN number 2008400344.
And I'd like to have the VG_AHRS firmware.
I couldn't get data from VG_AHRS at first, so I turned to the INS app.
After all , I just want to get the angle data + rate data.

Truly appreciate!
Looking forward to any reply!

I noticed that there is an initialization issue in AHRS and INS app.
Is it necessary if I want to get data from burst read 0x3D?

@drib861204 Hi, I didn't have a 300zi available to do a tset as you said these days, but now I do and I will do a tset and reply you as soon as possible.

@Liang-Zhang Many thanks!
May I update what I've tried these days.
I used the upload function from vscode aceinna extension to upload VG_AHRS to my imu.(photo 1)
The imu output is the same as I downloaded the bin file from https://developers.aceinna.com/code/apps
They both can only answer to 0x56, 0x3E, etc, but not 0x3D and others.(photo 2)
So I feel like I skipped the initialization step of this app.
But still I have no idea how to initialize.
VSCodeToolBar.png
singleread.png

I solved the problem adding volatile to "data" in the function: void FillSPIBurstDataBuffer() inside UserMessagingSPI.c on VSCode open source VG-AHRS application.
VGAHRS_v3_code.png
Now I can finally get roll and pitch angles by sending 0x3D SPI command.
If this error happens to other openimu300zi's, then it is a freaking HUGE bug that should've been solved already.
Anyone suffers from the same problem? Or anyone uses SPI on openimu300zi and finds it works just fine? Let me know if you are in either of the situation. Thanks!

Hi folks
Here is the arduino codes I use, please use them if you need some quick setup.
https://www.dropbox.com/sh/v86c8owlpwf26k8/AADKFPKmRmg14mmroI32NZW3a?dl=0
openimu300zi.ino serial monitor:
VGAHRS_v3_2.png
openimu300zi_roll_pitch.ino serial plotter:
VGAHRS_v3_monitor.png

Log in to reply