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

Forum List Topic List

You are viewing a reply to Project Migration from Coocox  
Posted by dautrevaux on 2016-10-26 09:49 France

Hi,

There is no automatic way to import Coocox projects in System Workbench for STM32. My best proposal to migrate from Coocox top System Workbench for STM32 would be:

  1. look at your Coocox project to check
    • what board/MCU you have selected
    • what firmware version you use
    • what additional (possibly third party) firmwares you use
      • FreeRTOS
      • STemWin
      • ...
    • what specific build options you added and list:
      • the defined symbols
      • the include paths pointing in your code (not the ones pointing in ST-provided firmware)
  2. Create, in a clean workspace, a System Workbench for STM32 project for the same board/MCU and using the same kind of library (StdPeriph or HAL) and additional firmwares used
  3. Import manually your source code in the src and inc folders of your new project (for source and header files respectively)
    • copy/paste directly from the Windows Explorer, MacOS Finder or Linux interface
    • do not import ST-provided firmware or header files
    • you may create subdirectories of these folders to clone your original project structure
  4. Check that you have all the symbols and include paths noted in the first step
    • create paths relative to the ProjDirPath variable (click on the Variables button in the path creation dialog)
    • don’t forget to create paths for all languages and configurations
    • there should already be
      • several workspace-relative paths to the ST firmware
      • the “${ProjDirPath}/inc”
      • additional project- or workspace-relative paths to third-party firmwares

Then you should be able to try to build your project and correct the possible errors. This is clearly not an automatic mechanism, but the structure of projects are quite different between Coocox and System Workbench for STM32 so a direct import of the project cannot work.

Bernard (Ac6)

Reads: 2233
Link