Bosch Sensortec Community

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    BMA253 READING CHIP ID ERROR

    Occasional Visitor

    BMA253 READING CHIP ID ERROR

    I am interfacing the BMA253 with STM32 Discovery Board using 4 wire SPI. As a first step, I am trying to read the CHIP ID from the sensor register 0x00. The chip which should be read is 0xFA. The following code is added in the while loop just for the purpose of verification.


    uint8_t address = 0x00;
    while (1)
    {
    HAL_GPIO_WritePin(GPIOD, GPIO_PIN_2, GPIO_PIN_RESET);
    HAL_SPI_Transmit(&hspi1, &address, 1, 100);
    HAL_Delay (100);
    HAL_SPI_Receive(&hspi1, &result, 1, 100);
    HAL_Delay (100);
    HAL_GPIO_WritePin(GPIOD, GPIO_PIN_2, GPIO_PIN_SET);
    }

    Since it is in the infinite while loop, for the first two loop cycles I am getting 0xFF in the result. Then in the next two loop cycles, I am getting the correct Chip Id which is 0xFA. Then I am getting 0xFF in the next two loop cycles and this pattern is alternating infinitely.

    I am not able to understand why I am receiving 0xFF and then 0xFA.

    Could there be a problem with the delay mismatch? I feel that 100ms should be fine.

    I also feel that the SPI Receive is being incorrectly implemented. I am worrying because since SPI Read is an important function in retrieving the acceleration data, this function is the key.

    I request anyone to please suggest me on what to do to get it working perfectly. Any help would be highly appreciated.

    Thanks in advance.
    1 REPLY 1
    Highlighted
    Community Moderator

    Re: BMA253 READING CHIP ID ERROR

    Hi,

    Thanks for your inquiry. BMA253 supports SPI interface mode 0 and 3. The maximum SPI clock frequency is 10MHz. We have BMA253 shuttle board and APP2.0 base board availalbe in distributors such as Digikey, Mouser, Arrow and Future. You can purchase the eval. boards and then use logic analyzer to monitor the SPI bus to see how the waveforms look like. Then you can check the SPI communication on your own board.

    Most likely the issue comes from STM32 MCU SPI controller. Please ask them for technical support.

    Thanks.

    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