macos_mios32_toolchain_core
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| macos_mios32_toolchain_core [2013/11/05 23:54] – updated link to mios32_toolchain admin | macos_mios32_toolchain_core [2014/03/12 21:34] (current) – admin | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====How to set up the toolchain for coding MIOS32 apps with OS X==== | ====How to set up the toolchain for coding MIOS32 apps with OS X==== | ||
| - | |||
| - | You have probably already installed the developer tools (Xcode) provided by Apple. You need them before going further. | ||
| - | Xcode is located on the MacOS Installation DVD, but the most recent version can also be downloaded from [[http:// | ||
| ===steps: | ===steps: | ||
| - | 0- about the terminal\\ | + | 0- install Xcode\\ |
| - | 1- get the mios32 files from the repository server\\ | + | 1- about the terminal\\ |
| - | 2- install the MIOS32 toolchain\\ | + | 2- get the mios32 files from the repository server\\ |
| - | 3- configure the paths\\ | + | 3- install the MIOS32 toolchain\\ |
| - | 4- other derivatives\\ | + | 4- configure the paths\\ |
| + | 5- other derivatives\\ | ||
| + | |||
| + | ===1- install Xcode=== | ||
| + | |||
| + | Xcode is a toolchain from Apple with a powerful IDE, which can be downloaded for free in the App Store. | ||
| + | |||
| + | Even if you don't use the source code editor of this IDE, you have to install Xcode in order get access to the command line tools, such as " | ||
| - | ===0- about the terminal=== | + | ===1- about the terminal=== |
| Most of the things now will be done with the Terminal, if you don't know anything about it here are the basic commands you need: | Most of the things now will be done with the Terminal, if you don't know anything about it here are the basic commands you need: | ||
| Line 26: | Line 31: | ||
| A nice shortcut if you want to go to a particular folder without having to type the full path is to type "cd " in the terminal, then open the parent directory of the one you want to go in with the finder, and drag and drop the folder icon inside the terminal. It's path will appear by magic, press " | A nice shortcut if you want to go to a particular folder without having to type the full path is to type "cd " in the terminal, then open the parent directory of the one you want to go in with the finder, and drag and drop the folder icon inside the terminal. It's path will appear by magic, press " | ||
| - | ===1- get the files from the repository server=== | + | ===2- get the files from the repository server=== |
| TK proposes to use the " | TK proposes to use the " | ||
| Line 48: | Line 53: | ||
| In the " | In the " | ||
| - | ===2- install the MIOS32 toolchain=== | + | ===3- install the MIOS32 toolchain=== |
| The MIDIbox community have created a modified GNU Compiler Collection, ready for use with the ARM Cortex M3 platform. The toolchain contains all of the tools required to build MIOS32 applications including GCC and NEWLIB. | The MIDIbox community have created a modified GNU Compiler Collection, ready for use with the ARM Cortex M3 platform. The toolchain contains all of the tools required to build MIOS32 applications including GCC and NEWLIB. | ||
| Line 60: | Line 65: | ||
| 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 (/ | ||
| - | ===3- set up the paths variables=== | + | ===4- set up the paths variables=== |
| For those who don't know anything about Unix like me a few days ago, here's a quick explanation: | For those who don't know anything about Unix like me a few days ago, here's a quick explanation: | ||
| Line 102: | Line 107: | ||
| LCD: | LCD: | ||
| -------------------------------------------------------------------------------'' | -------------------------------------------------------------------------------'' | ||
| - | and with the finder, go to this tutorial folder, you should have now a .hex file uploadable to your core32 with " | + | and with the finder, go to this tutorial folder, you should have now a .hex file uploadable to your core32 with MIOS Studio. |
| The annoying point there is that the variables you set up in the shell just disappear when you shut down or log off your computer. That means you have to set them up again when you power on your computer again. There' | The annoying point there is that the variables you set up in the shell just disappear when you shut down or log off your computer. That means you have to set them up again when you power on your computer again. There' | ||
| Line 137: | Line 142: | ||
| - | ===4- other derivatives=== | + | ===5- other derivatives=== |
| - | For STM32 running on a MBHP_CORE_STM32 board use following setup: | + | For STM32F1 |
| '' | '' | ||
| Line 159: | Line 164: | ||
| export MIOS32_BOARD=MBHP_CORE_LPC17\\ | export MIOS32_BOARD=MBHP_CORE_LPC17\\ | ||
| export MIOS32_LCD=universal'' | export MIOS32_LCD=universal'' | ||
| + | |||
| + | |||
| + | For STM32F4 running on a MBHP_CORE_STM32F4 board use following setup: | ||
| + | |||
| + | '' | ||
| + | export MIOS32_BIN_PATH=$MIOS_PATH/ | ||
| + | export MIOS32_GCC_PREFIX=arm-none-eabi\\ | ||
| + | export MIOS32_FAMILY=STM32F4xx\\ | ||
| + | export MIOS32_PROCESSOR=STM32F407VG\\ | ||
| + | export MIOS32_BOARD=MBHP_CORE_STM32F4\\ | ||
| + | export MIOS32_LCD=universal'' | ||
| + | |||
macos_mios32_toolchain_core.1383695648.txt.gz · Last modified: 2013/11/05 23:54 by admin