Difference between revisions of "Nucleo Boards"
From RobolaboWiki
| Line 5: | Line 5: | ||
<h3> Installing dependencies </h3> | <h3> Installing dependencies </h3> | ||
| − | + | <h4>Dependencies for compilling. </h4> STM32CubeMX and STM32CubeIDE, in a command line, execute: | |
<pre> | <pre> | ||
sudo apt-get install build-essential gcc-arm-none-eabi libnewlib-arm-none-eabi libstdc++-arm-none-eabi-newlib | sudo apt-get install build-essential gcc-arm-none-eabi libnewlib-arm-none-eabi libstdc++-arm-none-eabi-newlib | ||
Revision as of 08:15, 29 July 2019
Contents
Configuring environment
Linux
Installing dependencies
Dependencies for compilling.
STM32CubeMX and STM32CubeIDE, in a command line, execute:sudo apt-get install build-essential gcc-arm-none-eabi libnewlib-arm-none-eabi libstdc++-arm-none-eabi-newlib
To install dependencies for flashing the microcontroller, in a command line, execute:
sudo apt-get install git cmake libusb-1.0-0-dev dfu-util
To install dependencies for debugging the microcontroller, in a command line, execute:
sudo apt-get install gdb
Moreover, stlink utility is mandatory to debug in a nucleo board, therefore in a command line, execute:
git clone https://github.com/texane/stlink.git cd stlink make cd build/Release sudo make install
References
https://nebkelectronics.wordpress.com/2016/12/19/the-stm32cube-library-part-1-toolchain/
https://nebkelectronics.wordpress.com/2016/12/24/stm32cube-library-part-2-hello-world/
https://nebkelectronics.wordpress.com/2017/10/08/stm32cube-library-part-3-compiling/
