User Tools

Site Tools


manual:demos:s32k118_evb_s32ds

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
Next revision Both sides next revision
manual:demos:s32k118_evb_s32ds [2020/03/25 12:03]
voorburg [Workspace creation in S32 Design Studio]
manual:demos:s32k118_evb_s32ds [2020/03/25 12:12]
voorburg [Firmware update procedure]
Line 34: Line 34:
 ===== 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 S32K144'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 S32K118's internal flash memory. The steps in this section only need to be done once.
  
-Right-click the **Boot** project in the //Project Explorer// and select //Build Project// from the popup menu. This compiles all the bootloader sources and links them together into the final executable.+Right-click the **Boot** project in the //Project Explorer// and select //Refresh// from the popup menu. Next, right-click the **Boot** project again and this time select //Build Project// from the popup menu. This compiles all the bootloader sources and links them together into the final executable.
  
-The bootloader program is now ready to be programmed into the internal flash memory of the S32K144 ​microcontroller. Make sure the S32K144 ​EVB board is powered up and 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 S32K118 ​microcontroller. Make sure the S32K118 ​EVB board is powered up and 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.
  
 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\ARMCM4_S32K14_S32K144EVB_GCC\**Boot**\Debug\**openblt_s32k144.elf** +  * \Target\Demo\ARMCM0_S32K14_S32K118EVB_GCC\**Boot**\Debug\**openblt_s32k118.elf** 
-  * \Target\Demo\ARMCM4_S32K14_S32K144EVB_GCC\**Boot**\Debug\**openblt_s32k144.srec**+  * \Target\Demo\ARMCM0_S32K14_S32K118EVB_GCC\**Boot**\Debug\**openblt_s32k118.srec**
  
- +Note that after closing the debug session in Eclipse, the on-board OpenSDA interface halts the CPU. If you want to continue running the bootloader program, a reset of the microcontroller is needed. This is achieved disconnecting and then reconnecting ​the power to the board.
-Note that after closing the debug session in Eclipse, the on-board OpenSDA interface halts the CPU. If you want to continue running the bootloader program, a reset of the microcontroller is needed. This is achieve by briefly pressing ​the reset button on the board.+
 ===== Building the Demo Program ===== ===== Building the Demo Program =====
  
-Right-click the **Prog** project in the //Project Explorer// and select //Build Project// from the popup menu. This compiles all the user program sources and links them together into the final executable.+Right-click the **Prog** project in the //Project Explorer// and select //Refresh// from the popup menu. Next, right-click the **Prog** project again and this time select Build Project ​from the popup menu. This compiles all the user program sources and links them together into the final executable. ​
  
 The output file is The output file is
  
-  * \Target\Demo\ARMCM4_S32K14_S32K144EVB_GCC\**Prog**\Debug\**demoprog_s32k144.srec**+  * \Target\Demo\ARMCM0_S32K14_S32K118EVB_GCC\**Prog**\Debug\**demoprog_s32k118.srec**
  
  
 ===== Firmware update procedure ===== ===== Firmware update procedure =====
  
-To download the demo program \Target\Demo\ARMCM4_S32K14_S32K144EVB_GCC\**Prog**\Debug\**demoprog_s32k144.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_S32K14_S32K118EVB_GCC\**Prog**\Debug\**demoprog_s32k118.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:​can_demo|Firmware updates using the CAN communication interface]]   * [[manual:​can_demo|Firmware updates using the CAN communication interface]]
  
manual/demos/s32k118_evb_s32ds.txt · Last modified: 2023/12/04 22:38 by voorburg