Differences

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

--- manual:demos:infineon_xmc1400_boot_kit_gcc [2017/04/24 14:49]
voorburg created
+++ manual:demos:infineon_xmc1400_boot_kit_gcc [2023/12/04 22:39] (current)
voorburg [Supported firmware update interfaces]
@@ Line 3: / Line 3: @@
 ===== 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            | No          | No          | No           | No           |
 ===== Development Environment =====
@@ Line 10: / Line 10: @@
 {{:manual:demos:infineon_xmc1400_boot_kit.jpg?200 |}}
-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.
+This demo is targeted towards the [[https://www.infineon.com/cms/en/product/evaluation-boards/kit_xmc14_boot_001/|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 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.
@@ Line 34: / Line 34: @@
 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 (xmc1400.eww) is located at: \Target\Demo\ARMCM0_XMC1_XMC1400_Boot_Kit_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 XMC1400. Make sure the XMC1400 Boot Kit 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:
-  * \Target\Demo\ARMCM0_XMC1_XMC1400_Boot_Kit_IAR\**Boot**\bin\**openblt_xmc1400.out**
+  * \Target\Demo\ARMCM0_XMC1_XMC1400_Boot_Kit_GCC\**Boot**\Debug\**openblt_xmc1400.elf**
-  * \Target\Demo\ARMCM0_XMC1_XMC1400_Boot_Kit_IAR\**Boot**\bin\**openblt_xmc1400.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 =====
-When using IAR EWARM, simply open the workspace from within the Embedded Workbench. The workspace file (xmc1400.eww) is located at: \Target\Demo\ARMCM0_XMC1_XMC1400_Boot_Kit_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
-  * \Target\Demo\ARMCM0_XMC1_XMC1400_Boot_Kit_IAR\**Prog**\bin\**demoprog_xmc1400.srec**
+  * \Target\Demo\ARMCM0_XMC1_XMC1400_Boot_Kit_GCC\**Prog**\Debug\**demoprog_xmc1400.srec**
 ===== Firmware update procedure =====
-To download the demo program \Target\Demo\ARMCM0_XMC1_XMC1400_Boot_Kit_IAR\**Prog**\bin\**demoprog_xmc1400.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:rs232_demo|Firmware updates using the RS232 communication interface]]
   * [[manual:can_demo|Firmware updates using the CAN communication interface]]

OpenBLT Bootloader

User Tools

Site Tools

Differences

Page Tools