Standard Peripheral Libraries for STM32F7, STM32L4, and others
27 Comments
W
William Schindler
7 years ago
HAL is bloated, inefficient and horrible to debug. the SPL libraries were/are much simpler to use and resulted in better used flash space and readability.
W
William Schindler
7 years ago
HAL is bloated, inefficient and horrible to debug. the SPL libraries were/are much simpler to use and resulted in better used flash space and readability.
V
Vaishnavi V
7 years ago
standard peripheral library are best to understand how the micro controllers work. It would be nice if ST provides SPL for all controllers. Let the user choose SPL or HAL whatever needed
A
Anonymous
7 years ago
i choose flexible device ! so go on flexible and not to restricted
D
Dimitris Tassopoulos
8 years ago
Featured
Also, ST come on! You should target professionals mainly and not hobbyists. HAL is a hobbyist thing for people to play around in the free time is not a serious development platform. And have in mind, that I reject all the designs that spec stm32f7s. I hope that also other engineers do the same. It seems like boycott it's the only way to achieve the most sensible thing, getting back SPL for professional use.
D
Dimitris Tassopoulos
8 years ago
ST is becoming Nokia. Nobody seems to learn from others mistakes. They have an excellent product and SPL library and instead of keep like that and don't change a thing or just enhance the lib with a few soft libs that are commonly used in the industry, they decide to destroy everything. Usually, these are bad management decisions from people that they don't have an idea about product development and low embedded stuff. Probably, they've never worked professionally as embedded engineers, too. So one day, in order to present new power points to their bosses, they come up with a really bad idea and make it their life's purpose to push it down our throats. The result is that you either need to use this HAL abomination, move to another MCU or go 5+ years back and start writing cmsis again.
I can understand their need to support C++, but guys do it right. And also don't kill SPL. Don't become Nokia.
J
Juozas Kimtys
9 years ago
Featured
When, some years ago, HAL appears, I really want to study this new stuff as previously studied SPL. But, after, I found, that too many time I have to spend to adopt (without success) my SPI EEPROM 512kbit subroutine (in F4 project) - not success to write. Later, several times in different projects, I have observed how easier is to make result by using SPL and have stopped to try study HAL. But, today I want to make things by using STM32F745 and STM32F767 and I see, that without HAL I can make only LED blink (by using some hints currently available in Internet). Please provide SPL for F7 family!
J
Jeronimo Werder
9 years ago
Featured
I had many projects using the microcontrollers from ST together with the SPL libraries. In the meanwhile I created a lot of software modules based on SPL which I could reuse in other projects which become worthless with the new HAL libraries. So it would be a great benefit to proceed with the SPL libraries!
D
David
9 years ago
hal becomes more popular. faced it many times with different mcu's. Things getting bad...SPL was real thing for STM32 family mcu's.
But when you need compatibility, optimization or full hardware control,HAL becomes a real hell for any programmer. It has so many concepts from software developing, but its not for real time applications...where precise timers, uart,spi,can buses and etc... With hal these things going mad if you need a lot of customizing.
HAL libs just mess up all Real time operating system concepts. Mcu with HAL libs become to inaccurate heavy loaded pile of ****.
M
Marek Petrinec
9 years ago
Featured
As hardware developer i also need powerfull low lvl program. But i cannot optimize anything with hal drivers. STM32 are one of the best for me but not with hal drivers. Hal can use kids for learning without optimalization. Please provide it.
I
Ivan Ivanov
9 years ago
HAL has no proc for interconnect SPI and DMA. Assembler-way only with mask and addresses. SPL was better ! HAL is immature product !
P
Peter Harsch
9 years ago
Featured
Some of our currently manufactured devices are build around a STM32F3. We would like to switch to the STM32F7 but when looking at the HAL we decided to discontinue with STM32. Byebye ST.
G
Guillaume Lapalme-Thibault
9 years ago
Bring back the SPL library please!
B
Brian Beattie
9 years ago
The HAL libraries are much to convoluted and "heavy" for good engineering use. While I like the STM32 line of devices I may need to reconsider future designs.
P
Pedalero
9 years ago
Cube + HAL = terrible combination. Pls, return old good SPL!
P
Petar Donchev
9 years ago
No SPL? How to use my huge pile of code for F0,F1,F2,F3 and F4?
O
Omid
9 years ago
We need STD Periph for all ST Micro Controller
H
Hamed Roshanfekr
9 years ago
no professional company would accept using hal drivers.
R
Rob DA
9 years ago
Can't get code running on F7 using HAL libraries. Compiles, but stops running. Too much stuff hidden, and isn't portable between devices despite the literature!
N
Noam Weissman
9 years ago
Just started working on a project for STM32F765 ... F4 code should run but its not !!! HAL is horible
HAL is bloated, inefficient and horrible to debug. the SPL libraries were/are much simpler to use and resulted in better used flash space and readability.
HAL is bloated, inefficient and horrible to debug. the SPL libraries were/are much simpler to use and resulted in better used flash space and readability.
standard peripheral library are best to understand how the micro controllers work. It would be nice if ST provides SPL for all controllers. Let the user choose SPL or HAL whatever needed
i choose flexible device ! so go on flexible and not to restricted
Also, ST come on! You should target professionals mainly and not hobbyists. HAL is a hobbyist thing for people to play around in the free time is not a serious development platform. And have in mind, that I reject all the designs that spec stm32f7s. I hope that also other engineers do the same. It seems like boycott it's the only way to achieve the most sensible thing, getting back SPL for professional use.
ST is becoming Nokia. Nobody seems to learn from others mistakes. They have an excellent product and SPL library and instead of keep like that and don't change a thing or just enhance the lib with a few soft libs that are commonly used in the industry, they decide to destroy everything. Usually, these are bad management decisions from people that they don't have an idea about product development and low embedded stuff. Probably, they've never worked professionally as embedded engineers, too. So one day, in order to present new power points to their bosses, they come up with a really bad idea and make it their life's purpose to push it down our throats. The result is that you either need to use this HAL abomination, move to another MCU or go 5+ years back and start writing cmsis again. I can understand their need to support C++, but guys do it right. And also don't kill SPL. Don't become Nokia.
When, some years ago, HAL appears, I really want to study this new stuff as previously studied SPL. But, after, I found, that too many time I have to spend to adopt (without success) my SPI EEPROM 512kbit subroutine (in F4 project) - not success to write. Later, several times in different projects, I have observed how easier is to make result by using SPL and have stopped to try study HAL. But, today I want to make things by using STM32F745 and STM32F767 and I see, that without HAL I can make only LED blink (by using some hints currently available in Internet). Please provide SPL for F7 family!
I had many projects using the microcontrollers from ST together with the SPL libraries. In the meanwhile I created a lot of software modules based on SPL which I could reuse in other projects which become worthless with the new HAL libraries. So it would be a great benefit to proceed with the SPL libraries!
hal becomes more popular. faced it many times with different mcu's. Things getting bad...SPL was real thing for STM32 family mcu's. But when you need compatibility, optimization or full hardware control,HAL becomes a real hell for any programmer. It has so many concepts from software developing, but its not for real time applications...where precise timers, uart,spi,can buses and etc... With hal these things going mad if you need a lot of customizing. HAL libs just mess up all Real time operating system concepts. Mcu with HAL libs become to inaccurate heavy loaded pile of ****.
As hardware developer i also need powerfull low lvl program. But i cannot optimize anything with hal drivers. STM32 are one of the best for me but not with hal drivers. Hal can use kids for learning without optimalization. Please provide it.
HAL has no proc for interconnect SPI and DMA. Assembler-way only with mask and addresses. SPL was better ! HAL is immature product !
Some of our currently manufactured devices are build around a STM32F3. We would like to switch to the STM32F7 but when looking at the HAL we decided to discontinue with STM32. Byebye ST.
Bring back the SPL library please!
The HAL libraries are much to convoluted and "heavy" for good engineering use. While I like the STM32 line of devices I may need to reconsider future designs.
Cube + HAL = terrible combination. Pls, return old good SPL!
No SPL? How to use my huge pile of code for F0,F1,F2,F3 and F4?
We need STD Periph for all ST Micro Controller
no professional company would accept using hal drivers.
Can't get code running on F7 using HAL libraries. Compiles, but stops running. Too much stuff hidden, and isn't portable between devices despite the literature!
Just started working on a project for STM32F765 ... F4 code should run but its not !!! HAL is horible