Is this project terminated without finish ?

[ranshalit]

Hi,

Is the purpose of the project to use stm32 with CMSIS driver ?
Is the project terminated without finish ?

Thanks

[oliviermartin]

Hi @ranshalit, this project already enables STM32. It has been validated with 'ST STM32L476 Nucleo'. The purpose of this project is to leverage semiconductor SDKs with CMSIS API and various RTOS (CMSIS RTOS, FreeRTOS).

[RussellHaley]

Sweat! So this is still a thing?

I'm a software developer that works with firmware (like a dog 'using' a computer). At work we have a project for a custom STM32F27... (somthing-rather) that is being built in Eclipse in Windows and Linux using the AC6/openSTM plugins. We use the CMSIS API. We ported the firmware over to another custom board using an STM32F... er STM32F446xx I think.

Anyway, I'd like to try a new build framework and this project has popped up twice now. I'm hoping to support clang in everywhere.

I'm not sure of all my options:

• I'll install cmake and clang
• I have a new-ish debian VM. In the SO post where I found this repo, another poster mentions needing to build clang for thumb? I'm a little familiar with building clang and specifying the target architectures.
• Do I just download this repo and drop my source code into the Application folder? Currently the source tree is

inc/
src/
#STM code
StdPeriph_Driver/
CMSIS/

• I also already have GNU Make in Windows 10 using Powershell. I can install Clang and I've also built it in WIndows with VS 2017 (slow on my laptop. tee hee).

I'm super pumped about the MicroPython support as the client requested scripting capabilities and rebuffed my Lua suggestion.

[RussellHaley]

Ha, this is pretty slick. The baremetal example builds for the ST Nucleo bsp on FreeBSD with the default clang compiler (does it have the correct instruction sets?). I've added my project files under Application and copied in the baremetal cmake files (CMakeLists.txt and Application.cmake). Cmake completes and the build started but I need to set some include paths.

Anyways, I think I should be able to add our board support pretty easily by just moving our existing ST code (noted in prior post) into the appropriate place. I have a EE available at work to help if I need it. If I get this working I'll push the board support for STM32F4xx up.

I have a TI Simplelink LaunchXL at work too but I seem to remember their software stack is much more complicated. A problem for another time...

Cheers!