<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Keil UVision on Riccardo Dal Fiume</title><link>https://dalfiume.io/tags/keil-uvision/</link><description>Recent content in Keil UVision on Riccardo Dal Fiume</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 RICCARDO DAL FIUME / DALFIUME.IO</copyright><lastBuildDate>Sun, 19 Sep 2021 21:32:59 +0200</lastBuildDate><atom:link href="https://dalfiume.io/tags/keil-uvision/index.xml" rel="self" type="application/rss+xml"/><item><title>GitLab CI/CD pipeline for Keil uVision</title><link>https://dalfiume.io/posts/gitlab-ci-cd-pipeline-for-keil-uvision/</link><pubDate>Sun, 19 Sep 2021 21:32:59 +0200</pubDate><guid>https://dalfiume.io/posts/gitlab-ci-cd-pipeline-for-keil-uvision/</guid><description>&lt;p&gt;This is a practical setup I use to build Keil uVision projects automatically with &lt;a href="https://docs.gitlab.com/ee/ci/" target="_blank" rel="noreferrer"&gt;GitLab CI/CD&lt;/a&gt;.&lt;br&gt;
The goal is simple: every commit should produce a reproducible firmware build, with logs and binaries attached as artifacts.&lt;/p&gt;
&lt;p&gt;If you work on embedded systems, this gives you fast feedback on broken builds and avoids &amp;ldquo;works on my machine&amp;rdquo; problems.&lt;/p&gt;

&lt;h2 class="relative group"&gt;Prerequisites
 &lt;div id="prerequisites" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#prerequisites" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Before creating the pipeline, ensure:&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://dalfiume.io/posts/gitlab-ci-cd-pipeline-for-keil-uvision/images/cpu-board.png"/></item></channel></rss>