<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Zig Embedded</title>
		<link>https://zig-embedded.org/</link>
		<description>My journey into Embedded Software Development</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 26 Oct 2026 22:18:58 +0100</lastBuildDate>
		
			<atom:link href="https://zig-embedded.org/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Resources for NUCLEO-F401RE</title>
				<link>https://zig-embedded.org/blog/2/resources-for-nucleo-f401re/</link>
				<pubDate>Mon, 26 Oct 2026 22:18:58 +0100</pubDate>
				<guid>https://zig-embedded.org/blog/2/resources-for-nucleo-f401re/</guid>
				<description><![CDATA[<p>I was looking for documentation for my NUCLEO-F401RE board.</p>
<p><a href="https://www.st.com/en/evaluation-tools/nucleo-f401re.html#documentation">Here</a>
is the documentation page for that board.
You can find the
<a href="https://www.st.com/resource/en/user_manual/um1724-stm32-nucleo64-boards-mb1136-stmicroelectronics.pdf">User Manual</a>
and CAD resources there.</p>
<p>You can also download their programming tools there, but I try not to use those.
Instead, I will use the <a href="https://developer.arm.com/tools-and-software/gnu-toolchain">GNU toolchain</a>.</p>
<p>I&rsquo;m not sure if I will use this directly, but here are the links for the
CMSIS headers for the
<a href="https://github.com/STMicroelectronics/cmsis-device-f4/blob/master/Include/stm32f4xx.h">F4 chip</a>.
Those device-specific headers depend on the Arm core headers, such as <a href="https://github.com/ARM-software/CMSIS_5/blob/develop/CMSIS/Core/Include/core_cm4.h">CMSIS 5</a> or the latest <a href="https://github.com/ARM-software/CMSIS_6/blob/main/CMSIS/Core/Include/core_cm4.h">CMSIS 6</a>.</p>
<p>CMSIS stands for <em>Cortex Microcontroller Software Interface Standard</em>.
They provide a standard set of definitions for the underlying hardware.</p>
<p>More details about the chip itself are found in the
<a href="https://www.st.com/resource/en/datasheet/stm32f401re.pdf">datasheet</a>
and
<a href="https://www.st.com/resource/en/reference_manual/rm0368-stm32f401xbc-and-stm32f401xde-advanced-armbased-32bit-mcus-stmicroelectronics.pdf">reference manual</a>.</p>
]]></description>
			</item>
			<item>
				<title>Starting Embedded</title>
				<link>https://zig-embedded.org/blog/1/starting-embedded/</link>
				<pubDate>Fri, 23 Oct 2026 22:09:27 +0100</pubDate>
				<guid>https://zig-embedded.org/blog/1/starting-embedded/</guid>
				<description><![CDATA[<p>Hi,</p>
<p>My name is Roeland.</p>
<p>After developing custom small-business software for 25 years,
it is time for something new. I am going to learn embedded software engineering.</p>
<p>I have a bachelor&rsquo;s degree in electrical engineering (specializing in
electronics) from 25 years ago, but I have forgotten most of it.
I mostly just remember a diode bridge, because that was drilled into us
during my final year.</p>
<p>I have also never really used low-level languages like C or Zig.
This will be the start of my learning journey, which I will share here.
I will start with C, but Zig seems like a great long-term choice since it
improves on C. For hardware, I bought an STM32 Nucleo board
(NUCLEO-F401RE, €24).
My ultimate goal is to write embedded software in Zig, using open-source
tools as much as possible.</p>
<p>It may take a while to get there. As a first step, I ordered the book <em>Making
Embedded Systems</em> by Elecia White (no affiliation). I am not sure if it is the best place to
start, but I saw it recommended online multiple times.</p>
<p>Wish me luck&hellip; I will need it!</p>
<p>You can email me at <a href="mailto:me@roeland.xyz">me@roeland.xyz</a> if you would like to share
feedback or suggestions.</p>
]]></description>
			</item>
	</channel>
</rss>
