User Tools

Site Tools


manual:demos:infineon_xmc4700_relax_kit_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
manual:demos:infineon_xmc4700_relax_kit_gcc [2016/10/24 08:34]
voorburg [Development Environment]
manual:demos:infineon_xmc4700_relax_kit_gcc [2023/12/04 22:40] (current)
voorburg [Supported firmware update interfaces]
Line 1: Line 1:
-====== ARM-CM4 XMC4 Infineon XMC4700 Relax Kit GCC ======+====== ARM-CM4 XMC4 Infineon XMC4700 Relax Kit GCC Dave 4 ======
  
 ===== Supported firmware update interfaces ===== ===== Supported firmware update interfaces =====
  
-UART           ^ CAN             ​^ USB          ^ TCP/​IP ​      ​^ SD-card ​     ^ +RS232         ^ CAN            ^ USB         ​^ TCP/​IP ​     ^ SD-card ​     ​^ Modbus RTU   
-| Yes            | Yes             ​No           No           | No           |+| Yes           | Yes            | Yes         ​Yes         Yes          ​| No           |
  
 ===== Development Environment ===== ===== Development Environment =====
Line 10: Line 10:
 {{:​manual:​demos:​infineon_xmc700_relax_kit.jpg?​100 |}} {{:​manual:​demos:​infineon_xmc700_relax_kit.jpg?​100 |}}
  
-This demo is targeted towards the [[http://​www.infineon.com/​cms/​en/​product/​evaluation-boards/​KIT_XMC47_RELAX_V1/productType.html?​productType=5546d46250cc1fdf0150f6bdcddb6ec7|Infineon XMC4700 Relax Kit]] board, with 2048 kB internal Flash EEPROM and 352 kB internal RAM.+This demo is targeted towards the [[https://​www.infineon.com/​cms/​en/​product/​evaluation-boards/​kit_xmc47_relax_v1/|Infineon XMC4700 Relax Kit]] board, with 2048 kB internal Flash EEPROM and 352 kB internal RAM.
  
-To program the bootloader into the internal flash on the XMC4700 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. When using the on-board Segger J-Link JTAG interface, make sure the [[https://​www.segger.com/​downloads/​jlink|J-Link software and documentation pack V6.00d]] or newer is installed on your PC.+To program the bootloader into the internal flash on the XMC4700 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.emblocks.org/|EmBitz]] ​development ​environment from Em::BlocksThe version that was used to create these demo programs was {{:​manual:​embitz_1_00.zip?linkonly|EmBitz ​version ​1.00}}.+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.
  
  
 +===== Workspace creation in Dave =====
 +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.
 +
 +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\ARMCM4_XMC4_XMC4700_Relax_Kit_GCC\ ​
 +
 +{{:​manual:​demos:​infineon_xmc4700_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\ARMCM4_XMC4_XMC4700_Relax_Kit_GCC\. Eclipse will automatically find the **Boot** and **Prog** projects and select them:
 +
 +{{:​manual:​demos:​infineon_xmc4700_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 STM32F207'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 XMC4700's internal flash memory. The steps in this section only need to be done once.
  
-When using EmBitz, simply open the project ​file by double-clicking the file: \Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_GCC\**Boot**\ide\**stm32f207.ebp** from the Windows ExplorerTo build the bootloader, select //Build -> Rebuild ​all target files// from the program ​menu. +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 STM32F207. Make sure the Segger J-Link debugger interface it connected ​to the JTAG connector on the Olimex STM32-P207 board and the other side to your PC via a USB cable. Next, select //Debug -> Start Debug Session (F8)// from EmBitz'​s program ​menu to flash the bootloader program. Once done, you can start the bootloader program by selecting //Debug -> Run (F5)// from the program'​s menu.+The bootloader program is now ready to be programmed into the internal flash memory of the XMC4700. Make sure the XMC4700 Relax 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\ARMCM3_STM32F2_Olimex_STM32P207_GCC\**Boot**\bin\**openblt_stm32f207.elf** +  * \Target\Demo\ARMCM4_XMC4_XMC4700_Relax_Kit_GCC\**Boot**\Debug\**openblt_xmc4700.elf** 
-  * \Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_GCC\**Boot**\bin\**openblt_stm32f207.srec**+  * \Target\Demo\ARMCM4_XMC4_XMC4700_Relax_Kit_GCC\**Boot**\Debug\**openblt_xmc4700.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 EmBitz, simply open the project ​file by double-clicking the file: \Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_GCC\**Prog**\ide\**stm32f207.ebp** from the Windows ExplorerTo build the demo program, select //Build -> Rebuild ​all target files// from the program'​s ​menu. +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\ARMCM3_STM32F2_Olimex_STM32P207_GCC\**Prog**\bin\**demoprog_stm32f207.srec**+  * \Target\Demo\ARMCM4_XMC4_XMC4700_Relax_Kit_GCC\**Prog**\Debug\**demoprog_xmc4700.srec**
  
  
 ===== Firmware update procedure ===== ===== Firmware update procedure =====
  
-To download the demo program \Target\Demo\ARMCM3_STM32F2_Olimex_STM32P207_GCC\**Prog**\bin\**demoprog_stm32f207.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\ARMCM4_XMC4_XMC4700_Relax_Kit_GCC\**Prog**\Debug\**demoprog_xmc4700.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:rs232_demo|Firmware updates using the RS232 communication interface]]
   * [[manual:​can_demo|Firmware updates using the CAN communication interface]]   * [[manual:​can_demo|Firmware updates using the CAN communication interface]]
 +  * [[manual:​usb_demo|Firmware updates using the USB communication interface]]
 +  * [[manual:​net_demo|Firmware updates using the TCP/IP communication interface]] ​
   * [[manual:​sdcard_demo|Firmware updates from SD-card]]   * [[manual:​sdcard_demo|Firmware updates from SD-card]]
- 
  
manual/demos/infineon_xmc4700_relax_kit_gcc.1477290873.txt.gz · Last modified: 2019/09/24 22:13 (external edit)