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 families. The big advantage is that it is stateless, doesn't require big data structures, and allows finer control. HTH, Markus On Tue, 27 Mar 2018 17:54:47 +0000 Miguel Azevedo <miguella...@gmail.com> wrote: > Hey Markus! > How are you doing? > > Yes, In fact our Nordic drivers are a wraparound to the > manufacturer's drivers. So what is happening is [mynewt > driver]--->[nordic driver]--->[nordic hal]. Is this optimal? > No, but it works because Nordic works out every workaround for any > possible hw/hal bug. > This allows us to have a driver which works for all nRF52xxx chips. > I wouldn't oppose to have the same going on with STM(despite the fact > that I don't know much about their hw/libs). > I think a good person to ask this is Fabio Utzig, I believe he has > some experience with these boards and he's aware of how STM hw works. > :) > > Best Regards, > Miguel > > > On Tue, Mar 27, 2018 at 5:27 PM, markus <mar...@bibi.ca> wrote: > > 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 ... > > > > Is it acceptable to base a peripheral library on the LL api or is > > that not something to be done in mynewt? > > > > Have fun, > > Markus > > >
