Access Official Technical PDF

Share Summary:LinkedInEmail

A V2X development platform has to bring together more than a radio link. Engineers building connected-driving applications need to handle secure vehicle-to-everything communications, positioning, vehicle data and application processing as parts of one system. Unex Technology and STMicroelectronics addressed that integration challenge by combining Unex’s SOM-301 V2X System-on-Module with ST’s Telemaco3P Modular Telematics Platform.

The collaboration was intended to give developers a more direct route to prototyping vehicle-to-vehicle (V2V) and vehicle-to-infrastructure (V2I) applications. Its value lies in the division of responsibilities between the V2X module and the telematics platform, alongside the ability to customize the combined solution at hardware and software levels.

How the V2X development platform is organized

The SOM-301 is a self-contained module that integrates hardware and software components required for V2X operation. It includes Unex’s V2Xcast technology and an Autotalks CRATON2/PLUTON2 chipset. The chipset supports both Dedicated Short-Range Communications (DSRC) and C-V2X PC5 connectivity, giving developers options for V2X communication within the module.

The module also integrates ST’s Teseo III automotive multi-constellation GNSS chip. Positioning is therefore part of the module’s hardware, while the broader Telemaco3P platform provides its own automotive-grade multi-constellation GNSS hardware and dead-reckoning sensors. The source describes both sets of positioning components; their presence reflects the capabilities of the integrated system rather than a claim that they are interchangeable.

At the platform’s core is ST’s Telemaco3P secure automotive processor. ST described it as the first device with an embedded isolated Hardware Security Module (HSM), intended to provide a secure foundation for automotive applications. The platform also offers interfaces to vehicle networks, including CAN-FD, FlexRay and BroadR-Reach (100Base-T1), with optional Bluetooth, Wi-Fi and LTE modules.

Separating communications from application processing

A key architectural feature is the split between secure V2X communication and higher-level application work. The CRATON2 on the SOM-301 handles secure V2X communications. The Telemaco3P processor manages applications and can combine V2X messages with data from in-vehicle systems, Wi-Fi or cellular networks.

This separation gives developers a way to work with V2X message processing alongside other sources of information used by a telematics application. For example, a prototype can be designed to take V2X messages into account while also using relevant vehicle-bus or network data. The source does not specify particular application algorithms or use cases, so the platform’s role is best understood as an environment for developing and testing those applications—not as a finished driving function.

Unex’s V2Xcast software stack extends the V2X processing capabilities available in the integrated setup. Together, the stack, communications chipset and application processor provide distinct building blocks for handling V2X connectivity and developing the software that uses its messages.

Why integration matters for prototyping

Integrating a production-ready V2X System-on-Module onto a modular telematics platform can reduce the amount of separate hardware and software integration required to begin application development. Rather than assembling every V2X component and platform interface independently, developers can work from a combined setup that already brings these elements together.

The arrangement is also designed to support customization at both hardware and software levels. That flexibility matters in prototyping because application requirements can differ: developers may need to adapt the platform configuration, software stack or way V2X data is combined with other vehicle and network inputs. The collaboration’s stated goal was to support near-final V2V and V2I application prototypes and help shorten time to market.

For engineering teams, the practical evaluation points include:

  • Communication requirements: Determine whether DSRC, C-V2X PC5 or both are relevant to the application being prototyped.
  • Data integration: Identify how V2X messages will be used with information from vehicle buses, positioning hardware, Wi-Fi or cellular networks.
  • Security architecture: Understand the respective roles of the secure V2X chipset and the Telemaco3P processor’s embedded isolated HSM.
  • Customization needs: Assess which hardware and software elements may need to be adapted for the intended prototype.

These considerations help teams translate a development platform’s component list into a workable system architecture. They also clarify where application-level design and integration work remain necessary.

A development path for connected-driving systems

The Unex–ST integration illustrates how a modular approach can bring communications, processing, positioning and vehicle connectivity into a shared prototyping environment. SOM-301 supplies the V2X-focused hardware and software, while Telemaco3P provides the application-processing platform, security features and connections to vehicle and wireless networks.

For system integrators and automotive engineering teams, the practical implication is a more consolidated starting point for V2V and V2I development—not a substitute for application design, validation or configuration work. By clarifying how secure V2X communication and broader telematics processing fit together, the combined platform was intended to help developers move from component integration toward application prototyping with fewer integration steps.

Access Official Technical PDF

About The Author