I want to build a RTXV5 project based on stm32f103vct together with stm32cubeMX. I know how to start a new RTXV5 project , but when I update my keil to the version v5.24 I found I can not find the item"STM32Cube Framework API" on RTE > DEVIECE,there is only "StdPeriph Drivers" under DEVIEC item of RTE configuration. anyone came across the same problem ?why "STM32Cube Framework API" is replaced with "StdPeriph Drivers" in the DEVICE item of RTE configuration ??? thanks!
Did you install STCubeMX? Note: STCubeMX is not a Keil-, but a STMicroelectronics product, offered for download at: www.st.com/.../stm32cubemx.html
(You need to register at ST to download Cube, the tool is offered at the bottom of the site)
YES, I have installed STCubeMX,I have developed several projects using STCubeMX. My MDK version is v5.22, in the past I can use the CubeMX option in Keil RTE configuration. but when I update the ST CubeMX in the ST website ,the problem appeared :(
the problem is : I created a new keil project,and used the RTE to config RTX RTOS,then I found I there is no CubeMX option anymore.
pls note that the problem appeared after I update CubeMX. Is the updated CubeMX not compatible with MDK v5.22? Pls help me,thanks a lot!
I have the same problem. Ì read here www.keil.com/.../index.html Only F2 F4 and F7 are supported... are you sure stm32f103 works with previous version?
Yes, I have also read the related papers,and I have used the CubeMX option in Keil RTE successfully before I updated the ST CubeMX recently.
Hi,
Interesting, note that the CMSIS RTOS wrapper can also be used as an "interface" to the USB host module, the rest of the application can still use the native ChibiOS API.
I am thinking to add to the CMSIS wrapper a "interface-only" option, this option would export just the bare minimum CMSIS API in order for the ST/vendor drivers to work, the rest of the system would be ChibiOS-native. I think very little of CMSIS RTOS is strictly required.
Something that could be investigated: 1) Convert the internal CubeMX representation to a board.chcfg file (it is XML). 2) Convert the internal CumeMX representation to the clock settings in mcuconf.h.
The above changes would allow to use ST tools to generate ChibiOS-compliant settings.