Bosch Sensortec Community

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 
    SOLVED

    BMX055 Gyro High G Interrupt problem

    Highlighted
    AJT
    Member

    BMX055 Gyro High G Interrupt problem

    Hello there,

    I'm using a BMX0155 sensor connected to a STM32 thanks a SPI Bus.

    I've already implemented High-G interrupt for the accelerometer (IT is genererated when Accel X value is > 0.150g) and it works perfectly.

    After this implementation i tried to do the same thing for the gyroscope but without succes, here is some code :

    (a) Gyroscope register values :

    gyro_register_values.PNG

    (b) Gyroscope Interrupt register values :

    gyro_register_valuesIT.PNG

    So first, I  configure the right port the same way as i configured accelerometer IT port

    Then, I set GYRO registers with values of picture (a).

    Then I set IT GYRO registers with values of picture (b).

    finally i enable the right IT (high_en_z (bit 0) of 0x26 register is set)

    The fact is that the interrupt is generated (high_int (GYR 0x09) status flag is set and high_first_z (GYR 0x0C) is set too)...

    status_flags_value.PNG

    ... but i can't catch this IT with the STM32.

    Did i miss something with IT gyro configuration ?

    Thanks

    Regards

    Tags (1)
    2 REPLIES 2
    Community Moderator

    Re: BMX055 Gyro High G Interrupt problem

    Hi ,

    Pleaseconfigure BMX055 Gyro High Rate Interrupt as below,  it should  work.

    1.png

     

    AJT
    Member

    Re: BMX055 Gyro High G Interrupt problem

    Thanks for your anwser.

    I've checked with the oscilloscope and an IT is generated but the problem comes from the STM32 that doesn't catch it.

    I' ve another problem, in latched mode, status flags are reset whereas i do not set reset_int bit... any idea ?

    PS : i've tried to map accel IT to INT1 and INT2 and both are ok.

    [EDIT] : It seems that gyro electrical behavior register init value (0x0F) is not the same as the accelometer (0x05). Switching STM32 pin to pull down mode has fixed my problem.

    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