Loading...
 

SW4STM32 and SW4Linux fully supports the STM32MP1 asymmetric multicore Cortex/A7+M4 MPUs

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world.
And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4.
You can get more information from the ac6-tools website and download two short videos (registration required) highlighting:

System Workbench for STM32


Creating a project with CMSIS drivers

Hi all,

I’ve been using this for a few days and I’ve had enough of the HAL constraining just about everything I do and otherwise interfering with basic tasks. I would like to start afresh on a new project based solely upon the CMSIS drivers... Except that there appears to be no way of doing so. How do I create a blank project which includes makefiles etc for the CMSIS *only*: No HAL no nothing just plain basic essentials. Any sort of guidance would be much appreciated.

Regards,
TheSoundMan

Tunisia

Hi,

If you have issues with HAL due to its level of abstraction, I suggest to use only the LL.
The Low Layer (LL) drivers are designed to offer a fast light-weight expert-oriented layer which is closer to the hardware than the HAL.

Any Way, if you don’t need any of them, you can select no firmware when creating your project. Then you are free to populate your project :-D

Regards,
Tarek

Thanks for the answer Tarek. I can’t really wait till September for the LL drivers unfortunately (H7 series LL drivers aren’t available). Agreed yes they are ideal I’ve used them before and have no issues with them at all but yeah unfortunately I don’t have that sort of time.

I’m asking specifically regarding the formation of a project with CMSIS drivers already populated. Selecting no firmware does exactly as its name implies and creates a blank project (no CMSIS) which doesn’t achieve the end goal and leaves it up to me (or any other user) to manually install themselves. Given the prevalence of CMSIS it’s rather disappointing there isn’t atleast the option to include them.

Creating a HAL based project to immediately delete HAL is an innefficient and dirty method of achieving the desired result but it’s the best one I’ve found. I’m really hoping we aren’t really expected to manually install such essential components every single time, maybe someone else can point me the right way?


Tunisia

I agree, this is inefficient. Unfortunately there is no tracker here for feature requests. So I escalated myself this request.
Just I wonder what do you mean by “manually install such essential components”, which components ?

Thank you,
Tarek