====== ARM-CM4 S32K14 NXP S32K144 EVB S32 Design Studio ======

===== Supported firmware update interfaces =====

^ RS232         ^ CAN            ^ USB         ^ TCP/IP      ^ SD-card      ^ Modbus RTU   ^
| Yes           | Yes            | No          | No          | No           | No           |

===== Development Environment =====

{{:manual:demos:nxp_s32k144_evb.png?|}}

This demo is targeted towards the [[https://www.nxp.com/design/development-boards/automotive-development-platforms/s32k-mcu-platforms/s32k144-evaluation-board:S32K144EVB|NXP S32K144 EVB]] board, with 512 kB internal Flash EEPROM and 64 kB internal RAM.

To program the bootloader into the internal flash on the S32K144 microcontroller, the on-board [[https://www.nxp.com/design/microcontrollers-developer-resources/ides-for-kinetis-mcus/opensda-serial-and-debug-adapter:OPENSDA|OpenSDA]] debugger 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 [[https://www.nxp.com/design/software/development-software/s32-design-studio-ide:S32-DESIGN-STUDIO-IDE|S32 Design Studio IDE]]. 

When performing updates via CAN, make sure to configure the board such that it is powered with a 12V power source (jumper J107), instead of via USB, otherwise the CAN transceiver on the board is not powered.


===== Workspace creation in S32 Design Studio =====
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\ARMCM4_S32K14_S32K144EVB_GCC\

{{:manual:demos:nxp_s32k144_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\ARMCM4_S32K14_S32K144EVB_GCC\. Eclipse will automatically find the **Boot** and **Prog** projects and select them:

{{:manual:demos:nxp_s32k144_s32ds_project_import.png?455|}}

Click the //Finish// button to complete the project import operation.

===== 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.

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.

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\ARMCM4_S32K14_S32K144EVB_GCC\**Boot**\Debug\**openblt_s32k144.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.
===== Building the Demo Program =====

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

  * \Target\Demo\ARMCM4_S32K14_S32K144EVB_GCC\**Prog**\Debug\**demoprog_s32k144.srec**


===== 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:

  * [[manual:rs232_demo|Firmware updates using the RS232 communication interface]]
  * [[manual:can_demo|Firmware updates using the CAN communication interface]]