<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Pier-Yves Lessard Blog on EmbeddedRelated.com</title>
<link>https://www.embeddedrelated.com/blogs-1/nf/Pier-Yves_Lessard.php</link>
<description><![CDATA[RSS Feed for Pier-Yves Lessard Blog on EmbeddedRelated.com]]></description>
<image><title>Pier-Yves Lessard Blog on EmbeddedRelated.com</title>
<link>https://www.embeddedrelated.com/blogs-1/nf/Pier-Yves_Lessard.php</link>
<url>https://d23s79tivgl8me.cloudfront.net/user/profilepictures/146802.jpg</url>
</image>
<atom:link href="https://www.embeddedrelated.com/blogs_rss.php?bloggerid=146802" rel="self" type="application/rss+xml"></atom:link>
<language>en-US</language>
<lastBuildDate>Wed, 22 Apr 2026 00:19:42 +0000</lastBuildDate>
<pubDate>1776817182</pubDate>
<item>
<title>Debug, visualize and test embedded C/C++ through instrumentation</title>
<link>https://www.embeddedrelated.com/showarticle/1781.php</link>
<description><![CDATA[A Short Introduction
<p>
	Classical embedded debugging requires a debug probe that can access the internal memory bus and registers through a debug port, such as JTAG or SWD. For several reasons, the classical approach can sometime be painful. You may be locked to a vendor specific debug probe, or the probe may be costly, the software stack to use can be complex or awkward to use. Additionally,...]]></description>
<pubDate>Wed, 25 Mar 2026 01:34:16 +0000</pubDate>
<author>Pier-Yves Lessard</author>
</item>
</channel>
</rss>