Bosch Sensortec Community

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    BMI088 Failed to read and write the configuration file

    BSTRobin
    Community Moderator

    Re: BMI088 Failed to read and write the configuration file

    Hello knieriem,

    For BMI088 read synchronized data example, you could refer to the attached code, which works well on STM32.

    knieriem
    Member

    Re: BMI088 Failed to read and write the configuration file

    Hi BSTRobin,

    thanks for providing the example code. I'm not using the data sync feature yet, but it's helful to be able to compare initialization steps. So I learned from the sources, that - after the soft reset - it may be good to set the accelerometer to active mode before writing the config file. I have been doing it in reversed order (which appears to work successful nevertheless; it seems writing the config file does not require normal mode)

    BSTRobin
    Community Moderator

    Re: BMI088 Failed to read and write the configuration file

    Hello knieriem,

    Before writing config file , accel should be set to active mode, gyro should be set to normal mode.

    knieriem
    Member

    Re: BMI088 Failed to read and write the configuration file

    Hello BSTRobin,

    thanks for that information.
    I found, though, that the examples of the official driver do it in reverse order:   

    1. load_config, then
    2. set power modes.

    See example 1, or example 2.

    So if power mode shall be set before loading the config file, the examples should possibly be adjusted.
    Should it be the case, though, that the order doesn't matter -- the order in the examples obviously also works (BMI08X_REG_ACCEL_INTERNAL_STAT == 1) --, then of course adjusting the example files is not necessary.

     

    BSTRobin
    Community Moderator

    Re: BMI088 Failed to read and write the configuration file

    Hello knieriem,

    For github code, device initialization sequence was updated for both BMI08x and BMI090L, which has caused for change in loading firmware directly after initialization. But the code works.

    Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist