FlexSEA Wiki

A WEARABLE ROBOTICS TOOLKIT

User Tools

Site Tools


manage:software

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manage:software [2019/10/07 13:11]
jfduval [Troubleshooting!]
manage:software [2019/12/03 22:38]
jfduval [CLion]
Line 3: Line 3:
 ===== Overview ===== ===== Overview =====
  
-This page will get you up and running to write code for any STM32 microcontroller in a Dephy product. Over the course of the document we will cover installing the necessary tools, how to build the project for different applications and boards, and finally how to load the software onto the device.+This page will get you up and running to write code for any STM32 microcontroller in a Dephy product. Over the course of the document we will cover installing the necessary tools, how to build the project for different applications and boards, and finally how to load the software onto the device. To lean more about the build system refer to [[manage:​build_system|Dephy Build System]].
  
 ===== Setup ===== ===== Setup =====
Line 57: Line 57:
   * Navigate to the FlexSEA-Embedded-STM directory you previously cloned   * Navigate to the FlexSEA-Embedded-STM directory you previously cloned
   * Copy the file named workspace_template.xml in the .idea directory of this repository and rename it workspace.xml (replace the existing workspace.xml file if it exists). Make sure that you now have a file called workspace.xml in the .idea directory, this is where the CMake profiles for different build targets are stored and it is very important to have.   * Copy the file named workspace_template.xml in the .idea directory of this repository and rename it workspace.xml (replace the existing workspace.xml file if it exists). Make sure that you now have a file called workspace.xml in the .idea directory, this is where the CMake profiles for different build targets are stored and it is very important to have.
 +  * Copy the file named local_settings_template.sh in the main project directory of this repository and rename it local_settings.xml (replace the existing local_settings.sh file if it exists). Open it in a text editor and update the toolchain path.
   * You're now ready to open CLion and finish the setup   * You're now ready to open CLion and finish the setup
     * Open this project in CLion     * Open this project in CLion
Line 65: Line 66:
       * CLion will now restart       * CLion will now restart
     * Once CLion is open again click File -> Settings...     * Once CLion is open again click File -> Settings...
-    ​* Click the Appearance & Behavior tab on the left +      ​* Click the Appearance & Behavior tab on the left 
-    * Click on the Path Variables menu +      * Click on the Path Variables menu 
-    * Click the * symbol on the right to add a new path variable with the following info: +      * Click the * symbol on the right to add a new path variable with the following info: 
-      * Name: TOOLCHAIN_PATH +        * Name: TOOLCHAIN_PATH 
-      * Value: /​path/​to/​the/​toolchain/​gcc-arm-none-eabi-7-2018-q2-update +        * Value: /​path/​to/​the/​toolchain/​gcc-arm-none-eabi-7-2018-q2-update 
-        your path will probably look like "​C:​\toolchains\gcc-arm-none-eabi-7-2018-q2-update"​ or "/​home/​dephy/​toolchains/​gcc-arm-none-eabi-7-2018-q2-update"​+          Your path will probably look like "​C:​\toolchains\gcc-arm-none-eabi-7-2018-q2-update"​ or "/​home/​dephy/​toolchains/​gcc-arm-none-eabi-7-2018-q2-update"​ 
 +  * Run CMake update (within CLion) to confirm that it sees your toolchain
   * Congratulations,​ if you've been diligent in reading these instructions and these instructions are still accurate you should be good to go.   * Congratulations,​ if you've been diligent in reading these instructions and these instructions are still accurate you should be good to go.
 === Building === === Building ===
manage/software.txt · Last modified: 2019/12/03 22:38 by jfduval