Differences

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

--- linux_mios32_toolchain_core [2024/04/05 15:20] – [Setup MIOS32 Environment] phatline
+++ linux_mios32_toolchain_core [2024/05/23 19:45] – phatline
@@ Line 2: / Line 2: @@
     for MIOS32 application development on Linux
- \\
 ====== Preparation ======
 This document assumes that you have a relatively modern x86 based linux distribution. While it may work other distributions, it has only been tested on x86 Ubuntu 10.10. Many of the commands, especially "aptitude" are only available on Debian derived distributions like Ubuntu.
@@ Line 32: / Line 31: @@
 *** Arch Linux/Manjaro:** //sudo pacman -S base-devel//\\
-===== GNU Multiple Precision Library =====
-Terminal Commands:\\
-*** Debian/Ubuntu/Mint:**// sudo aptitude install libgmp3-dev// (or //lib32gmp3-dev//   for AMD64Version)\\
-*** Arch Linux/Manjaro:** //sudo pacman -S gmp//\\
 ===== MIOS32 Toolchain =====
@@ Line 76: / 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:\\
-  * export MIOS32_PATH=~/midibox/mios32/trunk
+  * export MIOS32_PATH=~/midibox/mios32/trunk\\
-  * export MIOS32_BIN_PATH=$MIOS32_PATH/bin
+  * export MIOS32_BIN_PATH=$MIOS32_PATH/bin\\
-  * 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:**__\\
+**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//\\
+*** Linux Arch:** //sudo thunar//\\
 the filebrowser now opens with root rights, navigate to the folder "etc" open the file "environment" >>> **/etc/environment**\\
 Depending on the path where your toolchain is situated, the Example Content off this file is:\\
-//PATH="/home/autark/midibox/gcc-arm-none-eabi/bin"
+  * PATH="/home/autark/midibox/gcc-arm-none-eabi/bin"\\
+  * MIOS32_PATH=/home/autark/midibox/mios32\\
+  * MIOS32_BIN_PATH=/home/autark/midibox/mios32/bin\\
+  * 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 "PATH" variable, in this case, boot with Linuxbootstick, and remove the PATH - line...\\
-MIOS32_PATH=/home/autark/midibox/mios32
+**you can also add more folders to the PATH, they are separeted with a ":", for example:**\\
-MIOS32_BIN_PATH=/home/autark/midibox/mios32/bin
+* PATH="/home/autark/midibox/gcc-arm-none-eabi/bin:/home/autark/program"\\
-MIOS32_BOARD=MBHP_CORE_STM32F4
+here we also have a folder named "program", when you put in there "Mios Studio", then you can write in Terminal "Mios Studio" and mios studio will open\\
-MIOS32_FAMILY=STM32F4xx
-MIOS32_GCC_PREFIX=arm-none-eabi
-MIOS32_PROCESSOR=STM32F407VG
-MIOS32_LCD=universal//