Clarification on SMARC imx95 support

Technical Support
, ,
1

Hi.

I have recently seen the announcement of Toradex BSP Layers and Reference Images for Yocto Project 7.4.0 Quarterly Release and noted the reference to

Upgrade support for i.MX95-based products:

  • Added support for i.MX95 B0 Silicon

  • Added support for Verdin i.MX95

  • Dropped support for SMARC iMX95 V1.0

We’re doing some BSP work for a customer who has given us their existing SMARC module, which looks to be a V1.0 with the A1 silicon on it. So we are using the older release to support this.

However the customer is going to be purchasing more modules over the next few months and from our point of view we’re wondering if the change of support means a later revision with the B0 silicon is due out imminently and so they could end up with a mix of A1 and B0 hardware.

Is there a way to ensure the Tezi installer picks the correct images the for hardware silicon revision? So if we need to generate 2 sets of images for them we can ensure the correct ones get installed by them. I think we’ve already accidentally installed the 7.4.0 demo images on the A1 hardware, resulting in it not booting etc.

Cheers

Marc

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

TEZI Hardware Compatibility and Image Selection

Based on the available documentation, I can provide some guidance on TEZI’s behavior and hardware compatibility, though the specific details about silicon revision detection for i.MX95 are not fully covered in the current sources.

TEZI Installation Process

The Toradex Easy Installer (TEZI) operates by presenting available OS images for installation (1). When TEZI starts, it displays a list of available images that can be installed on the module (2). The images can be sourced from:

  • Local storage (SD card, USB memory)
  • Network download from Toradex servers (2)

Hardware Detection Considerations

While the documentation doesn’t explicitly detail silicon revision detection for i.MX95, TEZI does have hardware awareness capabilities. The installer is designed to work with specific hardware configurations, and images are typically built for particular machine targets (3).

Machine Configuration in Yocto Builds

When building custom images, the MACHINE variable specifies the target device (3). For i.MX95-based modules, this would determine hardware-specific configurations including silicon revision support.

Recommendations for Mixed Hardware Scenarios

Given your situation with potentially mixed A1 and B0 silicon:

  1. Separate Image Sets: You’ll likely need to maintain separate BSP builds - one for the older release supporting A1 silicon and another for B0 silicon compatibility.

  2. Image Organization: When preparing TEZI installations, clearly organize and label your images to distinguish between silicon revisions.

  3. Installation Process: The TEZI interface allows you to select specific images during installation (2). Ensure your team understands which images correspond to which hardware revision.

Current Documentation Limitations

The available sources don’t provide specific details about:

  • Automatic silicon revision detection in TEZI for i.MX95
  • Automatic image filtering based on hardware compatibility
  • Specific mechanisms to prevent incompatible image installation

For the most current information about i.MX95 silicon revision support and TEZI compatibility mechanisms, you may need to consult the release notes and hardware-specific documentation for your BSP version.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

Hi @mkelly_tgp!

Ideally, your customer should avoid using two SMARC i. MX95 with different silicon revisions for production.

In this case, you could have two separate storage devices with different images, one for A1 and the other for B0 (for example, using USB sticks).

Do you know how many A1 types your customer currently has and how many B0 units they plan to purchase?

Best regards.

4

Hi Lucas,

Thanks for the reply. For now we’re going to tell them to keep an eye on what modules they have and what revisions. I don’t think the device with the SMARC modules is going to be a mass produced system, so hopefully it should be possible to keep track manually of which systems contain which revision in the future.

Cheers

Marc.

1 Like