Talk

Tips and Tricks for Designing Real-time IoT Systems

Watch Now

01:19:58

EOC 2021

Talk

Tips and Tricks for Designing Real-time IoT Systems

Jacob Beningo

01:19:58 EOC 2021

Jacob Beningo

01:19:58

IoT devices are becoming more complex and compute-intensive with every passing month. Keeping up with customer needs and requirements requires a design that is not just updatable and robust but also scalable and configurable.

In this session, we will explore practical tips and tricks for designing real-time IoT systems. Major topics that we will discuss include:

Challenges facing IoT Developers
Software architecture design
Identifying and leveraging execution domains
Device security

1 / 6

Please log in or create an account to test your knowledge and see the answers.

When getting started with securing a real-time embedded IoT device, what did Jacob Beningo recommend as the first practical framework to consult for threat-based security analysis and architecture guidance?

A Design and implement your own proprietary cryptographic stack from scratch

B Use ARM’s Platform Security Architecture (PSA) to guide threat analysis and architecture

C Rely solely on network encryption (e.g., TLS) and skip architecture-level analysis

D Start by deploying containers (Docker) on the device as the primary security boundary

E Postpone security until after the product is fielded and monitor for breaches

If your product uses a standard single-core microcontroller that does not provide multicore or TrustZone hardware features, which mechanism did Jacob recommend using to create isolation between software domains?

A Add a second physical microcontroller to act as a secure core

B Use ARM TrustZone as the isolation mechanism

C Rely on Docker containers running on the microcontroller

D Use a Memory Protection Unit (MPU) or SMPU to partition memory and isolate domains

E Disable interrupts globally to prevent cross-domain interaction

Why does Jacob emphasize thinking through the "secure device lifecycle" during design?

A Because security only matters at manufacturing and can be ignored once the device is fielded

B Because each stage (provisioning, commissioning, onboarding, operation, updating, retirement) has a different security context and needs explicit planning

C Because firmware updates are unnecessary if you provision devices correctly at the factory

D Because monitoring and auditing are only useful during development, not in the field

E Because retirement is the only stage requiring secure handling of keys and data

What software-architecture approach did Jacob recommend to make IoT application code more portable, testable, and resilient to supply-chain/hardware changes?

A Bottom-up: write hardware drivers and middleware first, then build application logic tightly coupled to them

B Top-down: design the application/business logic first, decouple it from hardware with an abstraction layer, and simulate/emulate the app before hardware work

C Skip abstraction layers entirely to improve runtime performance on constrained MCUs

D Write application code directly against vendor-specific peripheral registers for maximum control

E Delay software architecture decisions until after production hardware is finalized

According to Jacob, what three elements must be balanced to achieve a successful real-time embedded product delivery?

A Implementation, marketing strategy, and sales forecasts

B Implementation, architecture, and processes (e.g., CI/CD, testing)

C Hardware selection, color of the enclosure, and web UI design

D Only implementation matters; architecture and processes can be omitted if time is short

E Architecture, customer support, and pricing strategy

Which of the following was NOT listed by Jacob as one of the four main application domains you must explicitly manage when partitioning an IoT system?

A Privileged domain (privileged vs unprivileged execution)

B Security domain (secure vs non-secure processing environments)

C Execution domains (separate cores/processors for execution)

D Cloud domain (what to offload to cloud vs local)

E User-interface domain (a standalone domain specifically for UI separate from other domains)

Formatting help

italics	surround text with asterisks
bold	surround text with two asterisks
hyperlink	[hyperlink](https://example.com) or just a bare URL
inline code	surround text with single `backticks`
code block (multi-line)	wrap on its own lines with three backticks: ``` your code here ```
~~strikethrough~~	surround text with ~~two tilde characters~~
quote	prefix with >

Upvotes Newest Oldest

Stephane.Boucher

Score: 0 | 4 years ago | no reply

If you do not have an account on this platform, you first need to create one before you can access this webinar:
https://www.embeddedonlineconference.com/freesession/Tips_and_Tricks_for_Designing_Realtime_IoT_Systems.php

Partners & Sponsors

Percepio

Zeroplus

Edge Impulse

Crank Software

STMicroelectronics

Microchip

Joulescope

The Qt Company

NXP

TUXERA

XMOS

Lager

Qoitech

Become a Sponsor