Bosch Sensortec Community

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    BMI160: What exactly does INT_LATCH do?

    BMI160: What exactly does INT_LATCH do?

    IDEngineer
    Established Member

    Register 0x54 is "INT_LATCH". Bits 0-3 set the "interrupt mode", which has a range of values from "non-latched" to 312.5uS to 2.56s to "latched". The most descriptive explanation for what this does seems to be in section 2.11.7 of the spec sheet, which reads:

    "The setting of Register (0x54) INT_LATCH <3:0> controls if the interrupt signal and hence the respective interrupt flag will be permanently latched, temporarily latched or not latched."

    Does this mean that an active signal on the INT1 or INT2 pins will be "latched"? Or that you can set the pulse width of the INT signal, after which it will reset regardless of whether data has been read from the chip? Most importantly, what happens when you set INT_LATCH <3:0> to "latched"... does the INT pin go active one time and "latch" there FOREVER? How can that possibly be useful?

     

    2 REPLIES 2

    Vincent
    Community Moderator
    Community Moderator

    If you set as "latched (0b1111)" then the INT pin will be keep always active until you clear it or disable the INT. 

    If you set other values into the register, the the INT pin will keep active for selected time then deactive automatically whenever you read sensor register or not.  but if INT condition still meet afterwords, the INT pin will be active again.

    IDEngineer
    Established Member

    >>If you set other values into the register, the the INT pin will keep active for selected time then deactive automatically whenever you read sensor register or not. but if INT condition still meet afterwords, the INT pin will be active again.<<

    This sounds like the INT pin will oscillate until you "do something" to reset the interrupt condition:

    1) Interrupt condition occurs, so INT is taken active (and let's presume nobody reads registers nor does anything else to clear the interrupt condition)

    2) The configured amount of time elapses, so the INT pin goes inactive...

    3) ...but since the interrupt condition still exists, "the INT pin will be active again" for the configured amount of time

    4) Go to step number 2 above, and the INT pin pulses forever until someone clears the interrupt condition

    That doesn't sound correct. Does the chip REALLY behave like that?!?

    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