User Tools

Site Tools


manual:demos:olimex_stm32p207_gcc

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
manual:demos:olimex_stm32p207_gcc [2016/07/23 18:32]
voorburg [Firmware update procedure]
manual:demos:olimex_stm32p207_gcc [2016/10/12 17:13]
voorburg
Line 14: Line 14:
 To program the bootloader into the internal flash on the STM32F207 microcontroller,​ the [[http://​www.segger.com/​development-tools.html|Segger J-Link]] JTAG interface was used. However, this is not required if you have another means of programming the internal flash. To program the bootloader into the internal flash on the STM32F207 microcontroller,​ the [[http://​www.segger.com/​development-tools.html|Segger J-Link]] JTAG interface was used. However, this is not required if you have another means of programming the internal flash.
  
-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_0_42.zip?​linkonly|EmBitz version ​0.42}}.+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}}.
  
-Firmware ​update ​via the serial communication port are preconfigured to use USART3 on connector RS232_2 on the board.+Firmware ​updates ​via the serial communication port are preconfigured to use USART3 on connector RS232_2 on the board.
  
  
manual/demos/olimex_stm32p207_gcc.txt ยท Last modified: 2023/12/04 22:24 by voorburg