linux_mios32_toolchain_core
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
linux_mios32_toolchain_core [2011/08/21 01:18] – admin | linux_mios32_toolchain_core [2024/05/23 19:46] (current) – phatline | ||
---|---|---|---|
Line 2: | Line 2: | ||
for MIOS32 application development on Linux | for MIOS32 application development on Linux | ||
- | \\ | ||
====== Preparation ====== | ====== Preparation ====== | ||
This document assumes that you have a relatively modern x86 based linux distribution. While it may work other distributions, | This document assumes that you have a relatively modern x86 based linux distribution. While it may work other distributions, | ||
Line 28: | Line 27: | ||
===== Linux build utilities ===== | ===== Linux build utilities ===== | ||
- | Depending upon your distribution, | + | Terminal commands |
- | * sudo aptitude install build-essential\\ | + | *** Debian/ |
+ | *** Arch Linux/ | ||
===== GNU Multiple Precision Library ===== | ===== GNU Multiple Precision Library ===== | ||
- | If you do not already have libgmp3-dev | + | Terminal Commands: |
- | | + | *** Arch Linux/ |
+ | *** Debian/ | ||
+ | **Ubuntu, | ||
+ | //sudo dpkg --add-architecture i386//\\ | ||
+ | //sudo apt-get update// | ||
+ | //sudo apt-get install libc6:i386 libstdc++6: | ||
+ | //sudo apt-get install libc6: | ||
+ | |||
+ | |||
===== MIOS32 Toolchain ===== | ===== MIOS32 Toolchain ===== | ||
Line 40: | Line 49: | ||
The Toolchain has currently been compiled for Windows (2000+), Mac OS X (Leopard or newer) and Linux x86 (built on Ubuntu 10.10).\\ | The Toolchain has currently been compiled for Windows (2000+), Mac OS X (Leopard or newer) and Linux x86 (built on Ubuntu 10.10).\\ | ||
\\ | \\ | ||
- | The download directory for the toolchain is ftp://ftp.lansystems.co.uk/pub/midibox\\ | + | The download directory for the toolchain is http://www.midibox.org/mios32_toolchain\\ |
\\ | \\ | ||
- | Download the latest "linux86" file and extract into your favorite directory, If you extract into /usr/local the toolchain will create / | + | Download the latest "linux" file and extract into your favorite directory, If you extract into /usr/local the toolchain will create / |
* cd /usr/local | * cd /usr/local | ||
- | * sudo wget ftp://ftp.lansystems.co.uk/pub/midibox/ | + | * sudo wget http://www.midibox.org/mios32_toolchain/gcc-arm-none-eabi-xxxxxx.tar.bz2 |
- | * sudo tar zxvf mios32_toolchain_linux86_xxxxxxxx.tgz | + | * sudo tar zxvf gcc-arm-none-eabi-xxxxxx.tar.bz2 |
\\ | \\ | ||
- | replace xxxxxxx with the date of the latest linux toolchain in ftp://ftp.lansystems.co.uk/pub/midibox\\ | + | replace xxxxxxx with the date of the latest linux toolchain in http://www.midibox.org/mios32_toolchain\\ |
\\ | \\ | ||
You now need to set the path variable for the toolchain bin directory (/ | You now need to set the path variable for the toolchain bin directory (/ | ||
Line 74: | Line 83: | ||
The following commands will setup the build environment for MIOS32, you must change MIOS32_PATH to be wherever you installed the svn repository: | The following commands will setup the build environment for MIOS32, you must change MIOS32_PATH to be wherever you installed the svn repository: | ||
- | * export MIOS32_PATH=~/ | + | * export MIOS32_PATH=~/ |
- | * export MIOS32_BIN_PATH=$MIOS32_PATH/ | + | * export MIOS32_BIN_PATH=$MIOS32_PATH/ |
- | * export MIOS32_GCC_PREFIX=arm-none-eabi | + | * export MIOS32_GCC_PREFIX=arm-none-eabi\\ |
- | * export MIOS32_FAMILY=STM32F10x | + | * export MIOS32_FAMILY=STM32F10x\\ |
- | * export MIOS32_PROCESSOR=STM32F103RE | + | * export MIOS32_PROCESSOR=STM32F103RE\\ |
- | * export MIOS32_BOARD=MBHP_CORE_STM32 | + | * export MIOS32_BOARD=MBHP_CORE_STM32\\ |
- | * export MIOS32_LCD=universal | + | * export MIOS32_LCD=universal\\ |
\\ | \\ | ||
\\ | \\ | ||
- | You can add these lines to your ~/.profile file to ensure that they are always set, the editor pico (or nano) is a fairly simple text editor but you may have your favourite. | + | You can add these lines to your ~/.profile file to ensure that they are always set, the editor pico (or nano) is a fairly simple text editor but you may have your favourite.\\ |
+ | \\ | ||
+ | __ | ||
+ | **If you know what you are Doing in Linux-you can do this systemwide: | ||
+ | open your filebrowser with sudo rights, for example type in terminal: | ||
+ | *** Linux Mint:** //sudo nemo// \\ | ||
+ | *** Linux Arch:** //sudo thunar// | ||
+ | the filebrowser now opens with root rights, navigate to the folder " | ||
+ | Depending on the path where your toolchain is situated, the Example Content off this file is:\\ | ||
+ | |||
+ | * PATH="/ | ||
+ | * MIOS32_PATH=/ | ||
+ | * MIOS32_BIN_PATH=/ | ||
+ | * MIOS32_BOARD=MBHP_CORE_STM32F4\\ | ||
+ | * MIOS32_FAMILY=STM32F4xx\\ | ||
+ | * MIOS32_GCC_PREFIX=arm-none-eabi\\ | ||
+ | * MIOS32_PROCESSOR=STM32F407VG\\ | ||
+ | * MIOS32_LCD=universal\\ | ||
+ | |||
+ | if you cant log after reboot, then mostly you messed up your " | ||
+ | |||
+ | **you can also add more folders to the PATH, they are separeted with a ":", | ||
+ | * PATH="/ | ||
+ | here we also have a folder named " | ||
+ | |||
===== Building your first application ===== | ===== Building your first application ===== | ||
Once you have completed the above steps, you should be able to build your first application. | Once you have completed the above steps, you should be able to build your first application. | ||
Line 89: | Line 123: | ||
* make | * make | ||
if this works great! If not, either you made a mistake (or I did!!) | if this works great! If not, either you made a mistake (or I did!!) | ||
- |
linux_mios32_toolchain_core.1313889533.txt.gz · Last modified: 2011/08/21 01:18 by admin