linux_mios32_toolchain_core
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
linux_mios32_toolchain_core [2013/11/05 23:52] – changed link to toolchain admin | linux_mios32_toolchain_core [2024/05/23 19:45] – 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 ===== | ||
- | If you do not already have libgmp3-dev installed, you must install it (or lib32gmp3-dev if you are using an AMD64 version of linux). For Debian/ | ||
- | * sudo aptitude install libgmp3-dev (or lib32gmp3-dev) | ||
===== MIOS32 Toolchain ===== | ===== MIOS32 Toolchain ===== | ||
Line 74: | Line 72: | ||
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. |
linux_mios32_toolchain_core.txt · Last modified: 2024/05/23 19:46 by phatline