Table of Contents
Introduction
This article is part of the Zone Node series and describes the software and hardware environment used throughout the project. The purpose of this article is to describe the software and hardware setup required to follow the series and reproduce the results.
Before examining communication routing, control logic, or integration challenges, it is important to understand the tools and platforms that support the development and execution of the zonal node application. This article introduces the software components used to develop, configure, and deploy the application, as well as the hardware platforms used to demonstrate the zonal controller functionality. This information provides the foundation required for the remaining articles in the series.
Overview of the development flow
The zonal node application presented in this series is developed using a combination of Model-Based Design tools, NXP software components, and automotive-grade hardware platforms. At a high level:
- Application modeling starts in MATLAB® and Simulink®, where communication routing and control logic are implemented graphically.
- Code generation converts the model into production-ready embedded software using the code-generation tools provided by MathWorks and NXP.
- Deployment compiles the generated software and loads it onto the target hardware, where it is used to demonstrate communication between multiple vehicle networks.
This environment was selected to support rapid development, easier validation, and improved traceability between model design and generated software. By using a Model-Based Design approach, algorithm development, communication integration, and application verification can be performed within a common framework. The software and hardware presented here are used consistently throughout the series and will be referenced when discussing communication routing, system behavior, and integration scenarios.
Figure 1. Development flow diagram
The workflow begins with application development in Simulink. Communication routing logic, control functions, and software configuration are implemented within the model. The NXP Model-Based Design Toolbox (MBDT) provides hardware-specific blocks that enable integration with S32K3 peripherals and communication interfaces. Following code generation, the application is compiled and deployed to the target hardware, where communication routing functionality can be validated.
This article is intended for:
- Engineers interested in reproducing the zonal node demonstration
- Simulink users developing automotive communication applications
- Developers evaluating Model-Based Design workflows
- Engineers working with NXP automotive microcontrollers and evaluation boards
By understanding the software and hardware environment early in the series, readers will be better prepared to follow the implementation details presented in subsequent articles.
Required Software
The following software components are used throughout the project:
- MATLAB® and Simulink® – model development and simulation
- Embedded Coder® (required MATLAB toolbox) – automatic code generation from the model
- Simulink models – the zonal node routing application model referenced throughout the series
- NXP Model-Based Design Toolbox (MBDT) – S32K3 support and peripheral configuration
- NXP additional tools – FreeMASTER and S32 Design Studio for build, deployment, and debugging
- CAN analysis software – monitoring and validating CAN communication
- LIN analysis software – monitoring and validating LIN communication
3.1 MATLAB® and Simulink®
MATLAB® and Simulink® form the foundation of the development environment. They are used to create the zonal node application, implement communication routing logic, configure software behavior, and perform model-based verification activities. The application described throughout this series is developed as a Simulink model and later translated into embedded software using automatic code-generation tools (Embedded Coder®).
3.2 NXP Model-Based Design Toolbox (MBDT)
The NXP Model-Based Design Toolbox (MBDT) extends Simulink with hardware-specific support for NXP automotive microcontrollers. For this project, MBDT for S32K3 version 1.8.0 is used.
The toolbox provides blocks and configuration interfaces for communication peripherals, timers, digital I/O resources, and other hardware modules available on the target device. It also integrates with the code-generation workflow, allowing Simulink models to be converted into software that can run directly on the S32K3 microcontroller.
3.3 CAN Analysis Software
CAN analysis tools are used during development and validation to observe CAN and CAN FD traffic exchanged between the zonal node and other network participants.
Typical use cases include:
- Monitoring transmitted and received CAN frames
- Verifying CAN-to-CAN routing behavior
- Measuring message timing and bus utilization
- Troubleshooting communication issues
Examples of commonly used software include PCAN-View, CANalyzer, and CANoe.
3.4 LIN Analysis Software
LIN analysis tools are used to monitor communication between the zonal node and LIN-connected edge devices.
Typical use cases include:
- Verifying LIN schedule execution
- Monitoring frame transmission and reception
- Validating signal timing and integrity
- Testing LIN-to-CAN routing scenarios
Examples of commonly used software include PLIN-View and LINalyzer.
Required Hardware
The following hardware components are used throughout the project:
- S32K344 automotive microcontroller – used to execute the zonal node application
- S32K344-WB Evaluation Board – used as the development and validation platform
- CAN analysis hardware – used to monitor and verify CAN/CAN FD communication
- LIN analysis hardware – used to monitor and verify LIN communication
4.1 S32K3 Microcontroller
The S32K3 family provides:
- Arm® Cortex®-M7 processing cores
- CAN FD communication interfaces
- LIN communication support
- Safety-oriented automotive features
- Low-power operating modes
- Rich peripheral connectivity
These capabilities make the device suitable for implementing communication aggregation and routing functions within the scope of this project.
4.2 Evaluation Hardware
The zonal node application runs on the S32K344-WB Evaluation Board, a development platform based on the NXP S32K344 microcontroller.
The board provides access to the communication interfaces and processing capabilities of the target device while offering an integrated platform for software development, debugging, and validation activities.
Within the scope of this project, the board is used to execute the routing application and exchange messages with nodes connected through CAN and LIN networks. Its communication interfaces, debugging connectivity, and expansion capabilities make it suitable for evaluating zonal communication architectures and routing scenarios.
Figure 2. S32K344-WB evaluation board
4.3 Communication Networks
The examples presented throughout this series use CAN and LIN networks to demonstrate message forwarding, routing, and protocol translation scenarios. These networks provide the communication backbone between the zonal node, central controller, and edge nodes, and are referenced throughout the upcoming routing and integration articles.
4.4 Network Analysis Hardware
Additional hardware tools are used during development and validation to observe network traffic and verify communication behavior.
- CAN analysis interfaces can be connected to the network to monitor transmitted and received CAN/CAN FD frames, validate routing functionality, and troubleshoot communication issues.
- LIN analysis interfaces can be used to monitor LIN schedules, frame exchanges, and LIN-to-CAN routing scenarios.
These tools provide visibility into network activity and support verification of the communication flows presented in later articles of this series.
References
Conclusion
This article introduced the software and hardware environment used throughout the zonal node project. It presented the development tools, code-generation workflow, and target hardware that support the implementation of the communication routing application.
The next article will build on this foundation by examining the internal logic control mechanisms used within the zonal node and how they contribute to communication handling across multiple networks.