This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
manual:demos:nucleo_f091rc_gcc [2017/07/19 12:47] voorburg |
manual:demos:nucleo_f091rc_gcc [2017/07/19 15:09] voorburg [Development Environment] |
||
---|---|---|---|
Line 12: | Line 12: | ||
This demo is targeted towards the [[http://www.st.com/content/st_com/en/products/evaluation-tools/product-evaluation-tools/mcu-eval-tools/stm32-mcu-eval-tools/stm32-mcu-nucleo/nucleo-f091rc.html|Nucleo-F091RC]] board, with 256 kB internal Flash EEPROM and 32 kB internal RAM. | This demo is targeted towards the [[http://www.st.com/content/st_com/en/products/evaluation-tools/product-evaluation-tools/mcu-eval-tools/stm32-mcu-eval-tools/stm32-mcu-nucleo/nucleo-f091rc.html|Nucleo-F091RC]] board, with 256 kB internal Flash EEPROM and 32 kB internal RAM. | ||
- | To compile the demo programs you can use the [[http://www.emblocks.org/|EmBitz]] development environment from Em::Blocks. The version that was used to create these demo programs was {{:manual:embitz_1_00.zip?linkonly|EmBitz version 1.00}}. | + | To build the demo programs you can use the [[https://developer.arm.com/open-source/gnu-toolchain/gnu-rm|GNU ARM Embedded]] toolchain. |
To program the bootloader into the internal flash, the on-board ST-Link debugger interface was used. Firmware updates via the serial communication port are preconfigured to use the virtual COM-port offered by the ST-Link. This means that no additional hardware is needed, besides a standard micro-USB cable. | To program the bootloader into the internal flash, the on-board ST-Link debugger interface was used. Firmware updates via the serial communication port are preconfigured to use the virtual COM-port offered by the ST-Link. This means that no additional hardware is needed, besides a standard micro-USB cable. |