manual:demos:tc375_lite_kit_ads
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
manual:demos:tc375_lite_kit_ads [2022/11/07 18:22] voorburg [Workspace creation in AURIX Development Studio] |
manual:demos:tc375_lite_kit_ads [2023/12/04 22:41] (current) voorburg [Supported firmware update interfaces] |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== Supported firmware update interfaces ===== | ===== Supported firmware update interfaces ===== | ||
| - | ^ RS232 ^ 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 ===== | ===== Development Environment ===== | ||
| Line 13: | Line 13: | ||
| - | To compile the demo programs you can use the [[https://www.infineon.com/cms/en/product/promopages/aurix-development-studio/|AURIX Development Studio]] | + | To compile the demo programs you can use the [[https://www.infineon.com/cms/en/product/promopages/aurix-development-studio/|AURIX Development Studio]]. |
| To program the bootloader into the internal flash, the on-board miniWiggler interface was used. Firmware updates via the serial communication port are preconfigured to use the virtual COM-port offered by the miniWiggler. This means that no additional hardware is needed, besides a standard micro-USB cable. | To program the bootloader into the internal flash, the on-board miniWiggler interface was used. Firmware updates via the serial communication port are preconfigured to use the virtual COM-port offered by the miniWiggler. This means that no additional hardware is needed, besides a standard micro-USB cable. | ||
| Line 33: | Line 33: | ||
| ===== 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 STM32F767ZI'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 AURIX TriCore TC375's internal flash memory. The steps in this section only need to be done once. |
| - | - Set the project as the active project in Eclipse. This is achieved by clicking the **Boot** project in the //Project Explorer// to select it. | + | 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. |
| - | - Next, right-click the **Boot** project in the //Project Explorer// and select //Refresh// from the popup menu. | + | |
| - | - Finally, right-click the **Boot** project in the //Project Explorer// and select //Build Project// from the popup 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 STM32F767ZI microcontroller. Make sure the Nucleo-F767ZI board is connected to your PC via a USB cable. Next, select //Run -> Debug// from the menu to flash the bootloader program. This will launch the Debug perspective in Eclipse. Once done, you can start the bootloader program by selecting //Run -> Resume// from the menu. | + | The bootloader program is now ready to be programmed into the internal flash memory of the AURIX TriCore TC375. Make sure the AURIX TriCore TC375 Lite Kit is connected to your PC via a USB cable. Next, right-click the **Boot** project in the project navigator and select //Debug As -> AURIX 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\ARMCM7_STM32F7_Nucleo_F767ZI_CubeIDE\**Boot**\Debug\**openblt_stm32f767.elf** | + | * \Target\Demo\TRICORE_TC3_TC375_Lite_Kit_ADS\**Boot**\Debug\**openblt_tc375.elf** |
| - | * \Target\Demo\ARMCM7_STM32F7_Nucleo_F767ZI_CubeIDE\**Boot**\Debug\**openblt_stm32f767.srec** | + | * \Target\Demo\TRICORE_TC3_TC375_Lite_Kit_ADS\**Boot**\Debug\**openblt_tc375.srec** |
| ===== Building the Demo Program ===== | ===== Building the Demo Program ===== | ||
| - | - Set the project as the active project in Eclipse. This is achieved by clicking the **Prog** project in the //Project Explorer// to select it. | + | 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. |
| - | - Next, right-click the **Prog** project in the //Project Explorer// and select //Refresh// from the popup menu. | + | |
| - | - Finally, right-click the **Prog** project in the //Project Explorer// and select //Build Project// from the popup 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\ARMCM7_STM32F7_Nucleo_F767ZI_CubeIDE\**Prog**\Debug\**demoprog_stm32f767.srec** | + | * \Target\Demo\TRICORE_TC3_TC375_Lite_Kit_ADS\**Prog**\Debug\**demoprog_tc375.srec** |
| ===== Firmware update procedure ===== | ===== Firmware update procedure ===== | ||
| - | To download the demo program \Target\Demo\ARMCM7_STM32F7_Nucleo_F767ZI_CubeIDE\**Prog**\Debug\**demoprog_stm32f767.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\TRICORE_TC3_TC375_Lite_Kit_ADS\**Prog**\Debug\**demoprog_tc375.srec** using the bootloader, follow the instructions in the following links, depending on the communication interface you intend to use: |
| * [[manual:rs232_demo|Firmware updates using the RS232 communication interface]] | * [[manual:rs232_demo|Firmware updates using the RS232 communication interface]] | ||
| - | * [[manual:net_demo|Firmware updates using the TCP/IP communication interface]] | + | * [[manual:can_demo|Firmware updates using the CAN communication interface]] |
manual/demos/tc375_lite_kit_ads.1667841763.txt.gz · Last modified: 2022/11/07 18:22 by voorburg
Page Tools
