Re: STM32 backbone library

2018-03-28 Thread markus
That is an excellent question. After reading the statements more carefully it seems ST reserves the right for none-portability: "... The HAL and LL are complementary and cover a wide range of applications requirements: * The HAL offers high-level and feature-oriented APIs, with a high

Re: STM32 backbone library

2018-03-28 Thread Fabio Utzig
On Tue, Mar 27, 2018, at 3:45 PM, markus wrote: > Hey Miguel, > > as you can tell - still causing trouble ;) > > I should have mentioned that both APIs, LL (low level) and HAL (high > level) are provided by ST Microelectronics and are part of their SDKs. > > Although the LL API is called "low

Re: STM32 backbone library

2018-03-27 Thread markus
Hey Miguel, as you can tell - still causing trouble ;) I should have mentioned that both APIs, LL (low level) and HAL (high level) are provided by ST Microelectronics and are part of their SDKs. Although the LL API is called "low level" it is still portable between the different STM32 processor

STM32 backbone library

2018-03-27 Thread markus
I have a PWM implementation for the STM32 (currently F3 & F7) but I'm not happy with it - which is why there currently is no PR. Most of what I want to change is the use of the backend library, using the LL api instead of HAL. All STM32 bindings I could find in mynewt are based on the HAL library