Bosch Sensortec Community

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    BHI160 IMU Accelerometer INT pin not getting high after initialization

    kgoveas
    Community Moderator

    Re: BHI160 IMU Accelerometer INT pin not getting high after initialization

    Hi yogansh,

    The part numbers you sent earlier confirms that you are using the BHI160-B(di03) sample. It is hence strange to see that it initializes successfully with the BHI160 firmware based on the di01 edition.

    How are you controlling the BHI160? Do you have some driver that initializes and controls the sensor? Can you link it here?

    Regards,

    kgoveas

    yogansh
    Member

    Re: BHI160 IMU Accelerometer INT pin not getting high after initialization

     Hi kgoveas, 

    The code is working fine with BHI160 shuttle board with stm32 for that, I have converted this GitHub library. but the same code with the same chip it is not working in PCB (schematics already sent). I have checked connections in the PCB everything looks fine. so I again tried to code with different firmware this time it fails to initialize but INT is getting low and High, which in case of previous firmware initialized properly but not getting High after low.

    regards,

    Yogansh

    o_o
    Contributor

    Re: BHI160 IMU Accelerometer INT pin not getting high after initialization


    @yogansh wrote:

    With BHI160 Bosch_PCB_7183_di01_BMI160-7183_di01.2.1.10836_170103.fw  :-

    1) Successfully  initialized

    2) The interrupt is NOT getting High after it gets Low

    3) no data again.


     

    10836 is the correct firmware to use with BHI160.

    11696 is the correct firmware to use with BHI160B.

    The boot process goes like this:

    1. Power-on
    2. INT goes high (ready to receive firmware)
    3. FW download
    4. reset (INT goes low)
    5. Initialization
    6. INT goes high (some bytes in FIFO with initial meta event)
    7. Normal behavior. INT is high when bytes are in the FIFO, and goes low when the FIFO is emptied.

     

    Note that the sensor does not sample data on its own, therefore is no virtual sensor is enabled, you will only get one interrupt, with the initialization status. When you mentionned:


    @yogansh wrote:

    1) Successfully  initialized


    It means that you received the first interrupt ? In this case simply enable some virtual sensors.

    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