Demo

Introducing Modern Embedded Development Flows

Christopher Seidl

Watch Now

10:47

EOC 2023

Login to Watch

Christopher Seidl

Christopher Seidl is a Director of Product Management with over twenty years of experience in the industry. He responsible for the Keil tools, including Keil MDK, Arm’s leading development environment for Cortex-M based microprocessors. The Keil team is now working on the future of embedded software development using modern cloud-native technologies.

View full profile

Topics Covered

Agile/Processes

Demo

Introducing Modern Embedded Development Flows

Christopher Seidl

10:47 EOC 2023

Christopher Seidl

10:47

This quick demo shows how to use modern CLI-based tools for embedded development. It introduces Keil Studio, a set of VS Code extensions that are relying on the CMSIS-Toolbox for managing and building projects. We will also show how to use Arm Virtual Hardware with GitHub Actions to enable DevOps in the cloud.

1 / 3

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

What is the main reason Christopher Seidl stresses using the same command-line executables in both the CI pipeline and the local IDE?

A To ensure the build output is the same in CI and locally (reproducible builds).

B Because GUIs are deprecated and should never be used for embedded development.

C To make compile times significantly faster than using GUI toolchains.

D So developers can avoid using Git and work only on local files.

E To enable remote-only debugging that cannot be done locally.

According to the talk, what role does Arm Virtual Hardware (AVH) play in a modern embedded CI/CD flow?

A It lets the CI run simulations of the processor models so builds and tests can run without physical hardware.

B It permanently replaces physical development boards so you never need hardware again.

C It is only used for GUI-centric interactive debugging and cannot be run in CI.

D It is primarily a tool for flashing real devices over USB during CI runs.

E It acts as a package manager to cache vcpkg packages for the runner.

How does the solution YAML and the use of packs (CMSIS pack, compiler pack, BSPs) help when building for different targets in the demo?

A They declare the target types and reference the specific project YAMLs and packs so the same repository can build for simulator or actual hardware.

B They automatically translate the C source code into a different programming language per target.

C They remove the need for any board support packages by abstracting hardware completely.

D They force all builds to run only on the local machine and prevent CI execution.

E They are only used to generate the graphical representation in VS Code and have no effect on builds.

Formatting help

italics	surround text with asterisks
bold	surround text with two asterisks
hyperlink	[hyperlink](https://example.com) or just a bare URL
code	surround text with `backticks`
~~strikethrough~~	surround text with ~~two tilde characters~~
quote	prefix with >

Upvotes Newest Oldest

ChristopherSeidlSpeaker

Score: 0 | 3 years ago | no reply

Hello Victor,
thanks for the questions!

Currently, you need to create the YML input files by hand, but we're working on an interactive development of these as well. Will be ready once we go live towards the end of the year.
The project is here: https://github.com/Arm-Examples/RTX_Blinky
This workflow works for Arm-based MCUs only at the moment.

Hope this helps,
Christopher

victorhe

Score: 0 | 3 years ago | no reply

HI, Christopher,
Thanks for your great video. my question for this video is at 2:00,

how to create the workflow file? ( using the text editor to create it or there are some tools software for it?
can you share the link for the project for us?
Is this workflow file works just for ARM family of MCUs or it works for any MCUs?
Thanks a lot.

Partners & Sponsors

STMicroelectronics

Amazon AWS

Golioth

The Qt Company

Memfault

NXP

SEGGER Microcontroller

PE Micro

PX5

Become a Sponsor