In all examples from Hands-on Workshop "Developing with Sensors Made Simple"(pdf) the blue button interrupt is forgotten? Especially in LAB 5?

[AZakr.1]

When I press the blue button, the example applications die :( (especially in LAB 5 where blue is a single or double click switch)

[Peter BENSCH]

The Blue Button does trigger an interrupt, but the interrupt function was not used/implemented in Lab5, so pressing it does not lead to any meaningful result.

However, you have misunderstood the goal of Lab5: Tap and Double Tap are not triggered by the Blue Button, but by the sensor LSM6DSO, which is located on the X-NUCLEO-IKS01A3 used in the Lab.

Does it answer your question?

Regards

/Peter

[AZakr.1]

Thank you very much for your response.

Unfortunately, it is probably wrong. Sorry.

Please read carefully the readme.txt file contained in the LSM6DSO_SingleDoubleTap folder of the X-CUBE-MEMS1 package.

I will quote you an important passage:

"After application is started: - the user can try to tap the STM32 Nucleo board; when the single tap is detected, the LED is switched on for a while. Press the user button to pass from the single tap detection to the double tap detection feature. When the double tap is detected, the LED is switched on twice for a while. Press again the user button to disable the single / double tap detection feature. Press the user button to enable again the single tap detection feature and so on. "

The mode switching functionality described above probably does not work due to a misconfiguration EXTI_line [15:10] interrupt. The same mistake probably occurs in all Hands-on Workshop "Developing with Sensors Made Simple" (pdf) exercises. I am writing probably because I am a novice programmer and I am looking for a competent explanation of this strange situation. I might be wrong. But your explanation is probably superficial.

If you can, code Lab5 and share the result.

Regards

Adam