<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[wolfSSL - Embedded SSL Library — Compile WolfBoot with a custom hardware initialization via CMake]]></title>
		<link>https://www.wolfssl.com/forums/topic2436-compile-wolfboot-with-a-custom-hardware-initialization-via-cmake.html</link>
		<atom:link href="https://www.wolfssl.com/forums/feed-rss-topic2436.xml" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Compile WolfBoot with a custom hardware initialization via CMake.]]></description>
		<lastBuildDate>Thu, 11 Dec 2025 12:55:32 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Compile WolfBoot with a custom hardware initialization via CMake]]></title>
			<link>https://www.wolfssl.com/forums/post8644.html#p8644</link>
			<description><![CDATA[<p>Hello mallenbach,</p><p>The initialization code for your hardware should be added into your custom hal_init(), which is part of the HAL interface you should provide for wolfBoot to interact with your hardware: <br /><a href="https://github.com/wolfSSL/wolfBoot/blob/master/docs/HAL.md">https://github.com/wolfSSL/wolfBoot/blo … ocs/HAL.md</a><br />wolfBoot will call the function at startup.</p><p>If you rather prefer to integrate wolfBoot functionality into an existing bootloader, then you should check the section &quot;Build wolfBoot as Library&quot;: <a href="https://github.com/wolfSSL/wolfBoot/blob/master/docs/lib.md">https://github.com/wolfSSL/wolfBoot/blo … ocs/lib.md</a></p><p>Thanks,</p><p>-- <br />Daniele</p>]]></description>
			<author><![CDATA[null@example.com (danielinux)]]></author>
			<pubDate>Thu, 11 Dec 2025 12:55:32 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post8644.html#p8644</guid>
		</item>
		<item>
			<title><![CDATA[Re: Compile WolfBoot with a custom hardware initialization via CMake]]></title>
			<link>https://www.wolfssl.com/forums/post8642.html#p8642</link>
			<description><![CDATA[<p>Hello Eric and team,</p><div class="quotebox"><blockquote><p>I am looping in a colleague to help with your question.</p></blockquote></div><p>Do you have an ETA regarding this request? We are currently evaluating different solutions and CMake support is key.</p><p>Thanks!</p>]]></description>
			<author><![CDATA[null@example.com (mallenbach)]]></author>
			<pubDate>Thu, 11 Dec 2025 08:41:51 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post8642.html#p8642</guid>
		</item>
		<item>
			<title><![CDATA[Re: Compile WolfBoot with a custom hardware initialization via CMake]]></title>
			<link>https://www.wolfssl.com/forums/post8637.html#p8637</link>
			<description><![CDATA[<p>Hello Eric - thanks for your quick answer!</p><p>I am based in Paris area (France).</p><p>The project I am working on is an application running on a STM32F4 that aims at controlling (ON / OFF / RESET) a battery-powered power supply with some telemetry. Since this is remotely operated, I am looking for a safe way to perform FUOTA and integrity checks.</p><p>I am trying to understand if the CMake integration done in WolfBoot is mature and can easily be integrated in another project to do some &quot;extensions&quot; like this custom hardware integration.</p><p>Thanks.</p>]]></description>
			<author><![CDATA[null@example.com (mallenbach)]]></author>
			<pubDate>Mon, 08 Dec 2025 14:36:13 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post8637.html#p8637</guid>
		</item>
		<item>
			<title><![CDATA[Re: Compile WolfBoot with a custom hardware initialization via CMake]]></title>
			<link>https://www.wolfssl.com/forums/post8636.html#p8636</link>
			<description><![CDATA[<p>Hello mallenbach,</p><p>Welcome to the wolfSSL Forums!</p><p>Thanks for reaching out. Could you tell us a bit about your wolfBoot project and where you are located for our support statistics?</p><p>I am looping in a colleague to help with your question.</p><p>Kind regards,<br />Eric - wolfSSL Support</p>]]></description>
			<author><![CDATA[null@example.com (embhorn)]]></author>
			<pubDate>Mon, 08 Dec 2025 14:31:47 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post8636.html#p8636</guid>
		</item>
		<item>
			<title><![CDATA[Compile WolfBoot with a custom hardware initialization via CMake]]></title>
			<link>https://www.wolfssl.com/forums/post8635.html#p8635</link>
			<description><![CDATA[<p>Hello!</p><p>I would like to compile with CMake a bootloader that looks as below:</p><p>my-wolfboot-project/<br />├─ CMakeLists.txt<br />├─ src/<br />│&nbsp; ├─ main.c&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;# Your custom entry point<br />│&nbsp; └─ hw_init.c&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # Optional hardware setup<br />├─ include/<br />│&nbsp; └─ hw_init.h<br />└─ wolfboot/&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;# WolfBoot source (submodule or copy)<br />&nbsp; &nbsp;├─ ... (wolfBoot sources)</p><p>In main.c, I&#039;ll have a main function that performs some specific hardware configuration (GPIO, etc.) to then call &quot;loader_main&quot; and let Wolfboot does its magic.</p><p>I cannot find a place in the documentation where this case is described. I do not understant if I need to include Wolfboot sources or link against a static library.</p><p>Does anyone has some experience regarding this approach?</p><p>Thanks!</p>]]></description>
			<author><![CDATA[null@example.com (mallenbach)]]></author>
			<pubDate>Mon, 08 Dec 2025 14:24:23 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post8635.html#p8635</guid>
		</item>
	</channel>
</rss>
