Getting Started with the S32K3X8EVB-Q289 Evaluation Board for General Purpose | NXP Semiconductors

Automotive

Industrial

Consumer

Technologies

Getting Started with the S32K3X8EVB-Q289 Evaluation Board for General Purpose

Last Modified: Mar 25, 2024Supports S32K3X8EVB-Q289 Evaluation Board for Automotive General Purpose

Contents of this document

  • 1

    Out of the Box

  • 2

    Get Software

  • 3

    Plug It In

  • 4

    Build and Debug

Purchase your S32K3X8EVB-Q289 Evaluation Board for Automotive General Purpose

Contents of this document

1. Out of the Box

1.1 Get to Know the S32K3X8EVB-Q289 Evaluation Board

Get to Know the S32K3X8EVB-Q289 Evaluation Board

Get to Know the S32K3X8EVB-Q289 Evaluation Board

Figure 1.S32K3X8EVB-Q289 Evaluation Board

1.2 Block Diagram Features

Figure 2.S32K3X8EVB-Q289 Block Diagram

NextGet Software

2. Get Software

2.1 Get the Integrated Development Environment (IDE)

Download and install S32 Design Studio IDE for S32 Platform. Click S32 Design Studio for S32 Platform v.3.5.

Then click S32 Design Studio v3.5 Windows installer.

S32 Design Studio for S32 Platform v.3.5

S32 Design Studio for S32 Platform v.3.5

Note: You will receive an activation code via email or under the license Keys tab.

2.2 Install the S32K3xx Development Package and RTD

Go to Help → S32DS Extensions and Updates from the top menu to open the S32DS Extensions and Updates dialogue. Install S32K3xx Development Package.

Note: In case of installation issues, please ensure that the latest version of S32 Design Studio Platform package and S32 Design Studio Platform Tools package is installed.

Continue with the installation of Real-Time Drivers for S32K3xx.

2.3 For AUTOSAR® Users - Download and Install Elektrobit Tresos Studio and Real-Time Drivers

Download and install Automotive SW - Elektrobit tresos Studio / AUTOSAR Configuration Tool from the S32K3 Standard Software package.

Select the version that you prefer and start the installation.

Download and install also the Automotive SW - S32K3/S32M27x - Real-Time Drivers for Cortex-M from the S32K3 Standard Software package.

Then search for the file S32K3 Real-Time Drivers AUTOSAR R21-11 Version 3.0.0 P10.

Finally, start the installation.

Note: You will receive an activation code via email. The Instalator will ask for the EB Tresos installation directory on your disk - that saves time in configuration. If you installed RTD prior to EB tresos, create a SW32K3_RTD_4.4_x.y.z.link file in: C:\EB\tresos\links folder with the content: "path=C:/NXP/SW32K3_RTD_4.4_x.y.z", where x,y,z refers to the installed RTD version.

Optionally select additional software tools from the S32K3 Standard Software tools list.

2.4 Get FreeMASTER Run-Time Debug Tool

S32K3X8EVB-Q289 performs better when using the FreeMASTER Run-Time Debugging Tool.

Note: Check the FreeMASTER page for the latest version.

The FreeMASTER communication driver for S32K3 microcontrollers is also needed; download updatesite file with the FreeMASTER communication driver from the Automotive SW - S32K3 - S32 FreeMASTER link in the S32K3 Standard Software package.

Open the S32DS Extensions and Updates dialog (menu → Help → S32DS Extensions and Updates), click Add Update Sites link and navigate to the FreeMASTER communication driver for S32K3 (zip file starting with "com.") on your disk.

Install FreeMASTER Communication driver for S32K3.

Note: Similarly, you may use these steps for manual download and installation of other software from the S32K3 Standard Software package or S32K3 Reference Software package.

PreviousOut of the Box
NextPlug It In

3. Plug It In

3.1 Set Up Jumpers in the S32K3X8EVB-Q289 Evaluation Board

Default Jumper settings
Interface Jumper State Notes
FS26/SBC Power Supply J13 1-2 FS26_VLDO1 [+5.0 V] is routed to P5V0 domain
J16 CLOSED FS26_VLDO2 [+3.3 V] is routed to P3V3 domain
J393 OPEN RESET_MCU signal disconnected from FS26_RSTB pin
J400 OPEN FS26_FS0B and FS26_FS1B signals
J401 OPEN FS26_GPIO1 and GND signals
J685 1-2 Select the debug mode of the FS26
J688 CLOSED Power LED Indicators enabled
J690 CLOSED Input from VBAT connectors
J701 1-2 FS26_VTRK2 [+3.3 V] is routed to P3V3_PERH domain
J756 CLOSED RESET_MCU signal routed to FS26_WAKE2_IN pin
J762 CLOSED PGOOD signal from MCU routed to FS26_GPIO2 pin
S32K358 MCU J23 1-2 P5V0 (+5.0V from the FS26) is selected for the VDD_HV_A_MCU reference
J25 CLOSED VDD_HV_A is routed to VDD_HV_A_MCU reference. Remove R58 to enable J25 functionality
J30 CLOSED P3V3 (+3.3V from the FS26) is selected for the VDD_HV_B_MCU reference
J31 CLOSED VDD_HV_B is routed to VDD_HV_B_MCU reference. Remove R75 to enable J31 functionality
J37 2-3 VDD_HV_B_MCU is routed to the collector pin of the V15 ballast transistor
J374 CLOSED VDD_HV_A is routed to VDD_HV_A_PERH
J375 CLOSED VDD_HV_B is routed to VDD_HV_B_PERH
J691 1-2 V15_NPN [+1.5V] is routed to V15_MCU domain
J746 2-3 VDD_HV_B_MCU is routed to the source pin of the V15 DC/DC converter
USB to UART/I2C Interface J57 1-2 USB is in self-powered configuration
Ethernet Interface J62 CLOSED P3V3 domain is routed to P3V3_ENET
User Peripherals J321 1-2 VDD_HV_A_PERH is routed to VDD_IO
J670 1-2 PTE0 is routed to the ARDUINO shield connector
J671 1-2 PTE1 is routed to the ARDUINO shield connector
LIN Interface J390 CLOSED LIN1 physical layer is enabled
J674 2-3 LIN1 commander mode* selected
J678 CLOSED LIN2 physical layer is enabled
J679 2-3 LIN2 commander mode* selected
CAN Interface J413 CLOSED CAN1 physical layer is enabled
J672 CLOSED CAN2 physical layer is enabled
Audio Interface J376 CLOSED Audio interface is enabled

Note: *Master in the LIN standard document.

3.2 Plug In the Power Supply

Switch SW10 to the OFF position (fully to the right).

Connect the 12 V power supply adapter and switch SW10 to the ON position (fully to the left).

When power is applied to the EVB, four orange LED's adjacent to the voltage regulators show the presence of the supply voltages (12 V, 5 V, 3.3 V and 1.5 V).

Note: This power-up procedure manages that FS23 SBC starts with a disabled watchdog.

3.3 Debugger Connection

Connect a micro-USB cable to the J55 connector to debug via the on-board S32K3 debugger.

or use one of available JTAG connectors for debug via external S32K3 debugger.

PreviousGet Software
NextBuild and Debug

4. Build and Debug

4.1 Create S32DS Project from Example

Go to menu → File → New → S32DS Project from Example. Select one of RTD example codes. For example Siul2_Port_Ip_Example_S32K358.

4.2 Generate Configuration

  1. Double-click on project mex file
  2. Set PTG30 pin (connected to Green LED) as GPIO Output
  3. Define PTG30 Identifier (without spaces). For example "GREEN_LED".
  4. Please unsure that you configure appropriate project and click on Update Code button for generating configuration files.

4.3 Edit Code

Return back to the C/C++ perspective.

Edit main.c file in src folder and modify all instances (4x) of "LED_PORT" and "LED_PIN" to "GREEN_LED_PORT" and "GREEN_LED_PIN".

4.4 Upload software and Debug

Use Debug Configuration menu and select one of predefined debug configurations for building and uploading software into MCU.

Note: If you do not use default on-board debugger, edit Debugger tab for your setup.

The S32DS will switch into Debug perspective where you may let code run.

The green LED will now blinking for approximately 10s.

PreviousPlug It In
NextDesign Resources

Design Resources

Board Information

Chip Documents

Software

Training

PreviousBuild and Debug
NextSupport

Support

Forums

Connect with other engineers and get expert advice on designing with the S32K3X8EVB-Q289 evaluation board using our community sites.

PreviousDesign Resources