[Question] BMI270 : BMI2_E_CONFIG_LOAD

[Jet]

Hi Sir：

    Of cousre you can continue with that shuttle board, but first you should confirm your sensor chip with chip id because BMI260 and BMI270 are the same pin and package.

    And then correctly connect shuttle board pins to your platform.

    I use stm32F411 and shuttle board as well.

[Hugh]

Hi Jet,

I added one more "BMI4XX_REG_READ" to read the chip id correctly. "0x24" was read for the second try.

void StartBstTask(void const * argument)
{
    ...
    BMI4XX_REG_READ(BMI2_I2C_PRIM_ADDR,0x00,1);
    BMI4XX_REG_READ(BMI2_I2C_PRIM_ADDR,0x00,1);
    BMI270_MODULE_INIT(); 
}

And I checked all the 8K data with my logic analyzer and there was no problem.

But the result was "BMI2_E_CONFIG_LOAD" or "BMI2_E_DEV_NOT_FOUND" even with your reference code.

Now I suspect my BMI260_A2 shuttle board and am going to prepare another shuttle board which may take several weeks.

I will update the result then.

Thanks for your support,

Hugh

[Jet]

Hi Sir:

     Did you get data from register 0x21? what value?

     Did you observe the failure result during writing config file ? Like bmi2_set_adv_power_save()/set_config_load()/delay time/ SPI_CS voltage level after communcating.

    Recommend you to check these again.

[Hugh]

Hi Jet,

I've got a Bosch Sensortec application board 2.0 from my dealer.

I used Development Desktop 2.0, Bosch Sensortec application board 2.0, and my BMI260_A2 shuttle board and verified that my shuttle board works normally.

I captured the SPI packets and found that the downloaded 8K config file is different with https://github.com/BoschSensortec/BMI270-Sensor-API.

I applied the extracted config file from the SPI packets and it is initialized normally. I tried 1000 times and there were no error.

I'm asking to my dealer why I should replace the config file and to release an official config file for me.

Thanks,

Hugh

[Jet]

Hi Sir:

     I talked to our internal guys, currenly because lack the related shuttle board, only based on what you said, we can't figure out the reason why the config file of API was failure. I re-checked our shuttle boards and get the correct result.

     If you need to look for the root cause, recommend you to contact the local FAE and offer your shuttle board to do further analysis.