Direct RF Sampling vs Superheterodyne: Choosing an RFSoC Front End
Direct RF sampling now reaches 18 GHz. How to choose between direct sampling and superheterodyne for an RFSoC front end, and the filter, clock and decimation specs that choice sets.
Back to top
The security landscape for embedded systems has grown more complex over the past decade. What were once isolated devices are now deeply connected to networks, cloud services, and critical infrastructure. This shift exposes embedded platforms to a wider range of attacks — from remote exploits to physical tampering.
Relying solely on software-based protections leaves embedded systems vulnerable. If an attacker gains access to the firmware or OS, they may be able to bypass authentication checks, manipulate code execution, or extract sensitive data. Software defenses can be modified, overwritten, or disabled — especially if the device lacks a way to ensure its own integrity at startup.
A Trusted Platform Module (TPM) establishes a hardware root of trust. This means critical cryptographic operations — such as key generation, signing, or attestation — occur within a tamper-resistant chip, rather than in general-purpose memory where they might be exposed. By anchoring trust in hardware, TPMs prevent attackers from easily subverting security mechanisms, even if the operating environment is compromised.
The value of TPMs becomes clear when applied to embedded systems in high-stakes environments:

By anchoring trust in hardware, TPMs deliver the resilience that modern embedded systems require — something software alone cannot achieve.

For a practical look at how TPMs support secure lifecycle management, explore our on-demand webinar: Implementing Secure Software Upgrades in Embedded Systems: Best Practices and TPM Integration.
While TPMs are often described as “security chips,” their internal design is far more sophisticated than a simple key vault. A TPM combines specialized hardware circuits, cryptographic engines, and defined interfaces that together provide a robust framework for trust in embedded systems.
At the foundation, a TPM includes:
These features ensure that sensitive security operations occur in hardware, isolated from the main system processor.
PCRs are a defining feature of TPMs. These registers securely store measurements of the system state — such as firmware hashes, bootloader checksums, or OS integrity values.
In effect, PCRs make it possible to link device behavior to its integrity at boot and runtime.
Unlike software key stores, a TPM ensures that private keys never leave the chip unencrypted. Operations such as decryption, signing, or sealing occur internally. This prevents keys from being copied, dumped, or exposed during runtime.
TPMs connect to embedded systems through lightweight hardware interfaces such as SPI, LPC, or I²C, making them compatible with a wide range of processors and SoCs. Once integrated, the TPM works in tandem with firmware, secure bootloaders, and operating systems to provide:
By bridging hardware security with system-level design, TPMs offer a standardized, reliable way to enforce trust in embedded platforms.
Understanding the theory behind TPMs is one thing — embedding them successfully into real-world designs is another. Implementation requires careful attention to system integration, firmware workflows, and long-term device lifecycle management.
The most common use of a TPM is to protect sensitive assets such as device identities, private keys, or certificates. Rather than storing these in system flash or external memory, the TPM generates and safeguards them internally. Designers can also use sealed storage, which ties keys to specific Platform Configuration Register (PCR) values, ensuring they can only be accessed when the device is in a trusted state.

👉 This design approach echoes many principles of secure boot and runtime protection covered in our webinar on Secure Boot and Runtime Security in FPGA-Based Embedded Systems.
TPMs allow embedded devices to validate their state by checking PCR measurements. For example, if firmware is modified outside of an authorized update process, the resulting hash will no longer match the expected PCR value. In practice, this means the system can refuse to decrypt sensitive data or block network authentication until it is restored to a known-good state.
Beyond secure boot, TPMs strengthen device authentication and secure communications:
For embedded engineers, a successful TPM deployment requires thoughtful hardware and software co-design:
👉These integration choices often intersect with broader embedded system design trade-offs — whether deciding how to partition functions between hardware and software, or selecting the right interface (SPI, LPC, I²C) for minimal overhead. Our blog on Balancing Hardware-Software Partitioning in FPGA-Based Systems explores these considerations in depth.
Once the fundamentals of key storage and attestation are in place, TPMs unlock a set of advanced features that allow embedded systems to operate with even stronger security guarantees. These capabilities are especially valuable in sectors like automotive, industrial automation, and defense, where resilience and trust are non-negotiable.
TPMs play a central role in establishing secure boot processes. By ensuring that every stage of the boot chain — from firmware to the operating system — is measured and verified before execution, they prevent unauthorized or malicious code from running. This “chain of trust” approach forms the foundation of trusted computing in embedded devices.
TPMs allow developers to define fine-grained authorization policies for cryptographic keys. For example, a key may only be usable when specific PCR values are present, or when a password or external authorization factor is provided. This ties system functionality directly to its integrity state and helps enforce strict operational security.
With key sealing, data is encrypted and bound to a particular TPM and device state. It can only be “unsealed” when the platform’s PCR values match the trusted baseline. This ensures that even if data is copied to another system or if firmware is altered, the secrets remain inaccessible.
While TPMs add layers of security, they must also support reliable recovery paths. Common strategies include:
By combining secure boot, controlled access policies, sealed storage, and reliable recovery, TPMs enable embedded systems to withstand both digital and physical attack vectors while maintaining operational continuity.
TPMs are no longer limited to PCs and enterprise servers — they have become a critical enabler of trust in embedded systems across multiple industries. Their ability to provide hardware-backed identity, secure storage, and integrity validation makes them well-suited for high-value applications where reliability and security go hand in hand.
Modern vehicles contain dozens of Electronic Control Units (ECUs), each responsible for functions like braking, steering, or infotainment. Attackers targeting these systems may attempt to inject malicious firmware or spoof communications on the CAN bus.
👉 This aligns closely with Fidus’ experience in complex automotive and transportation electronics, where security, performance, and compliance must all be engineered together.
Programmable Logic Controllers (PLCs) and Supervisory Control and Data Acquisition (SCADA) devices are at the heart of manufacturing, energy, and utility operations. A compromised controller could result in production downtime or even physical damage.
👉 These requirements overlap with custom embedded system design services, where integrating TPMs alongside FPGAs or SoCs provides both processing performance and resilience.
IoT nodes are attractive targets for attackers since they are often deployed in the field with limited monitoring. Device cloning, man-in-the-middle attacks, and rogue network access are common risks.
👉 This directly connects to Fidus’s work in secure IoT device development, where hardware-backed trust and low-level software integration are essential for scale.
Case studies of successful TPM deployments
Each of these examples demonstrates how TPMs bridge the gap between theory and practice — turning cryptographic capabilities into tangible trust in embedded devices.
While today’s TPMs already address critical embedded security challenges, the landscape continues to evolve. Designers must not only secure against current threats but also prepare for what lies ahead.
For engineering teams, building with TPMs is not just about today’s security — it’s about ensuring long-term trustworthiness in embedded platforms that may remain in the field for a decade or more.
Trusted Platform Modules deliver a hardware foundation for embedded system security that software alone cannot provide. By safeguarding cryptographic operations, validating system integrity, and enabling trusted execution, TPMs help designers mitigate today’s threats while preparing for tomorrow’s.
For embedded teams, the decision to integrate a TPM is no longer optional — it’s a requirement for achieving resilience, compliance, and trust in connected devices.
To see TPMs in action and explore how they enable secure lifecycle management, don’t miss our on-demand webinar: Implementing Secure Software Upgrades in Embedded Systems: Best Practices and TPM Integration.
Direct RF sampling now reaches 18 GHz. How to choose between direct sampling and superheterodyne for an RFSoC front end, and the filter, clock and decimation specs that choice sets.
At 112G PAM4, most channel margin is lost at the transitions, not along the trace. Fidus Signal Integrity Architect Dr. Syed Bokhari explains how stackup, vias, BGA breakout and connector footprints decide 112G and 224G margin, and how COM proves it.
An SRAM adaptive SoC puts configuration scrubbing, interrupt recovery and TMR into your satellite payload design. A flash-based rad-hard FPGA removes that work and caps compute. Here’s how to scope it before choosing the part.
Trust us to deliver on time. That’s why 95% of our customers come back.