Skip to main content
Trustzone implementation in Armv8-M architecture, featured image

Trustzone implementation in Armv8-M architecture

GSAS Engineering · · 1 min read

Trustzone implementation in ArmV8-M architecture

TrustZone technology by Arm provides a system-wide approach to security, applicable across various processors including the Cortex-A and Cortex-M series. It creates an isolated execution environment that separates secure and non-secure code, which helps to protect sensitive information and functions. The key features include Isolation of Secure and Non-Secure Worlds,  Reduced Attack Surface,  Flexible Security Implementation,  Enhanced Secure Boot,  Protection of Cryptographic Operations,  Secure Firmware Updates, and Secure Inter-Process Communication (IPC).

 

Join us for the webinar to learn more about implementing the same technology on ArmV8-M architecture. The building blocks of this technology will be discussed briefly.

Agenda:

  • Security Attribution Unit (SAU)
  • **Implementation Defined Attribution Unit (IDAU)
    **
  • Non-Secure Callable (NSC) Region
  • Secure and Non-Secure MPU
  • Debug Control

Timing:

Wednesday, 28th August 2024 | 3:30 PM to 04:30 PM

 Webinar Recording


About GSAS Webinar Series

GSAS Micro Systems regularly hosts webinars, workshops, and technical seminars to help India’s embedded engineering community stay current with the latest tools, techniques, and industry standards. Our events feature hands-on demonstrations and expert guidance from our applications engineering team.

Request a private session for your engineering team, or browse our complete event archive.

Also appears in:

Interested in Arm tools?

Talk to our application engineers for personalized tool recommendations.

Stay in the Loop

Get monthly compliance updates, product insights, and engineering best practices delivered to your inbox.

Related Articles

Horizontal stacked bar showing where an ADAS test vehicle's bandwidth budget is spent, split into cameras, lidar, radar and bus traffic, with the logger uplink limit drawn as a vertical rule crossing the bar, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

ADAS Sensor Data Logging: Bandwidth Budgets That Add Up

Every page that tells you an ADAS test vehicle produces terabytes a day states the headline and skips the arithmetic, so you cannot redo it for your own sensor set. This article publishes the arithmetic instead: one formula, every table row derived on the page, a worked eight-hour drive that chains those rows into a sustained write rate, a media count and an offload window, and the five places bandwidth budgets go wrong. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 15 min read
Storage sizing ladder for automotive data logging: four rungs stepping from an aggregate link rate of 1 Gbit/s to 125 MB per second, then 450 GB per hour, then 3.6 TB per eight-hour shift, then 18 TB per five-day week, in decimal units, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

Automotive Data Loggers: Capture Without Loss

Search for an automotive data logger and the results split into cheap OBD dongles at one end and enterprise ADAS recorders at the other, with nothing in between explaining the engineering that decides whether you lose frames. This is the loss budget end to end: mirror oversubscription upstream of the logger, encapsulation overhead on the capture path, sustained write rate against burst rate, rotation stalls, and storage arithmetic worked in full so you can redo it with your own numbers instead of trusting ours. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 13 min read
The bench to harness adapter path drawn left to right: the ECU connector, a test lead, a media converter or pluggable T1 module, RJ45, and the host, showing where each connector family sits between the device under test and the laptop, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

Automotive Ethernet Connectors: H-MTD, MATEnet, MQS

An ECU arrives on the bench with a connector nobody has a mate for, and the day is gone. Search the family names and you get connector product pages that describe their own part and stop there. This article puts the families side by side in one table using only what their public pages state, then makes the point those pages leave out: the IEEE link segment definition, not the connector, is what sets reach and loss limits, and shielding is a channel decision rather than a preference. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 12 min read