-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CubeMX #125
Comments
@FerdinandEn , did you follow the steps in this ReadMe |
CMSIS Toolbox is 2.3.0 For the CubeMX-Example: STM32U5xx_DFP::3,0,0-dev0
now leads to the error
After change of CubeMX.cbuild-pack.yml to dev1 CubeMX opens. I was then able to carry out all further steps successfully. |
Thanks a lot for your feedback and the hint that the cbuild-pack.yml is locking the BSP to 2.0.0-dev0. As you can see here: https://github.com/Open-CMSIS-Pack/pack-examples we do not currently have the STM32F7 pack in the works yet. |
After successfully completing the steps for using CubeMX, I wanted to gain some more experience. When opening Software Components, I received the following error message: I am trying to set up a new project with the board. At first I was able to enter all the settings in Software Components. However, I noticed that the dev packs were not used. After switching to the dev packs, I could no longer use Software Components I have another question: If I convert a STM32 project with uVision and then to VS Code. Can I then open CubeMX directly and adjust the settings? The following templates are used for CubeMX in uVision FrameworkCubeMX_gpdsc.ftl The templates are missing when opening CubeMX directly. |
The first problem you report, looks like an extension specific issue that should be reported here: On the second topic, we are in the process of moving away from gpdsc, replacing this with the global generator. In MDK uVision 5.40 we will start supporting the global generator. We will no longer rely on the above mentioned ftl file shipped as part of the STM32*_DFP packs. Instead the cbridge is handling the data/file conversion. |
Thanks for the information. |
I have now succeeded in creating a new project for the STM32U585AIIx. To do this, however, I had to make some changes in various yml files. If you are interested I can describe my approach. |
Yes, please I would be interested in your approach. |
Packs for STM32U5xx included with cpackget add New Solution Project with (create a new solution) Target Device: STM32U585AIIx CubeMX.csolution.yml
CubeMX.cbuild-pack.yml
CubeMX.cproject.yml
Use csolution CubeMX.csolution.yml list generators --verbose to get registered Generators CubeMX (Global Registered Generator) Use csolution CubeMX.csolution.yml run --generator CubeMX --context CubeMX.Debug+STM32U585AIIx -> CubeMX is started -> make settings -> generate code Use cbuild CubeMX.csolution.yml --update-rte info cbuild: build finished successfully! Now new pack components can be selected, e.g. RTOS2 e.g. Keil RTX5
Use cbuild CubeMX.csolution.yml --update-rte info cbuild: build finished successfully! Unfortunately, I don't have a board to test the program |
I have tried to create a CubeMX project (STM32F756) directly in VSCode. When I call the customized line in VSCode I only get the information that the exit code is 1.
Do I need a new version of the F7 pack to be able to reproduce the procedure?
I can't reproduce the example either, as I don't have the U585I packs with the required version.
The text was updated successfully, but these errors were encountered: