Skip to main content
Graduate
July 3, 2024
Question

IMU sensors with DatalogTerminal not working properly

  • July 3, 2024
  • 2 replies
  • 2153 views

Hi, im using the nucleo F401RE with the X-NUCLEO IKS01A3 and the Steval MKI197v1, i used CubeMX to insert the x-mems1 library, the aplication DataLogTerminal and only selected the LSM6DSOX sensor (steval).

I set the LSM6DSOX's SA0 pin to GND to prevent address conflicts, the I2C to Fast Speed Mode and ran the code generated on STM32CubeIDE.

When first launched it worked nice, but as i unplug the board and plug it back again it wont work anymore. Not even after compiling it again.

The only way i found to make it work again is to upload a different code on the nucleo and after that, upload the troublesome code.

 

Any advice on this? I attack the .ioc below.

 

Thanks in advance.

    This topic has been closed for replies.

    2 replies

    Super User
    July 3, 2024

    @aesteban wrote:

    as i unplug the board and plug it back again it wont work anymore. .


    You've mentioned three boards:

    1. Nucleo F401RE
    2. X-NUCLEO IKS01A3
    3. Steval MKI197v1

    So which one(s) are you plugging & unplugging?

     

    aestebanAuthor
    Graduate
    July 3, 2024

    Im conecting the MKI through the IKS's DIL24 and the IKS on the nucleo's Arduino pins, and im unpluging the nucleo-pc cable

    Super User
    July 3, 2024

    So you're unplugging the USB cable from the built-in ST-Link on the Nucleo board ?

    AndrewNeil_0-1720022535806.png

     

    So long as you don't do that during programming, that shouldn't be a problem.

    Probably not a good idea to do it during a debug session.

     

    aestebanAuthor
    Graduate
    July 8, 2024

    Ironically enough, the fault analisis display no faults... While i'm on the HardFault_Handler

    aesteban_0-1720422126115.png

    I don't really know what to do about this issue as I ran the same program but with other sensors and they doesn't show this problem, I have another Steval MKI197v1 just to check that it wasn't a sensor related issue.

    If (for example) i use the IKS sensors only, they work without an issue so i think it might be a library issue?