-
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
In macOS, *.app applications is really just a folder of a special kind that the OS is displaying in a different way. The actual executable that is needed by the stm32pio to run to generate a code is located inside this .app folder. I've never used this new IDE though to tell you whether the embedded inside it CubeMX is suitable for code-generation. You can browse any .app folder via Finder by selecting it and clicking "Show package contents" in context menu. The default stm32pio parameter (that you see in the error message you mention) can give you a hint where to locate the executable binary. Then you can override the default parameter value in stm32pio.ini config file. |
Beta Was this translation helpful? Give feedback.
-
Yes, I am aware of it. :) This is the content of STM32CubeIDE.app: The only executable I see is that STM32CubeIDE but there is no trace of MX :( |
Beta Was this translation helpful? Give feedback.
-
FYI: I managed to install MX thanks to the answer given here. EDIT: I managed to run stm32pio but I noticed that I have Core/Src and Core/Inc that have the same content as the generated Src and Inc (e.g. there is a double main.c file). EDIT2: I was following the example but the "Other Toolchains (GPDSC)" is no longer supported. |
Beta Was this translation helpful? Give feedback.
-
I guess the default one is STM32CubeIDE now (see #113) |
Beta Was this translation helpful? Give feedback.
I guess the default one is STM32CubeIDE now (see #113)