Arduino for STM32

Dont try to modify the code written for another core. Take a look at the Timer documentation for the stm32duino core
https://github.com/stm32duino/wiki/wiki ... y#Examples
The InputCapture.ino example should help with configuring timers and attaching an input capture interrupt.

I downloaded and tried to code some encoder stuff onto a Nucleo L476 board. Starting from a Arduino 1.8 installation with stm32duino I downloaded IDE 2.0 and started the new IDE. After adding the the STM32Duino additional board manager path https://github.com/stm32duino/BoardManagerFiles/raw/master/...

Since both inputs are on the same timer, TIM2, there should be only one HardwareTimer object, and both channels should be configured for this timer.

How is the display connected to the SM32, what pins ?
What core are you using, what board and variant selection ?

Try pins PA2 and PA3, or pD8 and PD9, it looks like PA10 and PA9 are connected to the debug ST-Link

Just as the error message states: The FTDI adapter is not a ( ST-Link ) debug probe. The FTDI is opened as a serial port on the Linux side and also when connected to the STM32F103C, I assume it is connected to RX and TX pins. So for STM32_Programmer_CLI you must give the serial port on Arch Linux th...

The analogRead() function is very generic, and it intializes and deinitializes the HAL ADC layer for every call. A quick test on a F407 Discovery board gave around 60uS per call or 18kHz sampling frequency. If you do your own calls to the HAL layer, this can be improved a lot. I tested the code from...

You can use PWM outputs for precisely timed sequences of pulses, or make it yourself using the timer library, its really convenient but the interrupt overhead in HAL for attach'd interrupts is a bit long, depends on your speed and timing requirements. Another pattern for timed events is something li...

Looking at the source code in the Low Power library: https://github.com/stm32duino/STM32LowPower void STM32LowPower::attachInterruptWakeup(uint32_t pin, voidFuncPtrVoid callback, uint32_t mode, LP_Mode LowPowerMode) this function does two things, it attaches the pin interrupt and it enables the pin ...

I dont have the hardware to test but if the LSE runs correctly when not sleeping then my wild guess would be that the core somehow switches to LSI when sleeping.