<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fpga on Arthur's blog</title><link>https://blog.aheymans.xyz/tags/fpga/</link><description>Recent content in Fpga on Arthur's blog</description><generator>Hugo</generator><language>en</language><copyright>Copyright © 2018–2024, Arthur Heymans; all rights reserved.</copyright><lastBuildDate>Mon, 20 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.aheymans.xyz/tags/fpga/index.xml" rel="self" type="application/rss+xml"/><item><title>NORbert: chasing a ground bounce through the quad I/O address phase</title><link>https://blog.aheymans.xyz/post/cs_debounce_ft4222/</link><pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.aheymans.xyz/post/cs_debounce_ft4222/</guid><description>&lt;p>
Found a weird bug in &lt;a href="https://github.com/ArthurHeymans/NORbert">NORbert&lt;/a> last week. Quad I/O reads (0xEB, the 1-4-4 mode) driven by an FT4222 would silently return 0xFF at specific SPI clock frequencies. 1-1-1, 1-1-2, 1-2-2 and 1-1-4 all worked fine. 10, 15 and 20 MHz failed; 12 and 30 MHz worked. Same data, same emulator, only the SPI clock changed.&lt;/p>
&lt;p>
Peak &amp;#34;this is supposed to be the fun hobby project&amp;#34; energy.&lt;/p>
&lt;div id="outline-container-headline-1" class="outline-2">
&lt;h2 id="headline-1">
The symptom
&lt;/h2>
&lt;div id="outline-text-headline-1" class="outline-text-2">
&lt;p>
Flashprog verify run at 10 MHz, quad mode:&lt;/p></description></item></channel></rss>