This demo is targeted towards the 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 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 Keil MDK development environment.

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 Keil MDK, simply open the project from within uVision. The project file (xmc4700.uvprojx) is located at: \Target\Demo\ARMCM4_XMC4_XMC4700_Relax_Kit_Keil\Boot\ide\. Once opened, select Project→Rebuild all target files from the menu to compile all the bootloader sources and link the together into the final executable.

The bootloader program is now ready to be programmed into the internal flash memory of the XMC4700. Using your favorite programmer, flash the bootloader using one of the following files, depending on what file type your programmer supports:

• \Target\Demo\ARMCM4_XMC4_XMC4700_Relax_Kit_Keil\Boot\bin\openblt_xmc4700.axf
• \Target\Demo\ARMCM4_XMC4_XMC4700_Relax_Kit_Keil\Boot\bin\openblt_xmc4700.srec

When using Keil MDK, simply open the project from within uVision. The project file (xmc4700.uvprojx) is located at: \Target\Demo\ARMCM4_XMC4_XMC4700_Relax_Kit_Keil\Prog\ide\. Once opened, select Project→Rebuild all target files from the menu to compile all the demo program sources and link the together into the final executable.

The output file is

• \Target\Demo\ARMCM4_XMC4_XMC4700_Relax_Kit_Keil\Prog\bin\demoprog_xmc4700.srec

To download the demo program \Target\Demo\ARMCM4_XMC4_XMC4700_Relax_Kit_Keil\Prog\bin\demoprog_xmc4700.srec using the bootloader, follow the instructions in the following links, depending on the communication interface you intend to use:

• Firmware updates using the RS232 communication interface
• Firmware updates using the CAN communication interface
• Firmware updates using the USB communication interface
• Firmware updates using the TCP/IP communication interface
• Firmware updates from SD-card