<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Posts on Maquefel's Stash</title><link>https://maquefel.me/en/posts/</link><description>Recent content in Posts on Maquefel's Stash</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 11 Jan 2022 07:42:27 +0000</lastBuildDate><atom:link href="https://maquefel.me/en/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Don’t fear the bricking (unbricking Unmatched via JTAG)</title><link>https://maquefel.me/en/dont-fear-the-bricking-unbricking-unmatched-via-jtag/</link><pubDate>Tue, 11 Jan 2022 07:41:50 +0000</pubDate><guid>https://maquefel.me/en/dont-fear-the-bricking-unbricking-unmatched-via-jtag/</guid><description>&lt;p>First published at: &lt;a href="https://forums.sifive.com/t/dont-fear-the-bricking-unbricking-unmatched-via-jtag/5449">https://forums.sifive.com/t/dont-fear-the-bricking-unbricking-unmatched-via-jtag/5449&lt;/a>&lt;/p>
&lt;p>Despite, as i think, this is quite obvious, some people miss the point.&lt;/p>
&lt;p>So let me show you how to unbrick the HiFive Unmatched board, that&amp;rsquo;s usefull in case of:&lt;/p>
&lt;ul>
&lt;li>installing BSP without the need of preparing the SD card in advance (you still have to insert it through)&lt;/li>
&lt;li>unbricking the board in case of deleting U-Boot&lt;/li>
&lt;li>testing U-Boot + OpenSBI on fly hijacking the load addresses&lt;/li>
&lt;/ul>
&lt;p>The scheme works independently of selected MSEL value.&lt;/p></description></item><item><title>Using gpio-generic and irq_chip_generic subsystems for gpio driver</title><link>https://maquefel.me/en/using-gpio-generic-and-irq_chip_generic-subsystems-for-gpio-driver/</link><pubDate>Sat, 10 Sep 2016 12:31:52 +0000</pubDate><guid>https://maquefel.me/en/using-gpio-generic-and-irq_chip_generic-subsystems-for-gpio-driver/</guid><description>&lt;h1 id="intoduction">Intoduction&lt;/h1>
&lt;p>This article is a logical continuation of the previous one and it is recommended to stady after reading the &lt;a href="https://maquefel.me/en/qemu-ivshmem-introducing-interrupt-capable-virtual-gpio-concept/">previous material&lt;/a>. The current note is necessary for understanding the subsequent material, a further understanding gpio subsystem as a whole and helps with the development of own gpio drivers. The provisions of this article have not only apply to our virtual driver gpio, but also to any mmio gpio driver in general. It will focus on &amp;ldquo;optimizing&amp;rdquo; referred to in the preceding article.&lt;/p></description></item><item><title>QEMU ivshmem Introducing interrupt capable virtual gpio concept</title><link>https://maquefel.me/en/qemu-ivshmem-introducing-interrupt-capable-virtual-gpio-concept/</link><pubDate>Thu, 14 Jul 2016 12:21:27 +0000</pubDate><guid>https://maquefel.me/en/qemu-ivshmem-introducing-interrupt-capable-virtual-gpio-concept/</guid><description>&lt;h1 id="introduction">Introduction&lt;/h1>
&lt;p>&lt;img loading="lazy" src="https://maquefel.me/en/qemu-ivshmem-introducing-interrupt-capable-virtual-gpio-concept/77860c29e6024e7e818a102b55319904.jpg">&lt;/p>
&lt;p>It&amp;rsquo;s hard to underestimate the role of GPIO&amp;rsquo;s, especially in ARM embedded systems. Apart of being a very popular material for starters, GPIO&amp;rsquo;s provide a way for controlling the many peripheral devices, act as source of valuable interrupts, or even can be the only way to communicate the world for a SOC.&lt;/p></description></item></channel></rss>