labapart / polymcu Goto Github PK

First, thanks a lot for working on this project. It's so helpful to have a CMake-based buildsystem for the ARM/CMSIS/FreeRTOS! I haven't worked much with other stacks but it's cool to know that I could use this if I wanted to.

The FreeRTOS application doesn't compile for the Arm Cortex M7 target out of the box because configMAX_SYSCALL_INTERRUPT_PRIORITY doesn't get set. I noticed that this gets set in board.h for the ARMCM4 target but not the M7. The way this is done in the ST Cube framework is by the application providing a separate FreeRTOSConfig.h header. What do you think of this pattern? It seems cleaner to me. For now I just throw the definition of the missing settings into board.h to be consistent with the other target as a workaround.

Just curious if this is somehow in the cope of the project at all...

Hi,

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

Thanks

Hi,

what kind of peripheral API do you propose for your eco system?
what do you think about CMSIS-Driver? is this suitable ?

it provides the interface for some of the most popular peripherals:
https://github.com/ARM-software/CMSIS/tree/master/CMSIS/Driver/DriverTemplates

I have only found few implementations of this CMSIS-Drivers.
NXP:
https://github.com/ARM-software/NXP_LPC/tree/master/LPC4300/CMSIS/Driver
"Freescale Kinetis K60 Series Device Support and Examples" from https://www.keil.com/dd2/pack/

STM32:
"STMicroelectronics STM32F4 Series Device Support, Drivers and Examples" from https://www.keil.com/dd2/pack/

Hi,

First: I'm not a firmware developer, I just muck around in firmware.

I'm attempting to bring in an existing STM32F466ret (?) based project in polymcu. Our project uses the Std Periph library, not the HAL. I was able to put our source code into the application folder and get it to start the build. I then turned my attention to the board/device support and started to notice some differences.

The CMSIS/core/include folder in polyMCU has a newer set of files from my download from STM32. That is confusing alone. Yours is v5.00, the currrent std periph download is 4.10. Also there are different files, some that are present in the F4 package. Notably core_cmSimd.h, core_cmFunc.h, core_cmInstr.h.

I don't know how to handle all these mismatches. Thoughts? Thanks for the neat tool!