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
manual:demos:s32k118_evb_s32ds [2020/03/25 12:12]
voorburg [Firmware update procedure]
manual:demos:s32k118_evb_s32ds [2023/12/04 22:38] (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 22: Line 22:
 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. 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 S32 Design Studio. After starting S32 Design Studio, you are prompted to open a workspace. It is easiest to create a new one in the following directory: .\Target\Demo\ARMCM0_S32K14_S32K118EVB_GCC\+The first step in getting the the bootloader up-and-running,​ is the creation of the Eclipse workspace in S32 Design Studio. After starting S32 Design Studio, you are prompted to open a workspace. It is easiest to create a new one in the following directory: .\Target\Demo\ARMCM0_S32K11_S32K118EVB_GCC\
  
 {{:​manual:​demos:​nxp_s32k118_s32ds_workspace_creation.png?​550|}} {{:​manual:​demos:​nxp_s32k118_s32ds_workspace_creation.png?​550|}}
  
-To import the demo programs into the workspace, select //File -> Import// from the program menu. Then select //General -> Existing Projects into Workspace//​. On the next screen you select the following directory as the root directory: .\Target\Demo\ARMCM0_S32K14_S32K118EVB_GCC\. Eclipse will automatically find the **Boot** and **Prog** projects and select them:+To import the demo programs into the workspace, select //File -> Import// from the program menu. Then select //General -> Existing Projects into Workspace//​. On the next screen you select the following directory as the root directory: .\Target\Demo\ARMCM0_S32K11_S32K118EVB_GCC\. Eclipse will automatically find the **Boot** and **Prog** projects and select them:
  
 {{:​manual:​demos:​nxp_s32k118_s32ds_project_import.png?​455|}} {{:​manual:​demos:​nxp_s32k118_s32ds_project_import.png?​455|}}
Line 42: Line 42:
 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\ARMCM0_S32K14_S32K118EVB_GCC\**Boot**\Debug\**openblt_s32k118.elf** +  * \Target\Demo\ARMCM0_S32K11_S32K118EVB_GCC\**Boot**\Debug\**openblt_s32k118.elf** 
-  * \Target\Demo\ARMCM0_S32K14_S32K118EVB_GCC\**Boot**\Debug\**openblt_s32k118.srec**+  * \Target\Demo\ARMCM0_S32K11_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 achieved disconnecting and then reconnecting the power to the board.
Line 52: Line 52:
 The output file is The output file is
  
-  * \Target\Demo\ARMCM0_S32K14_S32K118EVB_GCC\**Prog**\Debug\**demoprog_s32k118.srec**+  * \Target\Demo\ARMCM0_S32K11_S32K118EVB_GCC\**Prog**\Debug\**demoprog_s32k118.srec**
  
  
 ===== Firmware update procedure ===== ===== Firmware update procedure =====
  
-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:+To download the demo program \Target\Demo\ARMCM0_S32K11_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.1585134759.txt.gz · Last modified: 2020/03/25 12:12 by voorburg