Nations Technologies NS350 TPM Reaches Volume Production Inside Two Qualcomm Ecosystem Designs: Edge AI Box and AC Wallbox Carry a TPM 2.0 Root of Trust, CC EAL4+ for EU CRA

恒森科技
Nations TechnologiesTPM 2.0trusted computingedge AIEV charging
At electronica 2026 in Munich, Nations Technologies' NS350 trusted computing chip appeared in two Qualcomm-based designs: an Edge AI Box on the Dragonwing platform and a smart charging Wallbox on Qualcomm's powerline communication silicon. The company says cooperation on both has entered volume production. The 40 nm NS350 family ships TPM 2.0 (SPI) and TCM 2.0 (I2C, SM2/SM3/SM4) profiles and holds ANSSI-CC-2024/31 at EAL4 augmented with AVA_VAN.4, bound to firmware 30.30.9220.9488.

At electronica 2026 in Munich, held 10–13 November, Nations Technologies put two terminals on display inside a partner's ecosystem: an Edge AI Box that runs inference and connectivity locally on Qualcomm's Dragonwing platform, and a smart charging Wallbox that uses Qualcomm's powerline communication (PLC) silicon to talk to the vehicle. Both machines carry the same component — the NS350 trusted computing chip. In a product release dated 13 November, the company states that cooperation on the two designs "has entered volume production".

The division of labour: the platform connects, the secure chip certifies

Put the two designs side by side and the structure of the announcement becomes clear. The Edge AI Box targets smart gateways, energy monitoring and industrial controllers; its commercial value is local inference plus uplink connectivity. The Wallbox targets EV charging, where the value is a stable link between car and charger. Neither requirement is solved by compute: the box has to demonstrate that the software it is running has not been altered, and the charger has to demonstrate that both the vehicle and the charger are legitimate devices. Both are jobs for a hardware root of trust.

Nations Technologies reduces that root of trust to three functions — device identity, key protection and boot integrity verification. For a device maker, that reframes all three as a line item rather than firmware work: a part number to specify, a certification number to cite in a tender, and a certificate injection step that can be standardised on the production line.

The platform side matters too. Dragonwing is Qualcomm's industrial and embedded IoT brand, launched in February 2025 and expanded across the IE-IoT portfolio at CES in January 2026; one analyst note counts more than 200 ecosystem partners and 35 distributors. A security chip entering that ecosystem is not chasing single-unit volume — it is entering reference designs that module and box makers will reuse.

Two firmware personalities: TPM 2.0 and TCM 2.0

The NS350 is not a single-personality part. The same family ships in two firmware configurations that map to the international and the Chinese trusted-computing standards:

  • v30 runs TPM 2.0: compliant with TCG TPM Main Specification Level 00 Rev 1.59 and the PC Client platform specification 1.05 rev 14, over SPI, with RSA 2048/3072/4096 and ECC NIST P-256/P-384, hashing in SHA-1, SHA-256 and SHA-384;
  • v33 runs TCM 2.0: compliant with GM/T 0012-2020, over I2C, with SM2/SM3/SM4 and 24 PCRs using SM3;
  • Shared specifications: 40 nm process, QFN32 and QFN16 packages, 1.8 V or 3.3 V supply, standard (−20 to +85 °C) and enhanced (−40 to +85 °C) temperature grades, typical standby current of 75 µA, secure field firmware upgrade, and three pre-provisioned endorsement key certificates (RSA 2048, RSA 3072, ECC P-384).

The practical benefit sits at product-line level: one hardware design, with export variants fitted with v30 for the TPM 2.0 ecosystem and domestic variants fitted with v33 for the TCM 2.0 regime, without touching the power rail or the footprint. For a manufacturer selling into both markets, that is cheaper than maintaining two separate security architectures.

What the EAL4+ certificate actually covers

The company's public shorthand is "internationally CC EAL4+ certified". The precise anchor is French certificate ANSSI-CC-2024/31, issued 5 October 2024, covering the NS350 v30 with TPM firmware 30.30.9220.9488 at EAL4 augmented with ALC_FLR.1 and AVA_VAN.4, against the PC Client Specific TPM 2.0 protection profile (PP PCCS TPM F2.0 L0 r1.59 V1.3). Thales/CNES performed the evaluation, the developer is the Shenzhen entity, and the sponsor is the Singapore subsidiary NSING Technologies.

Three details belong in a selection document rather than the headline. The certificate is bound to a firmware version, so a customer shipping new firmware must confirm the new version is still inside the coverage — the certificate does not carry over automatically. AVA_VAN.4 is the vulnerability-analysis component, meaning resistance to enhanced-basic attack potential, and it is where TPM-class parts separate from each other even at the same EAL4 base. Most often missed is the recognition scope: under the international CCRA arrangement this certificate is recognised only up to EAL2 plus ALC_FLR.1, while full EAL4 recognition comes from the European SOG-IS agreement — which makes the certificate carry more weight in Europe than in parts of North America and Asia.

Separately, the data brief lists FIPS 140-2 level 2 (physical security level 3) as a targeted certification rather than an achieved one — worth checking before quoting it in a North American government or enterprise project.

Edge AI box: proving who is running

In an edge box, the TPM's most useful job is turning "is this device still running the firmware it shipped with" into a verifiable fact. Boot measurements are extended into PCRs, device identity and keys stay inside the chip, and the cloud side receives a measurement it can verify rather than a self-declaration. Anti-cloning, anti-tamper and protection against a compromised node joining the network all rest on that single mechanism.

It also explains why a TPM rather than a generic secure element. TPM 2.0 is a standardised interface that Windows and Linux measured-boot and remote-attestation stacks already speak, so the box maker does not have to invent a protocol. A general-purpose secure element offers a stronger key container but needs custom software to sit inside an OS trust chain.

Charging: where the Plug & Charge private key lives

Vehicle-to-charger communication is moving along the ISO 15118 series. Qualcomm's PLC line (QCA7000/QCA7005/QCA7006AQ, HomePlug Green PHY) is documented as compliant with ISO 15118 parts 1, 2 and 3, interoperable with IEEE 1901 and meeting CCS Type 1 and Type 2 requirements. Under ISO 15118-20, mutual authentication runs over TLS 1.3 and Plug & Charge depends on a certificate PKI, with contract certificates and private keys held at both the vehicle and the charger.

A private key in MCU flash and a private key inside a dedicated trusted-computing chip are two different risk models. In the former, physical access plus a firmware read takes the credential with it. In the latter, credentials are isolated inside a die with active shielding and environmental monitoring, and authentication completes inside the chip. The company's wording for the charging case — identity verification before charging, credentials isolated inside the trusted computing chip, protection against power theft and identity forgery — is aimed at the same property. For a charge point operator the value is traceability of billing and roaming settlement; for the charger maker it is passing the vehicle OEM's and the operator's onboarding tests.

The compliance calendar: CRA is not due yet, RED already applies

Much of the coverage treats a chip like this as the key to the EU Cyber Resilience Act. That deserves unpacking. Regulation (EU) 2024/2847 entered into force on 10 December 2024; reporting obligations have applied since 11 September 2026 (early warning within 24 hours, full notification within 72 hours, final report within 14 days of a fix), and the main obligations only become fully applicable on 11 December 2027. The CRA is a set of process obligations on the manufacturer — vulnerability handling, a declared support period, CE marking — not a certification a component can hand over. What a chip supplies is technical evidence: measured boot, identity credentials, secure storage.

What is already being enforced is a different rule. Delegated Regulation (EU) 2022/30 under the Radio Equipment Directive has applied since 1 August 2025, adding cybersecurity, privacy and fraud-prevention requirements for the covered categories, with EN 18031-1/2/3 as the harmonised standards. A charger or an edge box with Wi-Fi or cellular connectivity has to clear that today. Delegated Regulation (EU) 2026/339, published in April 2026, repeals 2022/30 with effect from 11 December 2027, so the two regimes are deliberately stitched into a single timeline rather than run in parallel.

HSY Perspective

The real change is not EAL4+ arriving in a charger; it is that device identity has become a line item that can be written into a bill of materials. That capability used to live inside a solution provider's firmware, where customers could see the function but not the evidence. Once it has a part number, a certification number and a production-line provisioning step, procurement and engineering can finally discuss security on the same sheet of paper.

Three publicly checkable facts support that reading. ANSSI-CC-2024/31 puts EAL4 augmented and AVA_VAN.4 in writing and binds them to a specific firmware version. The NS350 family ships TPM 2.0 and TCM 2.0 profiles, so one BOM covers domestic and export product lines. Qualcomm's Dragonwing and PLC platforms already carry more than two hundred ecosystem partners, which means reference designs get reused rather than rebuilt. Together they push the secure element from project customisation toward catalogue part: pricing and lead time become more predictable, and differentiation migrates to certificate-chain management, consistency of provisioning, and re-assessment after every firmware revision.

The boundary is worth stating. Under CCRA the EAL4+ certificate is mutually recognised only to EAL2, so buyers in markets that assess against their own national recognition rules will discount it; and because the certificate is firmware-bound, any production firmware change may need its coverage reconfirmed — a question that will appear in more supplier questionnaires each year. If EU harmonised standards and guidance after 2027 make component-level evidence chains explicit, then "does it have a TPM, at what level, from which lab" moves from a scoring bonus to an entry requirement. If device makers keep treating the chip as compliance paperwork rather than an architectural decision, it stays an expensive piece of memory.

Sources: Nations Technologies product release of 13 November 2026 on the Qualcomm-ecosystem Edge AI Box and Wallbox; NS350 product page and NS350 v30/v33 data briefs; ANSSI certification report ANSSI-CC-2024/31 (5 October 2024); Messe München electronica 2026 dates; Qualcomm automotive PLC solutions guide; European Commission material on the Cyber Resilience Act and Delegated Regulations (EU) 2022/30 and (EU) 2026/339.