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

Embedded engineering bench in India, illustrating the hardware a developer can act on today, supported by GSAS
Technical Guides Arm

Arm's Agentic AI Push: What Indian Embedded Teams Can Actually Use Today

Arm has set out its platform strategy for the agentic era, putting inference everywhere it has compute. Indian embedded teams can start on that direction this quarter with the Cortex-M toolchain they already own: Helium, CMSIS-NN, Ethos-U and Vela, on boards you can order today.

13 Sept 2026 · 7 min read
Embedded development bench, illustrating the hardware debug loop an AI agent can now drive, supported in India by GSAS
J-Link SEGGER

An AI Agent That Drives the Debugger: SEGGER and Embedder Connect J-Link to the Loop

SEGGER has given an AI coding agent direct control of J-Link and J-Trace: flash, breakpoints, memory inspection and live RTT on real silicon. The loop only works if the probe can read target RAM while the core runs, and GSAS field engineers know exactly where that breaks first.

13 Sept 2026 · 6 min read
Master and slave roles on a 100BASE-T1 link: the master PHY times its transmitter from a local clock, the slave recovers the clock from the received signal, with the both-master and both-slave misconfigurations that leave the link down, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

100BASE-T1 Link Won't Come Up: A Vendor-Neutral Checklist

A 100BASE-T1 link that will not come up is almost never a mystery, but the answers on the web are written per silicon vendor and do not transfer. This is the ordered bring-up checklist that holds regardless of which PHY, switch or SoC you have: physical layer first, then the PHY over MDIO, then the master and slave pairing, then the causes of a link that comes up and drops. The standards and tooling claims trace to IEEE 802.3 task force records, the Linux ethtool and kernel documentation or published test material. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 14 min read