This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
manual:demos:infineon_xmc1400_boot_kit_gcc [2016/12/21 11:23] voorburg removed |
manual:demos:infineon_xmc1400_boot_kit_gcc [2017/04/24 15:04] voorburg [Building the Demo Program] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== ARM-CM0 XMC1 Infineon XMC1400 Boot Kit IAR EWARM ====== | + | ====== ARM-CM0 XMC1 Infineon XMC1400 Boot Kit GCC Dave 4 ====== |
===== Supported firmware update interfaces ===== | ===== Supported firmware update interfaces ===== | ||
Line 8: | Line 8: | ||
===== Development Environment ===== | ===== Development Environment ===== | ||
- | {{:manual:demos:stm32f0_discovery.png?200 |}} | + | {{:manual:demos:infineon_xmc1400_boot_kit.jpg?200 |}} |
- | This demo is targeted towards the [[http://www.st.com/stm32f0discovery|STM32F0-Discovery]] board, with 64 kB internal Flash EEPROM and 8 kB internal RAM. | + | This demo is targeted towards the [[http://www.infineon.com/cms/en/product/evaluation-boards/KIT_XMC14_BOOT_001/productType.html?productType=5546d46250cc1fdf015144a2102e1191|Infineon XMC1400 Boot Kit]] board, with 200 kB internal Flash EEPROM and 16 kB internal RAM. |
- | To program the bootloader into the internal flash on the STM32F051 microcontroller, the on-board ST-Link Debugger 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 XMC1400 microcontroller, the on-board [[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.iar.com/|IAR Embedded Workbench for ARM]] development environment. | + | To compile the demo programs you can use the [[http://www.infineon.com/cms/en/product/microcontroller/32-bit-industrial-microcontroller-based-on-arm-registered-cortex-registered-m/dave-version-4-free-development-platform-for-code-generation/channel.html?channel=db3a30433580b37101359f8ee6963814|Dave (version 4)]] development environment for XMC microcontrollers. |
- | The [[https://www.olimex.com/Products/Components/Cables/USB-Serial-Cable/USB-Serial-Cable-F/|Olimex USB-Serial-Cable-F]] was used to create a connection between the STM32F051 USART2 serial peripheral and the PC's COM-port. The pin connections are as follows: | ||
- | * Blue cable to GND (ground pin) | + | ===== Workspace creation in Dave ===== |
- | * Green cable to PA2 (USART2 receive) | + | Two demo projects are included in the OpenBLT bootloader package. One for the bootloader itself and one for the demo user program. This user program is configured such that it can be programmed, into the internal flash memory of the microcontroller, during a firmware update with the bootloader. |
- | * Red cable to PA3 (USART2 transmit) | + | |
+ | The first step in getting the the bootloader up-and-running, is the creation of the Eclipse workspace in Dave. After starting Dave, you are prompted to open a workspace. It is easiest to create a new one in the following directory: .\Target\Demo\ARMCM0_XMC1_XMC1400_Boot_Kit_GCC\ | ||
+ | |||
+ | {{:manual:demos:infineon_xmc1400_dave_workspace_creation.png?550|}} | ||
+ | |||
+ | To import the demo programs into the workspace, select //File -> Import// from the program menu. Then select //Infineon -> DAVE Project//. On the next screen you select the following directory as the root directory: .\Target\Demo\ARMCM0_XMC1_XMC1400_Boot_Kit_GCC\. Eclipse will automatically find the **Boot** and **Prog** projects and select them: | ||
+ | |||
+ | {{:manual:demos:infineon_xmc1400_dave_project_import.png?455|}} | ||
+ | |||
+ | Click the //Finish// button to complete the project import operation. | ||
===== Building and programming the Bootloader ===== | ===== Building and programming the Bootloader ===== | ||
- | Before the bootloader can be used, it needs to be built and programmed into the STM32F051's internal flash memory. The steps in this section only need to be done once. | + | Before the bootloader can be used, it needs to be built and programmed into the XMC1400's internal flash memory. The steps in this section only need to be done once. |
- | When using IAR EWARM, simply open the workspace from within the Embedded Workbench. The workspace file (stm32f0.eww) is located at: \Target\Demo\ARMCM0_STM32F0_Discovery_STM32F051_IAR\**Boot**\ide\. Once opened, select //Project->Rebuild All// from the menu to compile all the bootloader sources and link them together into the final executable. | + | Set the project as the active project in Eclipse. This is achieved by right-clicking the **Boot** project in the project navigator called //C/C++ Projects//. From the context menu, select //Set Active Project//. Next, select //Project -> Rebuild Active Project// from the menu to compile all the bootloader sources and link them together into the final executable. |
- | The bootloader program is now ready to be programmed into the internal flash memory of the STM32F051. Make sure the ST-Link Debugger Interface on the STM32F0-Discovery board is connected to your PC via a USB cable. Next, select //Project -> Download and Debug (Ctrl+D)// from the menu to flash the bootloader program. Once done, you can start the bootloader program by selecting //Debug -> Go (F5)// from the menu. | + | The bootloader program is now ready to be programmed into the internal flash memory of the XMC1400. Make sure the XMC1400 Boot Kit is connected to your PC via a USB cable. Next, right-click the **Boot** project in the project navigator and select //Debug As -> Dave C/C++ Application// from the context menu to flash the bootloader program. This will launch the Debug perspective in Eclipse. Once done, you can start the bootloader program by clicking the green play button on the toolbar or by pressing F8 on the keyboard. |
Alternatively, you can use your favorite programmer to flash the bootloader using one of the following files, depending on what file type your programmer supports: | Alternatively, you can use your favorite programmer to flash the bootloader using one of the following files, depending on what file type your programmer supports: | ||
- | * \Target\Demo\ARMCM0_STM32F0_Discovery_STM32F051_IAR\**Boot**\bin\**openblt_stm32f051.out** | + | * \Target\Demo\ARMCM0_XMC1_XMC1400_Boot_Kit_GCC\**Boot**\Debug\**openblt_xmc1400.elf** |
- | * \Target\Demo\ARMCM0_STM32F0_Discovery_STM32F051_IAR\**Boot**\bin\**openblt_stm32f051.srec** | + | * \Target\Demo\ARMCM0_XMC1_XMC1400_Boot_Kit_GCC\**Boot**\Debug\**openblt_xmc1400.srec** |
+ | Note that after closing the debug session in Eclipse, the on-board Segger J-Link interface halts the CPU. If you want to continue running the bootloader program, a reset of the microcontroller is needed. An easy method to achieve this is by disconnecting and then reconnecting the USB cable. | ||
===== Building the Demo Program ===== | ===== Building the Demo Program ===== | ||
- | When using IAR EWARM, simply open the workspace from within the Embedded Workbench. The workspace file (stm32f0.eww) is located at: \Target\Demo\ARMCM0_STM32F0_Discovery_STM32F051_IAR\**Prog**\ide\. Once opened, select //Project->Rebuild All// from the menu to compile all the demo program sources and link the together into the final executable. | + | Set the project as the active project in Eclipse. This is achieved by right-clicking the **Prog** project in the project navigator called //C/C++ Projects//. From the context menu, select //Set Active Project//. Next, select //Project → Rebuild Active Project// from the menu to compile all the user program sources and link them together into the final executable. |
The output file is | The output file is | ||
- | * \Target\Demo\ARMCM0_STM32F0_Discovery_STM32F051_IAR\**Prog**\bin\**demoprog_stm32f051.srec** | + | * \Target\Demo\ARMCM0_XMC1_XMC1400_Boot_Kit_GCC\**Prog**\Debug\**demoprog_xmc1400.srec** |
===== Firmware update procedure ===== | ===== Firmware update procedure ===== | ||
- | To download the demo program \Target\Demo\ARMCM0_STM32F0_Discovery_STM32F051_IAR\**Prog**\bin\**demoprog_stm32f051.srec** using the bootloader, follow the instructions in the following links, depending on the communication interface you intend to use: | + | To download the demo program \Target\Demo\ARMCM0_XMC1_XMC1400_Boot_Kit_GCC\**Prog**\Debug\**demoprog_xmc1400.srec** using the bootloader, follow the instructions in the following links, depending on the communication interface you intend to use: |
* [[manual:uart_demo|Firmware updates using the UART communication interface]] | * [[manual:uart_demo|Firmware updates using the UART communication interface]] | ||
+ | * [[manual:can_demo|Firmware updates using the CAN communication interface]] | ||