<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Uart on Ampsand</title>
		<link>https://dean.sellers.id.au/tags/uart/</link>
		<description>Recent content in Uart on Ampsand</description>
		<generator>Hugo</generator>
		<language>en-AU</language>
		
		
		
			<copyright>Dean Sellers</copyright>
		
		
			<lastBuildDate>Thu, 29 Oct 2026 12:04:08 +1100</lastBuildDate>
		
			<atom:link href="https://dean.sellers.id.au/tags/uart/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>RISC-V soft core 14: Measuring the board</title>
				<link>https://dean.sellers.id.au/2026/10/27/riscv-14-measuring-the-board/</link>
				<pubDate>Tue, 27 Oct 2026 14:00:00 +1100</pubDate>
				<guid>https://dean.sellers.id.au/2026/10/27/riscv-14-measuring-the-board/</guid>
				<description>&lt;p class=&#34;post-subtitle&#34;&gt;Measuring the board&lt;/p&gt;&lt;p&gt;&lt;em&gt;Part 14 of the RISC-V soft core series. Previously: &lt;a href=&#34;https://dean.sellers.id.au/2026/10/23/riscv-13-the-board-arrives/&#34;&gt;The board arrives&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;Part 13 ended with a list of things only the board can tell me. This part is the list I could get to: a scope on three signals, and a lot of bytes down the serial port. This might be the first part with no surprises, or a bunch of &lt;em&gt;that&amp;rsquo;s what I thought&lt;/em&gt; bits.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ll say up front what is &lt;em&gt;not&lt;/em&gt; here. I haven&amp;rsquo;t shown that the core meets 25 MHz on every path, and I haven&amp;rsquo;t looked at button bounce or the 7-segment flicker. Those are still to do, and maybe I will. This isn&amp;rsquo;t going to production, and with the signals I scoped and the serial soaks behind me I am fairly confident that what is supposed to happen is happening. As we know though &amp;hellip; there are always edges.&lt;/p&gt;</description>
			</item>
			<item>
				<title>RISC-V soft core 4: Talking to the world</title>
				<link>https://dean.sellers.id.au/2026/10/19/riscv-04-talking-to-the-world/</link>
				<pubDate>Mon, 19 Oct 2026 00:05:00 +1100</pubDate>
				<guid>https://dean.sellers.id.au/2026/10/19/riscv-04-talking-to-the-world/</guid>
				<description>&lt;p class=&#34;post-subtitle&#34;&gt;Talking to the world: loads, stores and a boot menu&lt;/p&gt;&lt;p&gt;&lt;em&gt;Part 4 of the RISC-V soft core series. Previously: &lt;a href=&#34;https://dean.sellers.id.au/2026/10/18/riscv-03-von-neumann-by-choice/&#34;&gt;Harvard by accident, von Neumann by choice&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;So far the core can add, branch, load, store and light some LEDs. It cannot tell me anything. For that it needs a way to talk, and RISC-V gives you a surprisingly short answer about how: it has &lt;strong&gt;no input and output instructions at all&lt;/strong&gt;. There is no &lt;code&gt;IN&lt;/code&gt; and no &lt;code&gt;OUT&lt;/code&gt;, as on an x86. The way you reach a device is the way you reach memory, with a load or a store to a particular address.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
