Embedded Perspectives
ci-cd
6 articles tagged with ci-cd.
Arm User-Based Licensing in CI/CD: armlm, Proxy Activation and What Breaks
A licensing failure in an Arm pipeline blocks the release branch and puts a firmware engineer on armlm output instead of driver code, up to seven days after the change that caused it. The reason: a UBL licence is a cached certificate valid for 7 days, not a checkout. Here is what that changes about pipeline design, and what to fix first.
Saleae Python API for CI/CD: Capturing Protocol Traces in GitHub Actions
The Logic 2 Automation API drives Saleae devices from Python. Here's how Indian embedded teams wire it into a GitHub Actions or GitLab CI workflow for nightly hardware-in-the-loop regression on a bench Raspberry Pi.
How Many Arm UBL Seats Do You Actually Need?: A Sizing Guide for Indian CI/CD Teams
How Arm User-Based Licensing actually sizes against your team: per developer identity, not per parallel CI job. A short guide for Indian engineering managers planning the UBL migration, talk to GSAS for the per-team sizing exercise.
Cortex-M CI/CD with csolution.yml + cbuild + GitHub Actions: A Working Pipeline for Indian Firmware Teams
A concrete CI/CD pipeline pattern for Indian Cortex-M firmware teams using the modern Arm CMSIS-Toolbox CLI (csolution + cbuild + cpackget) on GitHub Actions runners, UBL-licensed builds, vcpkg tool deployment, parallel build matrix, and the firewall + caching gotchas that catch most teams.
SEGGER Embedded Studio CMake Integration for Indian DevOps and CI Pipelines
How Indian embedded teams bridge bench-side IDE development with headless Linux CI runners using SEGGER Embedded Studio's CMake import/export and emBuild command line.
J-Link Commander CLI Scripting for Indian Production Lines and CI Test Rigs
How Indian EMS production lines and CI hardware-in-the-loop rigs drive J-Link probes headlessly using JLinkExe, JLinkGDBServer, JLinkRTTLogger, and J-Link Remote Server.