Loading...
 

Zephyr project on STM32

   Zephyr Workbench, a VSCode extension to manage Zephyr on STM32.
It enables users to easily create, develop, and debug Zephyr applications.
Main features:
  • Install host dependencies.
  • Import toolchain and SDK.
  • Create, configure, build and manage apps.
  • Debug STM32.
You can directly download it from the VSCode marketplace
For more details, visit the Zephyr Workbench

System Workbench for STM32

Forum List Topic List

[ prev topic | next topic ]  

Creating a project with CMSIS drivers

Posted by TheSoundMan000 on 2018-07-06 12:49

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

Reads: 5558
Link
Posted by tarek bouchkati on 2018-07-12 11:57 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

Link
Posted by TheSoundMan000 on 2018-07-12 12:18

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?

Link

Posted by tarek bouchkati on 2018-07-12 14:53 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

Link

 

Newest Forum Posts

  1. Монтаж камина с грилем в Москве - установка и барбекю by KpddomErorb, 2025-05-10 18:28
  2. SPI on Nucleo_STMH533RE by royjamil, 2025-05-04 20:13
  3. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-25 07:37
  4. SPI on Nucleo_STMH533RE by royjamil, 2025-03-23 11:31
  5. SPI on Nucleo_STMH533RE by higginsa1, 2025-03-23 09:33
  6. Configuring DMA for ADC in SW? by sam.hodgson, 2025-03-04 12:58
  7. Build a project in "release" mode by info@creosrl.it, 2025-02-20 18:12
  8. Build a project in "release" mode by info@creosrl.it, 2025-02-20 17:05
  9. Build a project in "release" mode by tang, 2025-02-20 10:36
  10. Build a project in "release" mode by info@creosrl.it, 2025-02-19 17:35

Last-Modified Blogs

  1. System Workbench for STM32