Getting Started with MR-CANHUBK344 Evaluation Board

The file "Project.zip" is downloadable from the examples section of the S32K344 evaluation board page. The project file is compatible with S32 Design Studio version 3.4.

Note: The S32DS version 3.4 is located under Previous tab.

The following extensions are required to build the project:

• FreeRTOS for S32K3 2.0.0
• S32K3 RTD AUTOSAR 4.4 Version 2.0.0
• S32K3xx development package Version 3.4.3

S32 Design Studio extension manager looks like the following screen.

Click on Add Update Sites link to add manually downloaded update site files:

2.1 Application

Once “MR_CANHUBK3_IEEE1722” has been successfully flashed on the MR-CANHUBK3 board, it will act as an ETH ↔ CAN IEEE 1722 protocol converter.

CAN messages received from CAN0 through CAN5 will be converted to an IEEE 1722 ACF-CAN fame and will be broadcasted to the Ethernet. To view incoming CAN frames you can install Wireshark on a Windows / Linux machine.

MR-CANHUBK344 board includes several interfaces. Necessary cables for all interfaces are provided with the kit. However, they may need to be cut or modified for your specific needs. This quick start guide assumes a familiarity with this type of hardware and the ability of making CAN, T1 Ethernet and power connections.

The demo also requires external components or test equipment that are able to make CAN/CAN FD interface connections and 100BASE-T1 Automotive Ethernet connections.

3.1 Power Input

Using a bench power supply or appropriate battery source, connect power 5 - 40 V (12 V nominal) @100 mA minimum to connector P27 at the top left corner of the board (Pin 1-2 power, Pin 3 NC, Pin 4-5 ground) or use the next P28 connector (Pin 1 power, Pin 2 ground).

Figure 1. Connector locations MR-CANHUBK3 for the software demo

3.2 CAN Bus Connections

A CAN bus typically requires termination at both ends. Use one of the included CAN-TERM termination boards when needed. Alternative CAN termination may be possible when using the ports that have the CAN SIC Phys.

3.3 100Base-T1 Ethernet Connection

The T1 connector (P9) is a 2 pin JST-GH connector for 2-wire 100Mbps Ethernet. The signals are capacitively coupled and are polarized P and N. The TJA1003 T1 interface chip will auto-negotiate the polarity if it is reversed. You may adapt this cable to other connector types as needed, by cutting the cable and soldering to the wires.

This JST-GH cable will connect directly to other mobile robotics boards such as the UCANS32K1SIC, the UCANS32K1SCT, the RDDRONE-T1ETH8 and NavQPlus. RDDRONE-T1ADAPT may be used to translate to an RJ45 connection type.

The yellow LED (D88) at the backside of the PCB indicates the link status. When flashing, it indicates there is a link.

3.4 Board Power Up Sequence – Circumventing the PMIC WDT

The FS26 is the safety system basis chip (SBC) with low-power fit for ASIL D from NXP and includes a safety watchdog timer (WDT).

In sample code, the challenge watchdog functionality has not been implemented. Instead, during startup of the S32K344 the sample application sends a request to the FS26 to disable the watchdog functionality.

To circumvent the FS26 WDT, the chip must be put into debug mode. This is done by removing JP1 and then supplying 12.0V on power input P27 or P28 and then re-inserting the JP1 jumper.

Once this is done, the reset LED D24 should no longer blink, indicating the S32K344 will not reset continuously by the FS26.

3.5 Board Status LEDs

Figure 6. Led overview

4.1 Import the Project

To import the included Project.zip, open File → Import → General → Project from Folder or Archive and then select the Project.zip archive.

4.2 S32 Pin Tool

Once the project has been imported, right click on “MR_CANHUBK3_IEEE1722” in the projects explorer and select S32 Configuration Tools → Open Pins.

The S32 Pin tool perspective view will appear and in the menu click the button “Update Code” and select “OK”. The driver configuration files will be generated.

4.3 Build Project

Go back to the Project Explorer right click on “MR_CANHUBK3_IEEE1722” and select “Build Project”. Now you can flash the “MR_CANHUBK3_IEEE1722.elf” using your programmer.

For more information regarding S32 Design Studio, S32 Configuration Tools and debugging please refer to the to the “Getting Started with S32K3 and S32DS” guide.

4.4 Simulate CAN Messages

You can also simulate CAN messages by pressing SW1 or SW2.

Connect CAN0 (P12) back to CAN1 (P14) to create a bus using included cable. Also connect the CAN-Term board to P13 to terminate the bus.

When pressing either SW1 or SW2, both LEDs D7 and D22 turn on briefly indicating the presence of a CAN packet.

SW1 will send a CAN message to CAN0 and SW2 will send a CAN message to CAN1.

4.5 WireShark

We strongly recommend you to install WireShark to monitor CAN and Ethernet traffic. Figure 5 shows WireShark screen when a CAN packet has been sent using IEEE 1722.

Note: The 100BaseTx to 100BASE-T1 media converter tool (not included with the board) is necessary for debugging Ethernet frames. You may use for example NXP RDDRONE-T1ADAPT

Wireshark output of an IEEE 1722 ACF-CAN Frame

Board Information

• S32K3 MCUs for General Purpose – Hardware Design Package
• MR-CANHUBK344 Hardware User Manual
• MR-CANHUBK344 Software User Manual

Chip Documents

• S32K3 MCUs for General Purpose – Hardware Design Package
• MR-CANHUBK344 Hardware Design Package
• MR-CANHUBK344 IEEE 1722 Protocol Stacks
• https://nxp.gitbook.io/mr-canhubk3

Software

• Automotive Software Package Manager
• Real-Time Drivers (RTD)
• FreeMASTER Run-Time Debugging Tool
• S32 Design Studio for S32 Platform
• Model-Based Design Toolbox (MBDT)
• S32K3 Standard Software
• S32K3 Reference Software

Training

• Introduction to MR-CANHUBK344

Forums

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

• S32K
• S32 Design Studio
• S32 Design Studio for S32 Platform
• FreeMASTER