Loading...
 

SW4STM32 and SW4Linux fully supports the STM32MP1 asymmetric multicore Cortex/A7+M4 MPUs

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world. And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4.
You can get more information from the ac6-tools website and download (registration required) various documents highlighting:

System Workbench for STM32


Startup file selection: from ST or AC6?

Hi,

I tried the STM32CubeMX to generating the code and importing it in AC6 SWorkbench IDE. The API works, and I am using all the startup files from ST.

Now to use a framework I wrote, I do not need the automatic code generation, as the basics will be taken care of by the framework.
So I generated the project from AC6 and selecting my MCU (STM32F103C8T6), but the startup file generated is fairly different from the one used by STM.
I see different entries in the IVT, I do not see the boot RAM entry and the rest of the code is different. I am not expecting to see differences in the IVT, but the one in AC6 actually comprehends also entries of the higher range devices of the same family. This to me sounds like a red flag for nasty bugs.
So far I would continue by using instead the template from ST startup_stm32f103xb.s and trash the one generated by AC6, called startup_stm32.s

You can reproduce this by making a project from STM32CubeMX and comparing the startup by making the project fully inside EWB.

Do you know why I see this difference?

Thanks,