Hello, just a question here. I'm totally new to the stm32 platform and was looking to get a dev board. I would like to try some of the examples from this repository to get a feeling of how things works. I understand there are examples available for a NUCLEO-L476RG + X-NUCLEO-IKS01A2, but I was looking to buy the B-L475E-IOT01A Discovery. I've notice there is not much difference in the MCU (lcd pins only??) and the set of sensors is not all that different.
My question is: will I be able to run the examples on the B-L475E-IOT01A Discovery without too much trouble being a total beginner on this platform?
Thank you

Hi everyone!
I want to use Motion Libraries on STM32MP (only Cortex-M4 core), but in CubeMX i get warning: "This pack does not support STM32MP1 Series".

Describe the set-up:

My board: STM32MP157A-DK1
My IDE: STM32CubeIDE 1.7.0
Libraries: MotionFX,MotionMC,MotionVC

The STM32MP has the same Cortex-M4 core as in many other microcontrollers running these libraries. How can I solve the problem?

How to get the MotionSensor Libraries working on other ARM Controllers?

I ported the MotionMC and MotionEC Lib (want to using the LSM303AGR) to our nRF52 but it get stuck inside MotionMC_manager_init function.

I think u set everything correct:

"-mfloat-abi=hard -mfpu=fpv4-sp-d16",
"-DFLOAT_ABI_HARD",
"-l:MotionMC_CM4F_wc32_ot_hard.a",
"-l:MotionEC_CM4F_wc32_ot_hard.a",

Or is it general impossible to port to other MCUs?

I see a list of drivers for supported MEMS
https://github.com/STMicroelectronics/X-CUBE-MEMS1/tree/main/Drivers/BSP/Components

I can't see iis3dwb, which can be used with MotionSP library.

Is there any plan to integrate this driver?

I see that in the PresenceDetection_STHS34PF80 example app the data collection method is implemented by changing the TIM3 period based on the desired ODR. Is the data ready bit being used in this example like when using the embedded algorithm. Is the data ready bit preferred for collecting data over using a timer?

Hi everyone,

I have a problem with the MotionDI library. I tried to calibrate the accelerometer, but it doesn't calculate the Bias and the SF matrix, they are 0.0. The calibration quality is MDI_CAL_OK after the first MotionDI_update function call, but the output values are totally wrong, more of the output values (Roatation[1] and Linear Acceleration) are oscillating.
Fun fact, that I tried to calibrate the accelerometer with the MotionAC library, and it worked really good on the same device, the quality was MDI_CAL_GOOD. I tried the 6 point calibration in both cases.
Configuration:
STM32F413
MotionDI_CM4F_wc32_ot_hard.a
ISM330DLC (but I wrote a driver manually, I use only the MotionDI from this repository)
Frequency: 100 Hz
iKnobs.AccKnob.CalType = MDI_CAL_ONETIME;
iKnobs.GyrKnob.CalType = MDI_CAL_CONTINUOUS;

The other knobs are the default, I didn't change it.

What am I doing wrong?

Thank you for your help!
Best regards,
Zalán Gyuricza

Hello!
Is there plan to add LSM303AH to the package in the near future?
Thanks

In this repo there is MotionSP.c which is at the moment version 2.2.0 30-May-2019

Inside the package FP-IND-PREDMNT1 version 2.4.0 I can find a different release of MotionSP.c (2.3.2 21-Oct-2020) which seems newer (from the release number), but is much smaller than this one (750 linesof code vs 1127).

Can someone clarify this?
Is it possible to have in a well know location (here?) the latest release of the ST Middleware (as an example MotionSP)?

Thanks

Hello!
Is there plan to add LSM303AH to the package in the near future?
Thanks

@cparata the official release v9.4.0 updated the driver for iis3dwb MEMS device to the latest commit in https://github.com/STMicroelectronics/iis3dwb-pid
But this introduced a potential array overflow, as described in these 2 unresolved issues (issue #6# and #7#)

Is it possible to jhave a look to them (and hopefully fix them)?
Thanks