| Installing and Activating Cross Development Environment |
 |
|
The Linux Cortex-M development software is distributed as a linux-<mcu>-<release>.tgz file available for download from the Emcraft site. That file can be installed to an arbitrary directory on your Linux development host, as follows: [psl@ocean SF]$ mkdir release You do not need to be the superuser (root) in order to install the Linux Cortex-M distribution. The installation can be performed from an arbitrary unprivileged user account. As a next step in the installation procedure, you need to download the GNU cross-build tools for Cortex-M. The tools are available from CodeSourcery and can be downloaded from the URL described below: It is recommended that you install the GNU development tools to the tools/ directory in the cross-development tree, as follows: [psl@ocean linux-cortexm-2.4.0]$ cd tools/ It is possible to install the tools to an alternative location, however, should you do that, you will need to modify the ACTIVATE.sh script to provide a correct path to the installed tools (specifically, PATH must include a correct path to the directory where you have installed the cross-tools).
[psl@ocean tools]$ tar xvfj arm-v7-linux-uclibceabi-pthreads-20161028.tar.bz2 The tools can be installed from an unprivileged account. In case you already have the toolchains installed on your development host (it would be the case, for instance, if you have more than one installation of the cross development environment on your host) and the underlying filesystem supports symbolic links (DOS FAT does not), you do not have to install the whole toolchains again. Instead, do the following: [psl@ocean linux-cortexm-2.4.0]$ cd tools/ Note: The CodeSourcery tools are 32-bit applications and need compatibility libraries to run on 64-bit Linux OS distributions. On the recent Fedora distributions, you need to install "glibc" and "zlib" i686 packages. On Debian, you need to install it by running Generally speaking, our customers do not have many issues (if any) with installation and activation of the development environment. For some reason, the most frequently occurring error is that people forget to run the activation script. This obviously results in insufficient path settings and the compiler failing to build sources for Cortex-M. The activation script needs to be run any time you start a development session. The script resides at the top of the installation directory: [psl@ocean release]$ cd linux-cortexm-2.4.0 An alternative way to run the script is to perform the following command: [psl@ocean linux-cortexm-2.4.0]$ source ACTIVATE.sh Whichever way you run the script, it sets a number of environment variables that are required for the cross development environment to function correctly. One of those variables is called MCU. The easy way to test if the cross development environment is active is to run the following command: [psl@ocean linux-cortexm-2.4.0]$ echo $MCU If MCU is empty or set to something other than STM32F7, this means that you have forgotten to run the activation script or somehow run it incorrectly. Some of our customers ask if the cross development environment can be run on a Windows host. We don't support Windows, however some of our customers have been successfully running the development environment on a virtual Linux machine under Windows. Again, we don't support that explicitly so if you want to try that, you are on your own. |