X-NUCLEO IKS4A1 with X-NUCLEO-6283A1

[AlexJ]

Hello,

I'm facing some trouble with interfacing these two boards.

Right now, I had only configured cube to load the datalogger example.

It's running fine without the 6283A1 but when I plug it on the IKS4A1, the code crash.

While debugging, I found that when the 6283A1 is not installed, the "configuration" variable is correctly filled with correct function pointer :

But when the 6283A1 is inserted, not all the variable is filled and the code is trying to execute a function that's not registered in the variable :

MotionFuncDrv[1][1]->GetAxes

I think it's a bug in the IKS library, the color sensor may have been interpreted as the LSM6 ?

Althought, the I2C bus is working fine.

Without the color sensor :

Searching for I2C devices on the bus...
Device found: 0x32
Device found: 0x3C
Device found: 0x70
Device found: 0x88
Device found: 0xBA
Device found: 0xD4
Device found: 0xD6
Total found devices: 7

With the color sensor :

Searching for I2C devices on the bus...
Device found: 0x32
Device found: 0x3C
Device found: 0x40 (*** VD6283A1)
Device found: 0x70
Device found: 0x80 (*** INA226)
Device found: 0x88
Device found: 0xBA
Device found: 0xD4
Device found: 0xD6
Total found devices: 9

Any help will be welcomed

[Miroslav BATEK]

Hello @AlexJ 

I have tried to replicate your setup using NUCLEO-F401RE + X-NUCLEO-IKS4A1 + X-NUCLEO-6283A1. I tested DatalogTerminal and DatalogExtended from the X-CUBE-MEMS1 package, as well as the 6283A1_LuxCCT example from the X-CUBE-ALS package. All the examples worked fine and communicated with the sensors. So, from the hardware point of view, it should be OK, and there might be a bug in the firmware. Could you please double-check your project or alternatively share it with me so I can review it?