On September 28th, 2023 at noon EDT / 9 am PDT, we’re hosting a webinar with Keenan Johnson of the Ribbit network! You have seen Keenan featured in our Case Study about Ribbit where we detail how they are using Golioth to power their fleet of environmental monitors. We’ve been giving away Ribbit kits to new newsletter signups, so be sure to sign up and enter the sweepstakes if you haven’t already.

But really we want to get into the nitty-gritty details of environmental monitoring: what are the challenges for putting devices into the field and how does someone address those challenges with a connection to the internet?

This session will cover things like:

  • Protecting a project from the elements while also still measuring those elements
  • Creating resource efficient communications back to the internet to prolong device life
  • Gathering relevant fleet health data to ensure long deployments
  • Working with community partners to deploy sensor networks asynchronously
  • Visualizing data in a useful way for all stakeholders
  • Utilizing automation to reduce engineering overhead for a large sensor network
  • Empowering citizen science to improve environmental monitoring

The presentation will last approximately 40 minutes, followed by a Q&A session with attendees that can ask questions directly to Keenan. Sign up for the webinar below!


As embedded developers, we’re consistently seeking ways to make our processes more efficient and our teams more collaborative. The magic ingredient? DevOps.Its origins stem from the need to break down silos between development (Dev) and operations (Ops) teams. DevOps fosters greater collaboration and introduces innovative processes and tools to deliver high-quality software and products more efficiently.

In this talk, we will explore how we can bring the benefits of DevOps into the world of IoT. We will focus on using GitHub Actions for continuous integration and delivery (CI/CD) while also touching on how physical device operations like shipping & logistics which can be streamlined using a DevOps approach.

Understanding the importance of DevOps in IoT is crucial to unlocking efficiencies and streamlining processes across any organization that manages connected devices. This talk, originally given at the 2023 Embedded Online Conference (EOC), serves as one of the many specialized talks freely accessible on the EOC site.

GitHub Actions for IoT

To illustrate how to put these concepts into practice, we’re going to look at a demo using an ESP32 with a feather board and Grove sensors for air quality monitoring. It’s important to note that while we utilize GitHub Actions in this instance, other CI tools like Jenkins or CircleCI can also be effectively used in similar contexts based on your team’s needs and preferences.

For this example we use GitHub Actions to automate the build and deployment process.

The two main components of our GitHub Actions workflow are ‘build’ and ‘deploy’ jobs. The ‘build’ job uses the pre-built GitHub Action for ESP-IDF to compile our code, and is triggered when a new tag is pushed or when a pull request is made. The ‘deploy’ job installs the Golioth CLI, authenticates with Golioth, uploads our firmware artifact, and releases that artifact to a set of devices over-the-air (OTA).

Imagine an organization that manages a fleet of remote air quality monitors across multiple cities. This GitHub Actions workflow triggers the build and deployment process automatically when the development team integrates new features or bug fixes into the main branch and tags the version. The updated firmware is then released and deployed to all connected air quality monitors, regardless of their location, with no additional logistics or manual intervention required. This continuous integration and deployment allows the organization to respond rapidly to changes and ensures that the monitors always operate with the latest updates.

Let’s delve into the GitHub Actions workflow and walk through each stage:

  1. Trigger: The workflow is activated when a new tag is pushed or a pull request is created.
        # Publish semver tags as releases.
        tags: [ 'v*.*.*' ]
        branches: [ main ]
  2. Build: The workflow checks out the repository, builds the firmware using the ESP-IDF GitHub Action, and stores the built firmware artifact.
        runs-on: ubuntu-latest
        - name: Checkout repo
          uses: actions/checkout@v3
            submodules: 'recursive'
        - name: esp-idf build
          uses: espressif/esp-idf-ci-action@v1
            esp_idf_version: v4.4.4
            target: esp32
            path: './'
            WIFI_SSID: ${{ secrets.WIFI_SSID }}
            WIFI_PASS: ${{ secrets.WIFI_PASS }}
            PSK_ID: ${{ secrets.PSK_ID }}
            PSK: ${{ secrets.PSK }}
        - name: store built artifact
          uses: actions/upload-artifact@v3
            name: firmware.bin
            path: build/esp-air-quality-monitor.bin
  3. Deploy: The workflow installs the Golioth CLI, authenticates with Golioth, downloads the built firmware artifact, and uploads it to Golioth for OTA updates.
        runs-on: ubuntu-latest
        - name: Checkout repo
          uses: actions/checkout@v3
            submodules: 'recursive'
        - name: esp-idf build
          uses: espressif/esp-idf-ci-action@v1
            esp_idf_version: v4.4.4
            target: esp32
            path: './'
            WIFI_SSID: ${{ secrets.WIFI_SSID }}
            WIFI_PASS: ${{ secrets.WIFI_PASS }}
            PSK_ID: ${{ secrets.PSK_ID }}
            PSK: ${{ secrets.PSK }}
        - name: store built artifact
          uses: actions/upload-artifact@v3
            name: firmware.bin
            path: build/esp-air-quality-monitor.bin

For those eager to dive in and start implementing DevOps into their own IoT development process, we’ve provided an example Github Actions workflow file on GitHub. Feel free to fork this repository and use it as a starting point for streamlining your own IoT firmware development process. Remember, the best way to learn is by doing. So, get your hands dirty, experiment, iterate, and innovate. If you ever need help or want to share your experiences, please reach out in our our community forum.

Visual Studio Code, colloquially known as VS Code, has become the de-facto Swiss Army Knife of Integrated Development Environments (IDEs). It is already configured for a lot of different languages and ecosystems when first installed. It’s also great for developing Zephyr RTOS projects, but not out of the box. Jonathan Beri presented at talk at the 2023 Embedded Open Source Summit detailing how to configure VS Code for Zephyr development.

To follow along, check out Jonathan’s example repository for us Zephyr in Visual Studio Code.

VS Code for Embedded Development

Most of the pre-configuration rolled into the stock installation of VS Code centers around languages used in web development. But increasingly we see the IDE called upon for embedded system development–moving beyond merely working with source code to include native debugging and flashing. These more specialized features tend to be the areas requiring custom configuration. Notably, Nordic and NXP are both actively developing VS Code environments for Zephyr.

For those who prefer to maintain their own workspace configuration, selecting the right extensions is a good place to start. The Microsoft’s extensions for C/C++ and Cmake are table stakes for embedded development. Jonathan also recommends the Cortex Debug plugin and suggests that Microsoft’s Embedded Tools is a newer plugin you may find useful.

Diving into Configuration Files

The meat of the talk comes about sixteen minutes in as Jonathan walks through the settings files he’s using to configure his workspace: settings.json, tasks.json, launch.json, and extensions.json. You can view these files in the example code repository.

Telling VS Code where to find GCC will get syntax highlighting and linting working well. Preventing CMake from trying to auto-configure Zephyr projects will silence a lot of the popup window noise when opening a new VS Code window. And setting up the task runner is akin to configuring aliases for your oft-used commands, accessible from the VS Code command palette. Finally, debugging configuration and recommended extensions round out the workspace-specific configurations using the built-in “profile” features.

All the Things You’ve Been Missing from VS Code

If you’ve already tried developing for Zephyr in VS Code it’s easy to forget what you’ve been missing. The live demo begins at about 20:30 and immediately shows the most basic annoyances have been solved. There are no longer random red squigglies sprinkled throughout your code, because VS Code now knows where to find all of the header files. You can jump to OS-specific function declarations as expected and access the function syntax hinting because the entire Zephyr tree is accessible for the extensions. These features are not novel, they’re just not fully configured out-of-the-box.

Building and flashing works as expected, because your target board and programmer have now been specified in the configuration. They’re triggered via simple to remember commands like west build that Jonathan added to the command palette via those JSON files. The serial terminal connection to the device is available in the IDE without having to juggle external console windows. The general noise floor of the IDE is almost non-existent at this point, all thanks to a comprehensive configuration that makes the developer experience worlds better.

Modern Tools for Modern IoT

Zephyr RTOS is paving the way for the next generation of embedded devices. As the Founder and CEO of Golioth, Jonathan Beri recognized the power of Zephyr to support cross-vendor hardware in the IoT space, which makes it possible for Golioth to support the hardware that you the choose (and not a narrow set of hardware required by your IoT Cloud). As this talk shows, he spends a lot of hands-on time with the RTOS and is sharing the workflow he has developed over the last several years.

Set aside an afternoon to prototype your IoT Fleet. Your first 50 devices are free with Golioth’s Dev Tier. Follow Jonathan’s examples for using VS Code, and you’ll be sending sensor data to the cloud in a matter of hours!

Golioth is your instant IoT cloud that lets you choose what hardware you want to use. We’re able to remain hardware agnostic because Zephyr RTOS has great cross-vendor support. As the fastest-growing RTOS, Zephyr is well worth learning, but we’ve found most people need a little help getting started. Golioth’s next free Zephyr training happens online on August 23rd. We hope to see you there!

We’ve been hosting these free trainings for the past two years, and our approach has evolved over that time. Golioth’s Lead Developer Relations Engineer, Chris Gammell gave a talk on how we approach hosting remote training at the 2023 Embedded Open Source Summit. Anyone interested in teaching a remote course on embedded development will find this interesting as you will surely face the same challenges we have.

Skipping the Dev Env Setup Process by Using Kasm

The biggest challenge to teaching a new embedded OS is not in the coding work the attendees will be doing, but in setting up every build environment correctly. It takes time to install all the compilers and library code. This is further complicated by differences in attendee OS choices, versions, and existing configuration. We found that anywhere from 45 minutes to the entire training was gobbled up with this step.

Kasm container for Zephyr development

Kasm container running inside Firefoxs show VS Code with the Zephyr build process in a terminal window

The solution we chose last fall is to pre-configure a build environment for all attendees. For an in-person training, this would best be done by providing a laptop to everyone that standardizes the experience. But we’re hosting training remotely, so we spun up a Kasm workspace so the build environment is loaded via web browser.

Each attendee logs into our Kasm instance, which includes the Zephyr SDK tools (compilers, etc), the Zephyr tree (kernel, driver, and library code), Golioth’s Zephyr Training example code repository, the self-guided Golioth Training docs, and Visual Studio Code (VS Code).

As Chris outlines in his talk, with this approach an attended can be compiling their first Zephyr code in a little more than one minute. Admittedly there is some tap-dancing around the issue of programming a local device when the code is being compiled in a remote container. But we’ve had great success doing this with Nordic’s desktop tools.

Getting That In-Person Atmosphere, When Not In Person

Our training is self-guided, using a Docusaurus-based document site that’s available to anyone interested. But one of the benefits of signing up for the live training is that Golioth staff who are experienced with Zephyr are there to share that experience and answer questions. This is no boring webinar, we take the remote-training experience and make it feel a lot more like being in a classroom!

Golioth Zephyr Training group photo from Gather.town

One of the study groups in Gather.town from the July 12th Golioth Zephyr Training

To add interactivity we use the Gather.town online platform. It’s feels a lot like the original Legend of Zelda; you have an 8-bit avatar that you can walk around the virtual classroom. When you get close to other people (or walk onto one of the table-group carpets) a group video chat automatically opens. You can raise your hand using an emoji and an instructor will walk over to help.

In three hours, we get to know each other, learn how to compile and run some code, and discuss myriad topics that transcend the words found on the self-guided training docs.

Upcoming Training

If your company is planning to host a remote training that centers around embedded engineering, watch Chris Gammell’s talk. He drills down from how Golioth conducts our training to the experiments that led us to these solutions. From large toolchains and local USB ports, to live interactions and working with different attendee skill levels, he will help you find the happy path for your organization.

If you’re still getting up to speed with Zephyr RTOS, join us for the upcoming Golioth Zephyr Training on August 23rd, 2023.

Golioth booth at 2023 Embedded Open Source Summit / Zephyr Developers Summit

The Golioth team just returned from the Embedded Open Source Summit after a fantastic week talking about Zephyr, Embedded Linux, and of course, the future of the Internet of Things. We presented talks, we showed off hardware demos at our booth, and we talked to hundreds of awesome engineers.

The Embedded Open Source Summit (EOSS) was a collection of different conferences hosted by the Linux Foundation, including the Zephyr Developer’s Summit (ZDS). Our booth  demonstrated the Golioth IoT platform used for automotive applications (CAN + GPS), power monitoring, air quality monitoring, and trash can monitoring; all based on Zephyr RTOS. Golioth makes it easy to connect microcontroller-based devices to the internet, with prebuilt features for data management and fleet control.

ZDS gives us the opportunity to discuss the many use cases we see from our customers with the developers and maintainers of the RTOS that we most often use. Having such direct insight into what’s coming down the road helps Golioth stay on the bleeding edge of what is possible.


The Golioth Zephyr SDK is an open source library build on top Zephyr RTOS. It delivers great cross-platform support and a wonderful network stack, and allows us to support the widest range of customer hardware needs. While we also offer a cross-platorm SDK based on FreeRTOS (which supports Espressif’s ESP-IDF, Infineon’s ModusToolbox™, and Linux), we see the widest interest in Zephyr from our customers.

We don’t just go to the Zephyr Developer’s Summit, Golioth is a silver member of the Zephyr Project. As a member of the Technical Steering Committee, we’re on weekly calls about the future of Zephyr, but nothing compares to spending in-person time with our friends and partners–ZDS is the perfect place to do that.

We presented three talks on our work with Zephyr over the past year, and enjoyed many of the other topics and discussion presented. Update: All videos have now been published on the Zephyr YouTube Channel!

Everyone Needs to Get Connected

Early morning Golioth booth before the EOSS/ZDS crowds arrived

There was a constant flow of interesting people to speak with at the Golioth booth. This year was a special treat, since ZDS was co-located with the Embedded Linux Conference, the Automotive Linux Summit, and three other conferences.

Overwhelmingly it’s apparent that there is a trend of moving IoT devices down the stack, from being Linux-based to being microcontroller based. That’s where Golioth specializes.

Jonathan Beri and Mike Szczys at the Golioth booth during 2023 EOSS/ZDS in PragueWith the silicon technology available today you should be able to connect microcontrollers to the internet, update the firmware remotely, send and received data with the device, and control not just one device but thousands upon thousands. You should be able to do this with a device you choose (and design with your exacting specifications0, not one dictated to you. You should not have to write all of this IoT cloud management code yourself. This is what we stand for, and what people told us they needed in conversation after conversation at this conference.

The development cycle for custom hardware is long, but your device management cloud software is already written. Give Golioth a try, your first 50 devices are free.

A Little Team-Building Goes a Long Way

Golioth team at the 2023 EOSS/ZDS conference dinner

We love conferences because we get to meet you there. But as a fully-remote company, we also get to meet the rest of the Golioth crew in person. Jonathan, Chris, and I were all at Embedded World in March, so it hasn’t been too long for the three of us. But it was quite exciting to meet Marko Puric, who joined us as a Field Application Engineer in May. Keep an eye out for more from Marko here on the blog and elsewhere in the Golioth universe.

IoT projects and products fail at a spectacularly high rate; not in the field, but by never making it out of the lab. One of the myriad reasons is time to market. When you have a fixed amount of time to make an idea work and deliver that product to the marketplace, you don’t get a lot of retries. That’s why I gave this talk about how to get the most out of your “Rev A” (first revision of) hardware. It was delivered as one of the free talks from the Embedded Online Conference (EOC) in 2023. You can view this and many other highly specialized talks on the EOC site. Registration is required for viewing the other free talks and there is a nominal fee to join the site and view the talks from this year and last year.

Balancing Act

Why not “move fast and break things”? Why bother caring about Rev A? Despite reduced costs around hardware thanks to quick turn manufacturing services domestic and abroad, it’s possible to get hardware fast…but there is still a delay between a Rev A and Rev B board. What’s more, the decisions you make in your early hardware prototypes can carry with you throughout the life of a product, and it makes sense to shoot for a best-case scenario when planning and executing your first spin of a prototype. This talk covered three areas of the prototype process.

Before Rev A

The “before” is all about planning, especially across different teams. Hardware designers for IoT products need to make sure they communicate properly with their firmware and cloud teams, in order to maintain good expectations. A written plan about what you’re hoping to get out of the Rev A prototype and how to maximize the testing of that prototype will ensure you don’t waste or duplicate efforts later. Design reviews are a crucial component to allow different teams to voice their needs before manufacturing.

During Rev A

Once your prototype is planned, designed, and manufactured, you need to execute on your testing plan. Your testing methods will help you to understand when a prototype has met or missed goals set during planning. This part of the talk also reviews some testing tools that can help teams get more data from their prototype device.

After Rev A

Once you have thoroughly tested your Rev A prototype, a post-mortem of what went wrong (and right) is crucial. It will ensure you improve your process (for future Rev A prototypes) and also capture all of the needed changes for a Rev B prototype.

Case Study

Golioth does not build and sell finished hardware products.  But we do regularly create “Rev A” hardware when we create different Reference Designs. These are built to help accelerate teams looking to build an end product but wouldn’t mind benefiting from someone else showing how to build the first spin of a design. Our Reference Designs are built on top of a prototyping platform we created that attempts to balance flexibility, a quasi-finished look, and a relatively compact design. None of these categories are super optimized, as that is left up to the user hoping to build a finished product.

We’re always looking for new Reference Designs to build to help accelerate engineers’ Rev A prototypes. If you have any requests or need help building out your prototype, let us know on our forum or drop us a note.

Conference Talk Slides




Come learn Zephyr with Golioth on July 12th, 2023! You will need to order your own hardware, but there is no cost to attend the live training. Sign up now so that you know you have a seat and can order a dev board with plenty of time.

Golioth’s Zephyr Training in a Nutshell

Golioth is an instant IoT Cloud for microcontroller-level devices. We are hardware agnostic, and we use Zephyr, the fastest growing RTOS, because it supports a wide range of hardware from different vendors. We have a number of customers who ask where to find Zephyr training, so we developed our own boot camp to get you started.

Nordic nRF7002-DK board

Nordic’s new nRF7002 Development Kit

This three-hour training uses your choice of the Nordic nRF7002 DK (WiFi) or nRF9160 DK (Cellular). We begin by installing the Nordic tools on your local machine for loading new firmware on the boards. Everything else happens in a browser-based container. You’ll use VS Code and the Zephyr build environment, but it’s already set up for you to start working quickly.

Two sections are presented. We first load a pre-compiled binary on the board and test out the Golioth platform features. This ensures you are able to successfully program the board, and exposes you to the Zephyr networking stack, serial shell (used to assign credentials which are loaded into non-volatile storage), and logging system. The second portion of the training provides an overview of how the Zephyr development environment works before getting hands-on with Devicetree, Kconfig, pin mapping, timers, threads, and general RTOS knowledge.

You will come away with an understanding of how a Zephyr application is formatted, how the build system works, and what to expect when your application is running on your board.

Take a Peek, then Join Us Live!

Our training is no secret, the self-guiding documentation and the sample code are both available to peruse right now. However, you’ll find the interaction with other attendees and with the Golioth staff running the training fills in a lot of knowledge that’s not so easy to print on a webpage.

Sign up

Join us Live on July 12th! Note that we also changed our signup policy: if you meet the criteria, you will be automatically enrolled into training (see form for more details). We are limited to 60 trainees, but we plan to also hold a training in August. We hope to see you there!

Fill out the signup form at https://forms.gle/3yk5WrWJ3Dunds9CA

The Golioth crew is headed to Prague next week for the Embedded Open Source Summit (EOSS). More specifically, we have a booth, are presenting several talks, and are taking meetings during the 2023 Zephyr Developer Summit (ZDS) which is one of several co-located conferences participated in EOSS.

Interested in catching up with Golioth at the conference? Drop us a line and we’ll make sure it happens!

Three Fascinating Talks from Golioth

Golioth is not only a silver member of the Zephyr Project, we heavily use Zephyr as one of our device SDKs. We’re excited to share some of our experience on the RTOS in the three talks we’re presenting.

Zephyr & Visual Studio Code: How to Develop Zephyr Apps with a Modern, Visual IDE

Golioth Developer Founder and CEO Jonathan Beri will present this talk on using Visual Studio Code with Zephyr. By default, VS Code is not optimized for embedded development, and there are many tips and tricks that we’ve learned over the years to turn it into the most power Zephyr IDE out there. Learn More »

Zephyr Onboarding in 30 Seconds – Methods and Experiments During Zephyr Training

Golioth Developer Relations Lead Chris Gammell will present this talk on setting up embedded development environments for training sessions. While it focuses on Zephyr, the same toolchain and operating system headaches exist for all embedded engineers. Chris will detail the approach to get people up and compiling Zephyr in minutes, not hours, using remote virtual machines. Learn More »

Manifests: Project Sanity in the Ever-Changing Zephyr World

Golioth Developer Relations Engineer Mike Szczys will present this talk on using the Zephyr manifest system. This is particularly important for revision control of Zephyr applications. It enshrines the state of Zephyr and all its libraries and modules so that every build begins from a known-working set of build tools. Learn More »

Say Hello at the Golioth Booth

Chris Gammell walking us through the Golioth demo hardware at 2023 Embedded World

As sponsors of EOSS, we will be demoing hardware at the Golioth Booth (#41). Stop by to say hello and see how Golioth makes building microcontroller-level IoT fleets way easier than it’s ever been before. In addition to Jonathan, Chris, and Mike mentioned above, Golioth’s new Field Application Engineer, Marko Puric, will be on hand!

Don’t forget to leave us a note if you’d like to block out some time for a meeting!

Golioth Sensors Converge

Our friends at DigiKey invited us to exhibit a hardware demo at the DigiKey booth during Sensors Converge 2023. The conference takes place in Santa Clara, California on June 20-22. Come see our demo at booth #616.

What kind of hardware makes the most sense at a DigiKey booth? All of the hardware, of course!

We’ve built a demo that shows off a fleet of three temperature sensors, all of them using microcontrollers from different manufactures, three different types of connectivity, and sensors from two different companies. Oh, did I mention that all of it runs the same C code? Readings are sent back to Golioth on a regular basis, and settings (like how often those readings occur) are configurable from the cloud. It’s shocking to think connectivity and cross-platform deployments could be this easy. But that’s what we do here at Golioth, and the Zephyr RTOS makes pretty easy.

Hardware and Firmware

Three member IoT fleet, all from different hardware vendors

The image above is what we pitched. It shows devices from Nordic, NXP, and Espressif connecting to Golioth using Cellular, Ethernet, and WiFi. They are all supported by Zephyr so adding them to the firmware project is a matter of generating one overlay file and one configuration file for each board.

You can take a look at the code in our iot_weather_fleet sample repository. All device-specific information is in the boards directory, everything else is abstracted to work with any Zephyr supported hardware (even swapping out sensors without changing the code).

Using different sensors to collect temperature readings.

Speaking of sensors, we used two different types: a Bosch BME280 and an Infineon DPS310. These both have driver support built into Zephyr. You just add your sensor to a Devicetree overlay file for the board, assign it an alias, and the RTOS does the rest. It’s truly remarkable!

Talk: Modular Hardware with Golioth and Zephyr

The concept for all of this came from a conference talk I gave earlier this year at the Embedded Online Conference. Most IoT devices are performing simple work, like sending back sensor readings. But of course the hardware design and firmware development take a lot of time and testing to get right. It should be possible to make hardware changes without rewriting the codebase when adding those changes to the firmware. And it is! We just need to embrace the concept and use it by default.

Design for the Embedded Future

The future is low power, and the future is most certainly connected. Golioth has those values at our core, making it simple to connect, control, and gather data from microcontroller-based devices en masse.

Golioth hardware being tested at DigiKey headquarters

With our Dev Tier you can connect up to 50 devices for free, so give Golioth a try today. We’d love to hear what you’re building–start a thread on the Golioth Forum to show off your work. If you have questions about how your fleet will perform with Golioth, please reach out to the Developer Relations Team and set up call.

We hope you’ll stop by the DigiKey booth this month. Here’s a sneak peek of what you’ll see!

We love going to conferences. It’s great way to meet new people and learn about interesting new areas of the IoT industry. Unfortunately, IoT-interested engineers are spread far and wide around the world. Enter the Embedded Online Conference (EOC), which helps to connect engineers in the far flung reaches of the earth. Engineers benefit from downloading new knowledge from the comfort of their homes and companies like Golioth get to meet engineers working on novel problems in the IoT space.

We are giving 3 talks at the conference this year, let’s take a look at what those are about:

Mike Szczys – Building a Modular Codebase with Zephyr RTOS and Devicetree

Developer Relations Engineer Mike Szczys is talking about one of our favorite subjects: using Zephyr for more efficient code!

If there’s one thing the chip shortage has taught us, it’s to be ready to pivot to different hardware on a short timeline. Mike has found that the Zephyr Real-Time Operating System makes this much less painful for firmware engineers. It borrows many concepts from the Linux ecosystem, delivering Devicetree, Pin Control, and Kconfig to microcontroller-land.

This talk details how to use Zephyr to maintain one codebase that can be built for many different hardware combinations. Once Kconfig and Devicetree overlay files have been created for each target, compiling the same project for Nordic, Espressif, or NXP chips (to name just a few) is simple. Changing vendors or models of sensor and other peripherals is a similar experience. The C code grabs all necessary hardware information like what pins are connected and which peripheral bus should be used for a particular build. From there it’s just a matter of changing the board name in the build command.

Dylan Swartz – Leveraging DevOps for Streamlined Firmware Delivery

One of our newest teammates, and our first product manager, Dylan Swartz is showcasing how to deploy firmware to embedded devices over the internet using modern techniques.

This talk provides a comprehensive understanding of how DevOps principles are applied to IoT development for improved efficiency and reliability. He discusses integrating firmware builds and over-the-air (OTA) updates into a continuous integration/continuous deployment (CI/CD) pipeline, resulting in increased release frequency, dependability, and quality. The presentation draws from real-world IoT projects that have successfully implemented DevOps methodologies to expedite time-to-market and enhance overall performance.

Attendees will gain practical knowledge of best practices for troubleshooting, monitoring, and scaling IoT deployments, ensuring that devices remain secure and updated throughout their life cycle. This session delivers valuable insights into implementing DevOps for IoT, equipping attendees with the tools and techniques necessary to optimize their embedded system development processes.

Chris Gammell – Improve your Embedded IoT Hardware Today

This talk is about getting more out of your “Rev A” hardware: how do you maximize the information you can generate during the expensive prototyping process?

I (Chris here) show how to add in hooks and capabilities that make troubleshooting, upgrading, and measuring deficiencies much easier. Your second rev will be leaps and bounds ahead of your first, and you can get to market faster.

This talk showcases components, tools, and troubleshooting methods that enable better hardware, regardless of the parts you choose or the form factor you need to fit into. As an example, Chris shows some recently created hardware that focused on modularity and flexbility. It was not targeted at a production environment, but forms the basis for a good “rev a” build of hardware and help engineers to focus on validating new product ideas before digging into more complex layouts and smaller form factors.

Interested in attending?

We would love to see you at the EOC this year! All the Golioth talks can be viewed by registering for free. We also have a $100 off coupon for anyone interested in full access to all talks just use the code GOLIOTH2023 when you register for the conference. We will be doing a Q&A session, as are many of the other speakers at the conference. The conference starts April 24th, 2023, but is available for the rest of the year.