<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Wired &amp;&amp; Coded;</title>
    <link>http://localhost:1313/</link>
    <description>Recent content on Wired &amp;&amp; Coded;</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 09 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="http://localhost:1313/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Chatting with Schematic: Evaluation of LLMs&#39; Know-How in Electronics</title>
      <link>http://localhost:1313/posts/2026/2026-04-09-chatting-with-schematic-evaluation-of-llms-know-how-in-electronics/</link>
      <pubDate>Thu, 09 Apr 2026 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2026/2026-04-09-chatting-with-schematic-evaluation-of-llms-know-how-in-electronics/</guid>
      <description>&lt;p&gt;This article evaluates the proficiency of 11 contemporary Large Language Models (LLMs) in performing electronic circuit analysis.&lt;/p&gt;&#xA;&lt;p&gt;Utilizing &lt;strong&gt;OpenCode&lt;/strong&gt;, an open-source agentic framework, the LLMs are tasked with analyzing a clock generator’s resistor-capacitor (RC) network defined in a &lt;strong&gt;KiCad 9.0&lt;/strong&gt; schematic. To facilitate LLMs&amp;rsquo; comprehension, an efficient preprocessing methodology is introduced to convert schematic data into structured &lt;strong&gt;CSV formats&lt;/strong&gt;. The evaluation requires the models to parse circuit netlists, retrieve specifications from component datasheets available in the workspace, and calculate the critical circuit parameters, specifically the &lt;strong&gt;common-mode voltage&lt;/strong&gt; and &lt;strong&gt;differential swing&lt;/strong&gt; of the clock output.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Test-Board from PCBWAY has Arrived!</title>
      <link>http://localhost:1313/posts/2026/2026-02-20-test-board-from-pcbway-has-arrived/</link>
      <pubDate>Fri, 20 Feb 2026 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2026/2026-02-20-test-board-from-pcbway-has-arrived/</guid>
      <description>&lt;p&gt;Some days ago I &lt;a href=&#34;https://www.jsykora.info/2026/02/agila-and-her-test-board/&#34;&gt;ordered a testing PCB from PCBWAY&lt;/a&gt;, and today the package has arrived!&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/wp-content/uploads/2026/02/image-8.png&#34;&gt;&lt;img src=&#34;images/image-8-1024x730.png&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/wp-content/uploads/2026/01/pcbway.png&#34;&gt;&lt;img src=&#34;images/pcbway.png&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;FRONT&lt;/strong&gt;:&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/wp-content/uploads/2026/02/image-11.png&#34;&gt;&lt;img src=&#34;images/image-11.png&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;BACK&lt;/strong&gt;:&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/wp-content/uploads/2026/02/image-12.png&#34;&gt;&lt;img src=&#34;images/image-12.png&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;As discussed in the previous article, this is a test-board for the future PCIe card with Agilex 3 FPGA. But presently - no FPGA. The board combines several power supplies (dc/dc converters), clock generator with level shifters, reset, and USB-JTAG:&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/wp-content/uploads/2026/01/her-testboard-render-annotated.drawio.png&#34;&gt;&lt;img src=&#34;images/her-testboard-render-annotated.drawio.png&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Practical AI in HW Development: Importing BGA Pad-to-Die Lengths from Excel to Kicad Footprint</title>
      <link>http://localhost:1313/posts/2026/2026-02-14-ai-llm-in-hw-development-importin-bga-pad-to-die-lengths-from-excel-to-kicad-footprint/</link>
      <pubDate>Sat, 14 Feb 2026 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2026/2026-02-14-ai-llm-in-hw-development-importin-bga-pad-to-die-lengths-from-excel-to-kicad-footprint/</guid>
      <description>&lt;p&gt;In hardware design, tedious manual data entry is a common bottleneck. I recently explored how the &amp;lsquo;AI revolution&amp;rsquo; - specifically LLMs and GitHub Copilot - could automate a specific, repetitive task: importing BGA pad-to-die lengths into KiCad 9. The input Excel table, downloaded from Altera site, has around 270 rows, so the motivation to &lt;em&gt;not do&lt;/em&gt; the import by manually entering numbers into software was pretty high.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-is-the-pad-to-die-length&#34;&gt;What is the Pad-to-Die Length&lt;/h2&gt;&#xA;&lt;p&gt;The picture bellow shows a cross section of a typical integrated chip in a BGA package. Balls at the bottom are soldered to the PCB, while the actual IC silicon die is much smaller and sits on a ceramic substrate. The substrate acts as an intermediary routing layer, connecting the silicon die to the BGA balls. The traces between balls to the die are not the same length. The &lt;em&gt;pad-to-die length&lt;/em&gt;, or &lt;em&gt;package length,&lt;/em&gt; is the length of the internal trace in the package; it is different for every pad or ball (unless the IC designer takes care to do the package delay matching).&lt;/p&gt;</description>
    </item>
    <item>
      <title>AGILA, and Her Test-board</title>
      <link>http://localhost:1313/posts/2026/2026-02-03-agila-and-her-test-board/</link>
      <pubDate>Tue, 03 Feb 2026 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2026/2026-02-03-agila-and-her-test-board/</guid>
      <description>&lt;p&gt;&lt;strong&gt;&lt;em&gt;AGILA&lt;/em&gt;&lt;/strong&gt; will be a new open-source board with the &lt;strong&gt;Altera Agilex 3 FPGA&lt;/strong&gt;, &lt;strong&gt;2 GB to 8 GB&lt;br&gt;&#xA;of LPDDR4 RAM&lt;/strong&gt; and the &lt;strong&gt;PCI-Express interface&lt;/strong&gt;. The Agilex 3 FPGA includes hard-IP support for PCI- Express interface up to Gen3 x4 and the LPDDR4 x32 up to 1066MHz (2133MT/s). The board form factor will be a low-profile PCI-Express card with the x4 edge connector. The upper edge of the board will be occupied by extension pin-header connectors. The board will also include a JTAG port and USB/JTAG interface for easy HDL development.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Powering the Agilex 3 FPGA</title>
      <link>http://localhost:1313/posts/2025/2025-12-05-powering-the-agilex-3-fpga/</link>
      <pubDate>Fri, 05 Dec 2025 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2025/2025-12-05-powering-the-agilex-3-fpga/</guid>
      <description>&lt;p&gt;The picture below is an extract from Power-Supply Block Diagram of the official Agilex 3 Devkit. The FPGA requires multiple power supply levels: from 0.75V to 3.3V. Specification is found in altera document &lt;a href=&#34;https://www.intel.com/content/www/us/en/docs/programmable/846855/current/power-management-overview.html&#34;&gt;Power Management User Guide: Agilex™ 3 FPGAs and SoCs&lt;/a&gt; and details for particular device in &lt;a href=&#34;https://www.intel.com/content/www/us/en/docs/programmable/848370/current/agilex-3-fpgas-and-socs-device-data-sheet.html&#34;&gt;Agilex™ 3 FPGAs and SoCs Device Data Sheet&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/wp-content/uploads/2025/12/image-4.png&#34;&gt;&lt;img src=&#34;images/image-4.png&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;minimum-set-of-power-levels&#34;&gt;Minimum Set of Power Levels&lt;/h2&gt;&#xA;&lt;p&gt;This is the list of mandatory power supply levels needed for the Agilex 3 FPGA:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Clocking the Agilex 3 FPGA</title>
      <link>http://localhost:1313/posts/2025/2025-12-03-clocking-the-agilex-3-fpga/</link>
      <pubDate>Wed, 03 Dec 2025 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2025/2025-12-03-clocking-the-agilex-3-fpga/</guid>
      <description>&lt;p&gt;Theoretically, Agilex 3 FPGA does not require any external clock signals to load bitstream and to operate an (asynchronous) user design. However, in practice, all designs will need to supply some clock signals for use in EMIF (e.g. LPDDR4) or GTS (e.g. PCIe) and other integrated IP. To be specific in this post, we focus on clocking scheme of the Agilex 3 Devkit board (block diagram pictured below).&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/wp-content/uploads/2025/11/DevkitAg3-Clocking-blockdiagram.png&#34;&gt;&lt;img src=&#34;images/DevkitAg3-Clocking-blockdiagram.png&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;secure-device-manager-sdm&#34;&gt;Secure Device Manager (SDM)&lt;/h2&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/2025/11/bitstream-loading-in-agilex-3-fpga/&#34;&gt;Secure Device Manager (SDM)&lt;/a&gt; is responsible for booting the FPGA: loading of bitstream (typically from QSPI-Flash), array configuration and HPS boot. Although the SDM can operate from an internal free-running clock, an &lt;strong&gt;external&lt;/strong&gt; (more stable) clock is necessary in case the design is using EMIF (LPDDR4) or GTS (PCIe). The external clock should be 25MHz, or 100MHz or 125MHz at 1.8V-level single-ended LVCMOS and must be fed into the dedicated pin OSC_CLK_1 (AG11). The expected frequency is pre-configured in the header part of the bitream (bitstream header, up to 512kB, is always loaded with internal clock, but the rest of the loading/booting process is configurable in the header). In case of the Agilex 3 Devkit design the 100MHz clock for SDM is generated in a dedicated external oscillator &lt;a href=&#34;https://cz.mouser.com/datasheet/3/564/1/si510_11.pdf&#34;&gt;Skyworks 510KBB100M000CAG&lt;/a&gt; (&lt;a href=&#34;https://cz.mouser.com/ProductDetail/Skyworks-Solutions-Inc/510KBB100M000CAG?qs=7%2F6SraaimPQyJWMiK7wAKQ%3D%3D&#34;&gt;Mouser&lt;/a&gt;).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Keep Thinking</title>
      <link>http://localhost:1313/posts/2025/2025-12-01-keep-thinking/</link>
      <pubDate>Mon, 01 Dec 2025 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2025/2025-12-01-keep-thinking/</guid>
      <description>&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;**What the local company manager expects:   **   1. Make all developers use gen-AI tools for coding   2. Expect productivity increase   3. Profit!!&lt;/th&gt;&#xA;          &lt;th&gt;&lt;strong&gt;What the AI-tooling company plans:&lt;/strong&gt;      1. Make all developers use gen-AI tools for coding   2. When most are dependent, decrease the quality and increase the price   3. Profit!!&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;**What a developer should do:   **   1. Keep thinking   2. When company starts complaining how costly the AI-tools are becoming, point out that you can deliver consistent quality at a pre-agreed price, and suggest salary increase   3. Profit!!&lt;/td&gt;&#xA;          &lt;td&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;</description>
    </item>
    <item>
      <title>Bitstream Loading in Agilex 3 FPGA</title>
      <link>http://localhost:1313/posts/2025/2025-11-23-bitstream-loading-in-agilex-3-fpga/</link>
      <pubDate>Sun, 23 Nov 2025 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2025/2025-11-23-bitstream-loading-in-agilex-3-fpga/</guid>
      <description>&lt;p&gt;Agilex 3 FPGA supports loading of the configuration bitstream by multiple methods. A method is selected by 3 strapping pins &lt;a href=&#34;https://www.intel.com/content/www/us/en/docs/programmable/847422/25-1/msel-settings.html&#34;&gt;MSEL[2:0]&lt;/a&gt; (these are multi-purpose strapping pins). The common methods are:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;MSEL[2:0]=111 =&amp;gt; wait for JTAG download,&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;MSEL[2:0]=011 =&amp;gt; normal QSPI Flash download mode&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;MSEL[2:0]=001 =&amp;gt; &amp;ldquo;fast&amp;rdquo; QSPI Flash download mode - this just skips a 10ms wait before accessing QSPI flash which is normally part of the normal QSPI flash download mode. This could help with PCIe link-up requirements, but the design must ensure that the QSPI device is ready.&lt;/p&gt;</description>
    </item>
    <item>
      <title>GTS Transceivers with PCI-Express hard-IP in Agilex 3</title>
      <link>http://localhost:1313/posts/2025/2025-11-19-gts-transceivers-with-pci-express-hard-ip-in-agilex-3/</link>
      <pubDate>Wed, 19 Nov 2025 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2025/2025-11-19-gts-transceivers-with-pci-express-hard-ip-in-agilex-3/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://www.intel.com/content/www/us/en/docs/programmable/848344/25-1/gts-transceiver-overview.html&#34;&gt;Agilex 3&lt;/a&gt; FPGA supports PCI-Express via its four &lt;a href=&#34;https://www.intel.com/content/www/us/en/docs/programmable/848344/25-1/gts-transceiver-overview.html&#34;&gt;GTS transceiver links&lt;/a&gt;. Each GTS physical link (tx+rx) supports up to 12.5Gbps transfer speed. On top of the GTS transceivers the FPGA implements hardened IPs for PCI-Express 3.0 x1-x2-x4, Ethernet 10 Gbe link, and USB 3.0 (only with HPS).&lt;/p&gt;&#xA;&lt;h2 id=&#34;available-pci-express-throughput&#34;&gt;Available PCI-Express Throughput&lt;/h2&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://en.wikipedia.org/wiki/PCI_Express&#34;&gt;PCI-Express&lt;/a&gt; speed is specified in generations: from 1.0 to 8.0 (planned in 2028), and in port width: from x1 to x16. The table below, copied from wikipedia, shows the expected throughput for the given generation and port width:&lt;/p&gt;</description>
    </item>
    <item>
      <title>LPDDR4 in Agilex 3 FPGA</title>
      <link>http://localhost:1313/posts/2025/2025-11-16-lpddr4-in-agilex-3-fpga/</link>
      <pubDate>Sun, 16 Nov 2025 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2025/2025-11-16-lpddr4-in-agilex-3-fpga/</guid>
      <description>&lt;p&gt;Presently (2025) there are two perspective busses for connecting DRAM devices in &lt;em&gt;embedded&lt;/em&gt; systems:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;DDR3L&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;LPDDR4 (and its lower-power variant LPDDR4X)&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The DDR3L supports traditional DDR multidrop bus topology with VTT termination and multiple memory devices sharing the address/control bus. The LPDDR4 is a completely different protocol and allows just a single memory device attached to the controller, with the advantage that external termination not required (saving board space and power).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Could we design an FPGA-based compute accelerator on an M.2 card?</title>
      <link>http://localhost:1313/posts/2025/2025-11-09-could-we-design-an-fpga-based-compute-accelerator-on-an-m-2-card/</link>
      <pubDate>Sun, 09 Nov 2025 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2025/2025-11-09-could-we-design-an-fpga-based-compute-accelerator-on-an-m-2-card/</guid>
      <description>&lt;p&gt;Ever since I attended the &lt;a href=&#34;https://www.jsykora.info/2025/11/axc3000-agilex-fpga-starter-kit/&#34;&gt;Altera FPGA workshMicronop featuring their new Agilex 3 device,&lt;/a&gt; I am thinking if Agilex could be the right FPGA to implement a general-purpose computation accelerator (i.e. a GPU) with a fast PCI-Express interface and a significant amount of DDR DRAM memory.&lt;/p&gt;&#xA;&lt;p&gt;The following features of Agilex 3 FPGAs are notable in the context:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;100k to 135k logic elements in the two largest variants&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;affordable cost of a device around 130 USD/piece&lt;/p&gt;</description>
    </item>
    <item>
      <title>AXC3000: Agilex FPGA Starter Kit</title>
      <link>http://localhost:1313/posts/2025/2025-11-05-axc3000-agilex-fpga-starter-kit/</link>
      <pubDate>Wed, 05 Nov 2025 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2025/2025-11-05-axc3000-agilex-fpga-starter-kit/</guid>
      <description>&lt;p&gt;Recently I attended &lt;strong&gt;Arrow&amp;rsquo;s Agilex 3 FPGA&lt;/strong&gt; workshop, which promoted, obviously, the new &lt;strong&gt;&lt;a href=&#34;https://www.altera.com/products/fpga/agilex/3&#34;&gt;Altera Agilex 3&lt;/a&gt;&lt;/strong&gt; FPGAs. In the workshop we completed lab tasks using also the new &lt;a href=&#34;https://www.arrow.com/en/products/axc3000/trenz-electronic-gmbh&#34;&gt;AXC3000 Starter Kit&lt;/a&gt; that features the Agilex 3 FPGA. At the end of the day there was a quiz and so I happened to win one the AXC3000 boards for myself. In this article I present my first-look analysis of the board.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/wp-content/uploads/2025/11/axc3000-top-scaled-1.jpg&#34;&gt;&lt;img src=&#34;images/axc3000-top-scaled-1.jpg&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Beware of Non-Legit Indiegogo Campaigns</title>
      <link>http://localhost:1313/posts/2025/2025-01-05-beware-of-non-legit-indiegogo-campaigns/</link>
      <pubDate>Sun, 05 Jan 2025 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2025/2025-01-05-beware-of-non-legit-indiegogo-campaigns/</guid>
      <description>&lt;p&gt;There is an ongoing Indiegogo campaign called &amp;ldquo;&lt;em&gt;X65GS 65816 Gaming Console&lt;/em&gt;&amp;rdquo;, see screenshot below.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;I - as the creator of the x65 project - do not support and do not endorse this campaign&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;In the campaign page they reused my own &amp;lsquo;amateur&amp;rsquo; photos of that one x65-sbc device, which is right now on my work-desk at home. IT MEANS: &lt;em&gt;&lt;strong&gt;they do not have the capacity or knowledge to produce own replicas of the x65-sbc computer for testing and marketing purposes&lt;/strong&gt;, yet they have the guts to request money from unsuspecting customers!&lt;/em&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>New x65 Debugger in the textual Framework</title>
      <link>http://localhost:1313/posts/2025/2025-01-03-new-x65-debugger-in-the-textual-framework/</link>
      <pubDate>Fri, 03 Jan 2025 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2025/2025-01-03-new-x65-debugger-in-the-textual-framework/</guid>
      <description>&lt;p&gt;I started a new debugger tool for my &lt;a href=&#34;http://localhost:1313/x65-8-16-bit-computer/&#34;&gt;x65&lt;/a&gt; project. Previously I created a dozen of single-purpose python scripts (running on a linux PC) that let me single-step the CPU, read CPU registers, dump memory and so on. The scripts use a common &amp;lsquo;backend&amp;rsquo; modules to connect to the x65 hardware over the USB / FTDI interface, but otherwise each script acts on its own.&lt;/p&gt;&#xA;&lt;p&gt;These python scripts and modules are located in the project subdirectory &lt;a href=&#34;https://github.com/jsyk/x65/tree/main/x65pyhost&#34;&gt;x65pyhost&lt;/a&gt;:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Enclosure for X65</title>
      <link>http://localhost:1313/posts/2024/2024-11-17-enclosure-for-x65/</link>
      <pubDate>Sun, 17 Nov 2024 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2024/2024-11-17-enclosure-for-x65/</guid>
      <description>&lt;p&gt;I designed an enclosure box for the &lt;a href=&#34;https://www.jsykora.info/x65-8-16-bit-computer/&#34;&gt;x65-SBC computer&lt;/a&gt;. For modelling I used &lt;a href=&#34;https://solidedge.siemens.com/en/&#34;&gt;Siemens Solid Edge 2024&lt;/a&gt; CAD software, of which I have the Employee Edition. (I think it is just similar to the &lt;a href=&#34;https://resources.sw.siemens.com/en-US/download-solid-edge-community-edition&#34;&gt;free Community Edition&lt;/a&gt;, but I did not verify.)&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/wp-content/uploads/2024/11/image.png&#34;&gt;&lt;img src=&#34;images/image-1024x696.png&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;The enclosure box is composed of &amp;rsquo;top&amp;rsquo; and &amp;lsquo;bottom&amp;rsquo; &lt;a href=&#34;https://github.com/jsyk/x65-mech/tree/main/enclosures/sbc-B-box&#34;&gt;parts&lt;/a&gt; which can be 3d-printed individually. The parts are screwed together with four M3x25 screws and M3 nuts, with the PCB held in the middle:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dreamtracker&#39;s Rabbit Hole</title>
      <link>http://localhost:1313/posts/2024/2024-10-26-dreamtrackers-rabbit-hole/</link>
      <pubDate>Sat, 26 Oct 2024 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2024/2024-10-26-dreamtrackers-rabbit-hole/</guid>
      <description>&lt;p&gt;As mentioned in &lt;a href=&#34;http://localhost:1313/2024/10/the-x65-saga-continues/&#34;&gt;previous post&lt;/a&gt;, &lt;em&gt;Matej&lt;/em&gt; asked me if &lt;a href=&#34;https://www.dreamtracker.org/&#34;&gt;Dreamtracker&lt;/a&gt; app is running on &lt;a href=&#34;https://www.jsykora.info/x65-8-16-bit-computer/&#34;&gt;X65&lt;/a&gt;. I told him that yes, it &lt;em&gt;should&lt;/em&gt; run, but better to test it first myself. I downloaded Dreamtracker in its current version V0.71, fired it up, and well, after a promising start - I could see its main menu for a split second - the program crashed into the &lt;em&gt;Monitor&lt;/em&gt;&amp;hellip;. Well, that felt embarrasing :o&lt;/p&gt;&#xA;&lt;p&gt;This youtube video shows the crashed start:&lt;/p&gt;</description>
    </item>
    <item>
      <title>The X65 Saga Continues</title>
      <link>http://localhost:1313/posts/2024/2024-10-03-the-x65-saga-continues/</link>
      <pubDate>Thu, 03 Oct 2024 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2024/2024-10-03-the-x65-saga-continues/</guid>
      <description>&lt;p&gt;It&amp;rsquo;s Autumn again and I am revisiting my Project &lt;a href=&#34;https://www.jsykora.info/x65-8-16-bit-computer/&#34;&gt;X65&lt;/a&gt;. My list of to-do tasks is endless and growing still :-)&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;finishing tests of the A1 prototype&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;load BOM to Mouser&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;testing the USB interface&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;better ESD concept&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;indication of stopped CPU&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;consider new extension connector&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;consider if SDMMC power should be switched&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;feasibility of machine assembly of prototypes&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;check the new SMC code in CX16&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;check the new 65816 code in CX16&lt;/p&gt;</description>
    </item>
    <item>
      <title>X65-SBC Video-Terminal  for the Forth OF816 Interpreter</title>
      <link>http://localhost:1313/posts/2024/2024-04-05-demo-of-video-terminal-on-x65-sbc-for-the-forth-of816-interpreter/</link>
      <pubDate>Fri, 05 Apr 2024 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2024/2024-04-05-demo-of-video-terminal-on-x65-sbc-for-the-forth-of816-interpreter/</guid>
      <description>&lt;p&gt;In the &lt;a href=&#34;http://localhost:1313/2024/03/32-bit-forth-for-the-x65-with-65c816-cpu/&#34;&gt;previous post&lt;/a&gt; I have mentioned that I am working on a port of the 32-bit Forth interpreter &lt;a href=&#34;https://github.com/jsyk/of816&#34;&gt;OF816&lt;/a&gt; to my &lt;a href=&#34;https://github.com/jsyk/x65&#34;&gt;X65-SBC&lt;/a&gt;, an 8/16-bit retro computer that I am building. The software runs on the X65-SBC in the 65C816 processor, but the user textual input and output was so far realized via the USB/UART interface terminated on a host PC in a terminal emulator (e.g. putty).&lt;/p&gt;&#xA;&lt;p&gt;As the next logical step, shown in the demo below, I have implemented a video text terminal using the VERA chip and the VGA output from the X65-SBC. &lt;a href=&#34;https://github.com/X16Community/vera-module/tree/main&#34;&gt;VERA&lt;/a&gt; is the computer&amp;rsquo;s video chip implemented in an FPGA. VERA has 128kB of internal VRAM and could be configured in various graphics modes, typically generating a 640x480-pixel resolution screen. For the purpose of a textual terminal output I am configuring VERA to display 80 columns by 60 rows of visible characters. Each character is 8x8 pixels, and each character can have one of the 16 foreground and background colors.&lt;/p&gt;</description>
    </item>
    <item>
      <title>32-bit Forth for the X65 with 65C816 CPU</title>
      <link>http://localhost:1313/posts/2024/2024-03-22-32-bit-forth-for-the-x65-with-65c816-cpu/</link>
      <pubDate>Fri, 22 Mar 2024 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2024/2024-03-22-32-bit-forth-for-the-x65-with-65c816-cpu/</guid>
      <description>&lt;p&gt;I am working on a port of the 32-bit FORTH interpreter &lt;a href=&#34;https://github.com/mgcaret/of816&#34;&gt;OF816&lt;/a&gt; for my &lt;a href=&#34;https://github.com/jsyk/x65&#34;&gt;X65-SBC&lt;/a&gt; computer with the 65C816 CPU. The OF816 was created by &lt;a href=&#34;https://github.com/mgcaret&#34;&gt;mgcaret&lt;/a&gt; and is available on github. I made a fork of the OF816 project  and added a new branch for my work: &lt;a href=&#34;https://github.com/jsyk/of816/tree/x65sbc&#34;&gt;x65-sbc&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The OF816 already supports a couple of 65C816-based systems: GoSXB, Apple IIgs, Neon816 and the W65C816SXB. I added a new subdirectory &lt;em&gt;X65&lt;/em&gt; in the &lt;em&gt;platforms&lt;/em&gt; directory and initially copied from the Neon816 port, because it seemed the simplest.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Linux 6.7.x on AMD GPU RX570 requires the kernel parameter amdgpu.dc=0</title>
      <link>http://localhost:1313/posts/2024/2024-03-08-linux-6-7-x-on-amd-gpu-rx570-requires-the-kernel-parameter-amdgpu-dc0/</link>
      <pubDate>Fri, 08 Mar 2024 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2024/2024-03-08-linux-6-7-x-on-amd-gpu-rx570-requires-the-kernel-parameter-amdgpu-dc0/</guid>
      <description>&lt;p&gt;Symptoms: Running Fedora 38 and 39 with kernels 6.7.7 on AMD Ryzen 5 with AMD GPU RX570 (Sapphire Radeon PULSE ITX RX 570 4GD5, 4GB GDDR5) sometimes results in a blank screen (no video signal, monitor going to sleep mode) after the boot. The display manager (sddm, wayland) does not start (or is not visible, there is no video) and it is not possible to login or switch to a virtual console.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Reading of 6502/65816 CPU Registers by a PC-based Debugger</title>
      <link>http://localhost:1313/posts/2024/2024-03-03-reading-of-6502-65816-cpu-registers-by-a-pc-based-debugger/</link>
      <pubDate>Sun, 03 Mar 2024 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2024/2024-03-03-reading-of-6502-65816-cpu-registers-by-a-pc-based-debugger/</guid>
      <description>&lt;p&gt;Modern microcontrollers and microprocessors have built-in facilities for external debuggers to read/write registers, set breakpoints and generally fully control the CPU. This is one of the main usecases of the standard &lt;a href=&#34;https://en.wikipedia.org/wiki/JTAG#Debugging&#34;&gt;JTAG&lt;/a&gt; interface. The 6502 and 65816 CPUs were created more than a &lt;em&gt;decade&lt;/em&gt; before the first version of JTAG was even defined. They contain no support for external debuggers whatsoever.&lt;/p&gt;&#xA;&lt;p&gt;To overcome the lack of debugger support, the system bus controller &amp;ldquo;NORA&amp;rdquo; in the &lt;a href=&#34;https://github.com/jsyk/x65&#34;&gt;X65 computer&lt;/a&gt; (link to GIT repository; photo below) implements the necessary functions for a debugger running on a host PC (with Linux or Windows) and connected over the USB-C port. With this support in NORA a debugger can control the 6502/65816 CPU at the instruction level.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Single-Board version of X65, now on Hackaday</title>
      <link>http://localhost:1313/posts/2024/2024-02-20-single-board-version-of-x65-now-on-hackaday/</link>
      <pubDate>Tue, 20 Feb 2024 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2024/2024-02-20-single-board-version-of-x65-now-on-hackaday/</guid>
      <description>&lt;p&gt;In the last 2 months I have re-done my X65 double-decker computer into a Single Board Computer (SBC).&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/wp-content/uploads/2024/02/mobovabo-to-sbc.jpg&#34;&gt;&lt;img src=&#34;images/mobovabo-to-sbc-1024x310.jpg&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;The single-board version fixes some of the electrical problems I had on the first version and it has way better signal integrity thanks to the 4-layer PCB. Other than that, the feature-set is basically identical.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;added the mono speaker with volume control.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;added (Olimex) UEXT connector - 2x5 pins connected to the NORA FPGA.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Differences between the 65C02 and 65C816 Processors in 8-bit Mode</title>
      <link>http://localhost:1313/posts/2023/2023-12-18-differences-between-the-65c02-and-65c816-processors-in-8-bit-mode/</link>
      <pubDate>Mon, 18 Dec 2023 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2023/2023-12-18-differences-between-the-65c02-and-65c816-processors-in-8-bit-mode/</guid>
      <description>&lt;p&gt;In &lt;a href=&#34;https://github.com/jsyk/x65&#34;&gt;X65&lt;/a&gt; the assembled CPU is either the 8-bit W65C02S or 16-bit W65C816S. The W65C816S is (partially) compatible with W65C02S. This page summarizes the differences from the low-level hardware point of view and in the case that the 65C816 is running in the 8-bit &lt;em&gt;Emulation Mode&lt;/em&gt;.&lt;/p&gt;&#xA;&lt;p&gt;These two photos shows the processors assembled on X65 main board:&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://github.com/jsyk/x65/blob/main/Photos/w65c02_pcb.jpg&#34;&gt;&lt;img src=&#34;images/w65c02_pcb.jpg&#34; alt=&#34;W65C02 on PCB&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://github.com/jsyk/x65/blob/main/Photos/w65c816_pcb.jpg&#34;&gt;&lt;img src=&#34;images/w65c816_pcb.jpg&#34; alt=&#34;W65C816 on PCB&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;processor-pinout-comparison&#34;&gt;Processor Pinout Comparison&lt;/h2&gt;&#xA;&lt;p&gt;Both processors are available in the same QFP-44 package, so they could be assembled alternatively on the same PCB.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AURA FPGA: The replacement of YM2151</title>
      <link>http://localhost:1313/posts/2023/2023-11-25-aura-fpga-the-replacement-of-ym2151/</link>
      <pubDate>Sat, 25 Nov 2023 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2023/2023-11-25-aura-fpga-the-replacement-of-ym2151/</guid>
      <description>&lt;p&gt;This document discusses the FM sound synthesis in the Commander X16 and in my &lt;a href=&#34;https://github.com/jsyk/x65&#34;&gt;x65 computer&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;sound-in-commander-x16&#34;&gt;Sound in Commander X16&lt;/h2&gt;&#xA;&lt;p&gt;Sound in Commander X16 is generated by two sources that are mixed together:&lt;/p&gt;&#xA;&lt;p&gt;  1) by the Programmable Sound Generator (PSG) in VERA FPGA, and&lt;/p&gt;&#xA;&lt;ol start=&#34;2&#34;&gt;&#xA;&lt;li&gt;by the MIDI FM-synthesis chip YM2151.&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;The following picture is a block diagram of the sound subsystem in C&amp;rsquo;X16:&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;images/cx16-sound.drawio.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;The PSG in VERA FPGA is a stereo sound generator loosely based on SID. It supports 16 channels (voices) and PCM playback. There is no ADSR or filters. This must be provided by software. The PSG is an integral part of VERA FPGA user logic that also generates the VGA video output. MIDI-like sound synthesis is provided by YM2151. Yamaha called it an FM operator Type-M (OPM). This is how the chip looked like:&lt;/p&gt;</description>
    </item>
    <item>
      <title>SNES Controller Mess</title>
      <link>http://localhost:1313/posts/2023/2023-08-05-snes-controller-mess/</link>
      <pubDate>Sat, 05 Aug 2023 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2023/2023-08-05-snes-controller-mess/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://en.wikipedia.org/wiki/Super_Nintendo_Entertainment_System&#34;&gt;SNES&lt;/a&gt; Controllers typically look like this:&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/wp-content/uploads/2023/08/obrazek-1.png&#34;&gt;&lt;img src=&#34;images/obrazek-1.png&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;SNES controller is a cheap and easy way how to add a joystick interface to a DIY project. One controller can be cheaply had from aliexpress or similar for around 2 USD.&lt;/p&gt;&#xA;&lt;p&gt;The controller has just 12 digital (on/off) buttons organized in various patterns, as you see in the photo: D-pad, ABXY buttons, two shoulder buttons, start and select. There are no analog interfaces, no LEDs etc.&lt;/p&gt;</description>
    </item>
    <item>
      <title>X65 - 8/16-bit computer</title>
      <link>http://localhost:1313/pages/2023/2023-08-05-x65-8-16-bit-computer/</link>
      <pubDate>Sat, 05 Aug 2023 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/pages/2023/2023-08-05-x65-8-16-bit-computer/</guid>
      <description>&lt;p&gt;&lt;strong&gt;X65&lt;/strong&gt; is a retro/modern 16-bit computer that I designed inspired by the architecture of Commander X16 (CX16). It is based on the legendary 6502 / 65816 processors, which, incredibly, are still in production in 2023 and beyond.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;X65&lt;/strong&gt; is an open-source - you can find all schematic and sources in my GIT repository:&lt;br&gt;&#xA;&lt;a href=&#34;https://github.com/jsyk/x65&#34;&gt;https://github.com/jsyk/x65&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Mechanical design files (enclosures) are available in a seperate GIT repository:&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://github.com/jsyk/x65-mech&#34;&gt;https://github.com/jsyk/x65-mech&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Blog related blog posts on this site are available under the ling: &lt;a href=&#34;https://www.jsykora.info/category/x65/&#34;&gt;Category=X65&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Milestone: X16 ROM BASIC runs the first program!</title>
      <link>http://localhost:1313/posts/2023/2023-05-15-milestone-x16-rom-basic-runs-the-first-program/</link>
      <pubDate>Mon, 15 May 2023 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2023/2023-05-15-milestone-x16-rom-basic-runs-the-first-program/</guid>
      <description>&lt;p&gt;My Open-X65 project achieved a milestone: the unmodified X16 ROM can be loaded and runs! I manually typed in a BASIC maze program, which draws some ASCI graphics:&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/wp-content/uploads/2023/05/20230514_200930_ready_print.jpg&#34;&gt;&lt;img src=&#34;images/20230514_200930_ready_print-1024x576.jpg&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/wp-content/uploads/2023/05/20230514_201322-mazeprog.jpg&#34;&gt;&lt;img src=&#34;images/20230514_201322-mazeprog-1024x576.jpg&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/wp-content/uploads/2023/05/20230514_201336-mazerun.jpg&#34;&gt;&lt;img src=&#34;images/20230514_201336-mazerun-1024x576.jpg&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Open-X65 GIT Repository</title>
      <link>http://localhost:1313/posts/2023/2023-05-15-open-x65-git-repository/</link>
      <pubDate>Mon, 15 May 2023 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2023/2023-05-15-open-x65-git-repository/</guid>
      <description>&lt;p&gt;The Open-X65 GIT repository is now public:&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://github.com/jsyk/x65&#34;&gt;https://github.com/jsyk/x65&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Note: this is not a release! The project is very much a work-in-progress. You have been warned ;-)&lt;/p&gt;</description>
    </item>
    <item>
      <title>OpenX65 part-way assembled</title>
      <link>http://localhost:1313/posts/2023/2023-05-08-openx65-part-way-assembled/</link>
      <pubDate>Mon, 08 May 2023 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2023/2023-05-08-openx65-part-way-assembled/</guid>
      <description>&lt;p&gt;Since the first post a lot of happened:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Motherboard PCB (bottom) has arrived, it is now part-way assembled with components and working quite well. First test-SW (a few instructions in a loop) is running OK.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;I designed the second PCB (top) with video (VERA), audio (AURA - FM synth) and ethernet port. This was also manufactured, part-way assembled and now I have the first VGA video output.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/wp-content/uploads/2023/05/20230508_200647-overview.jpg&#34;&gt;&lt;img src=&#34;images/20230508_200647-overview.jpg&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/wp-content/uploads/2023/05/20230508_200750-mobo-top.jpg&#34;&gt;&lt;img src=&#34;images/20230508_200750-mobo-top.jpg&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.jsykora.info/wp-content/uploads/2023/05/20230508_200722-vabo-top.jpg&#34;&gt;&lt;img src=&#34;images/20230508_200722-vabo-top.jpg&#34; alt=&#34;&#34;&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>My new 65C02-based retro-computer: OpenX65</title>
      <link>http://localhost:1313/posts/2023/2023-03-30-new-project-x65/</link>
      <pubDate>Thu, 30 Mar 2023 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2023/2023-03-30-new-project-x65/</guid>
      <description>&lt;p&gt;I am starting a new hobby project called &lt;a href=&#34;https://www.x65.eu/&#34;&gt;X65&lt;/a&gt;: I intend to create an open-source computer based on the &amp;ldquo;vintage&amp;rdquo; &lt;a href=&#34;https://en.wikipedia.org/wiki/MOS_Technology_6502&#34;&gt;6502 processor&lt;/a&gt;, which is still in production as the W65C02. The original 6502 was used in many home personal computers of the &amp;rsquo;80s: &lt;a href=&#34;https://en.wikipedia.org/wiki/MOS_Technology_6502#Computers_and_games&#34;&gt;Commodore, Atari, Apple II and so on&lt;/a&gt;. My computer will be called &lt;strong&gt;OpenX65&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Features as planned&lt;/strong&gt;:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;use W65C02 and (optionally) W65C816 (the 16-bit version) CPU&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;software compatibility with the &lt;a href=&#34;https://www.commanderx16.com/&#34;&gt;Commander X16&lt;/a&gt;: a modern retro computer, developped by the 8-bit Guy&lt;/p&gt;</description>
    </item>
    <item>
      <title>Initial release of mywayback</title>
      <link>http://localhost:1313/posts/2021/2021-02-27-initial-release-of-mywayback/</link>
      <pubDate>Sat, 27 Feb 2021 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2021/2021-02-27-initial-release-of-mywayback/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Mywayback&lt;/strong&gt; is a complete rewrite of my previous &lt;em&gt;timeback&lt;/em&gt; archival tool. It is now available on the github: &lt;a href=&#34;https://github.com/jsyk/mywayback&#34;&gt;https://github.com/jsyk/mywayback&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;Main features:&lt;/em&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Python 3.x in Windows (with NTFS-only) and Linux. Requires the package &lt;a href=&#34;http://www.grantjenks.com/docs/sortedcontainers/&#34;&gt;sortedcontainers&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Automatic deduplication of source files using SHA256&lt;/li&gt;&#xA;&lt;li&gt;Hashes of the files are stored in a hash-cache under the target directory, and reused on next run&lt;/li&gt;&#xA;&lt;li&gt;Each run produces a new snapshot view of the backed up data with the current date and time.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
    <item>
      <title>Engineers&#39; Tribute, and a handy wire gauge chart by PEI-Genesis</title>
      <link>http://localhost:1313/posts/2020/2020-09-22-engineers-tribute-and-a-handy-wire-gauge-chart-by-pei-genesis/</link>
      <pubDate>Tue, 22 Sep 2020 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2020/2020-09-22-engineers-tribute-and-a-handy-wire-gauge-chart-by-pei-genesis/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://www.engineerstribune.com/&#34;&gt;Engineers&amp;rsquo; Tribute&lt;/a&gt; is an endless well of electronic technology sites, perfectly suited for studying during long winter evenings (or lockdowns.. :-) )&lt;/p&gt;&#xA;&lt;p&gt;Checkout this handy wire-gauge chart made by &lt;a href=&#34;https://www.peigenesis.com/&#34;&gt;PEI-Genesis&lt;/a&gt;. The download link is right at their front page:&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;images/image.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Vacuum-Tube Watch</title>
      <link>http://localhost:1313/pages/2019/2019-10-29-vfdwatch/</link>
      <pubDate>Tue, 29 Oct 2019 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/pages/2019/2019-10-29-vfdwatch/</guid>
      <description>&lt;p&gt;Go see my &lt;a href=&#34;http://localhost:1313/vfd-watch-v2-1/&#34;&gt;Vacuum Tube watch &amp;ldquo;EVERGLOW&amp;rdquo; V2.1&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;images/20191021_203609sm-1024x576.jpg&#34; alt=&#34;&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Release of my Vacuum Tube Watch &#34;EVERGLOW&#34; v2.1</title>
      <link>http://localhost:1313/posts/2019/2019-10-19-release-of-the-vfd-watch-v2-1/</link>
      <pubDate>Sat, 19 Oct 2019 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2019/2019-10-19-release-of-the-vfd-watch-v2-1/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;http://localhost:1313/vfd-watch-v2-1/&#34;&gt;Vacuum Tube Watch&lt;/a&gt; project is &lt;a href=&#34;http://localhost:1313/vfd-watch-v2-1/&#34;&gt;now released&lt;/a&gt; in version V2.1 &amp;ldquo;EVERGLOW&amp;rdquo;. Go see it via the &amp;ldquo;Projects&amp;rdquo; menu above.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;images/01-1024x586.jpg&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Enjoy!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Vacuum Tube Watch &#34;EVERGLOW&#34; v2.1</title>
      <link>http://localhost:1313/pages/2019/2019-10-19-vfd-watch-v2-1/</link>
      <pubDate>Sat, 19 Oct 2019 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/pages/2019/2019-10-19-vfd-watch-v2-1/</guid>
      <description>&lt;p&gt;The &amp;ldquo;&lt;em&gt;EVERGLOW&lt;/em&gt;&amp;rdquo; &lt;em&gt;Watch&lt;/em&gt; is a &lt;a href=&#34;https://en.wikipedia.org/wiki/Vacuum_fluorescent_display&#34;&gt;vacuum tube&lt;/a&gt; clock put on the wrist:&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;images/01-1024x586.jpg&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;images/02-1024x768.jpg&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Features:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Soviet VFD tube &lt;a href=&#34;http://loststeak.com/ivl2-75-vfd-datasheets/&#34;&gt;IVL2-7/5&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;Time (24h), Date, (dd-mm-yyyy), day of week (Mo-Tu-We-etc).&lt;/li&gt;&#xA;&lt;li&gt;Alarm clock (7-day) with a beeper.&lt;/li&gt;&#xA;&lt;li&gt;Stop-watch (00:00 =&amp;gt; 9:59:59)&lt;/li&gt;&#xA;&lt;li&gt;Count-down clock (99:59 =&amp;gt; 00:00)&lt;/li&gt;&#xA;&lt;li&gt;50mAh LiPo accumulator (lasts 1-2 weeks), charging over a Micro-USB -port.&lt;/li&gt;&#xA;&lt;li&gt;Two buttons for activation and settings.&lt;/li&gt;&#xA;&lt;li&gt;Dimensions 70 x 41.5 x 11mm&lt;/li&gt;&#xA;&lt;li&gt;Open hardware, open source.&lt;/li&gt;&#xA;&lt;li&gt;// &lt;strong&gt;DESIGNED IN CZECHIA&lt;/strong&gt; //&lt;/li&gt;&#xA;&lt;li&gt;// &lt;strong&gt;HACKABLE SOFTWARE INSIDE&lt;/strong&gt; //&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;strong&gt;Photo Galery&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>ATtiny&#39;s UPDI interface activates permanently upon noise input!?</title>
      <link>http://localhost:1313/posts/2019/2019-08-25-attinys-updi-interface-activates-permanently-upon-noise-input/</link>
      <pubDate>Sun, 25 Aug 2019 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2019/2019-08-25-attinys-updi-interface-activates-permanently-upon-noise-input/</guid>
      <description>&lt;p&gt;&lt;strong&gt;UPDI&lt;/strong&gt; - Unified Program and Debug Interface - is the new programming and debugging interface on new ATtiny MCUs from Microchip. The UPDI requires just a single pin on the MCU, so it is very suitable for low-pin count chips. Physically it is implemented as a bidirectional (half-duplex) UART protocol. UPDI pin is typically located with the RESET pin on the ATtiny MCUs. A programmable fuse in the MCU switches the RESET/UPDI between these three modes:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Inexpensive Adafruit SMT Breakout boards (SOIC, TSSOP, MSOP) from a PCB Panel</title>
      <link>http://localhost:1313/posts/2019/2019-06-15-pcb-panel-of-smt-breakout-boards-soic-tssop-msop/</link>
      <pubDate>Sat, 15 Jun 2019 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2019/2019-06-15-pcb-panel-of-smt-breakout-boards-soic-tssop-msop/</guid>
      <description>&lt;p&gt;I created a smal 100x100mm PCB mini-panel of some of the SMT breakout boards from &lt;a href=&#34;https://github.com/adafruit/Adafruit-SMT-Breakout-PCBs&#34;&gt;Adafruit&lt;/a&gt;. Each mini-panel contains:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;3x&lt;/strong&gt; SOIC-20 (A-side) and TSSOP-20 (B-side)&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;5x&lt;/strong&gt; SOIC-16 (A-side) and TSSOP-16 (B-side)&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;5x&lt;/strong&gt; SOIC-8 (A-side) and MSOP-8 (B-side)&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;4x&lt;/strong&gt; SOIC-8 (A-side) and TSSOP-8 (B-side)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Note: All SOIC pads have 1.27mm pitch, all TSSOP pads have 0.635mm pitch.&lt;/p&gt;&#xA;&lt;p&gt;Panels were successfully manufactured at &lt;a href=&#34;https://www.seeedstudio.com/fusion.html&#34;&gt;Seeedstudio Fusion PCB&lt;/a&gt; service at the cost of 10 panels / USD 5, plus shipping. Since I got 170 break-out boards in one order, the individual boards are very cheap.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Release of the DIY Curve Tracer Project</title>
      <link>http://localhost:1313/posts/2019/2019-04-25-curve-tracer-released/</link>
      <pubDate>Thu, 25 Apr 2019 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2019/2019-04-25-curve-tracer-released/</guid>
      <description>&lt;p&gt;Here you can find documentation about my DIY &lt;a href=&#34;https://www.jsykora.info/analog-curve-tracer/&#34;&gt;Analog Curve Tracer&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;figure&gt;&#xA;&lt;p&gt;&lt;img src=&#34;images/ct_frontview_cap-1024x768.jpg&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;figcaption&gt;&#xA;&lt;p&gt;Analog Curve Tracer&lt;/p&gt;&#xA;&lt;/figcaption&gt;&#xA;&lt;/figure&gt;</description>
    </item>
    <item>
      <title>Analog Curve Tracer</title>
      <link>http://localhost:1313/pages/2019/2019-04-23-analog-curve-tracer/</link>
      <pubDate>Tue, 23 Apr 2019 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/pages/2019/2019-04-23-analog-curve-tracer/</guid>
      <description>&lt;p&gt;A signature curve tracer is a simple yet useful device in any electronics lab. It shows in picture form the V/A characteristic of a two-terminal device under test (DUT), such as a resistor, a capacitor, a diode or any PN junction. It could also be used to characterise a transistor or an optocoupler, if additional drive circuit for the third terminal is used. Another use is in locating circuit faults: as the probe terminal of the Curve Tracer is brought to every pin of an IC mounted on the probed but unpowered PCB, a faulty IC pin will typically exhibit much different VA characteristic than the other pins (because some structures on that pin a burned out inside the IC).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cheap AVR UPDI Programmer from ATtiny817 Xplained Mini</title>
      <link>http://localhost:1313/posts/2019/2019-04-16-avr-updi-programmer-from-attiny817-xplained-mini/</link>
      <pubDate>Tue, 16 Apr 2019 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2019/2019-04-16-avr-updi-programmer-from-attiny817-xplained-mini/</guid>
      <description>&lt;p&gt;New AVR processors from Microchip/Atmel use a 1-wire UPDI interface for flash programming. You could use either AVR ICE or Pickit 4 as the &amp;ldquo;official&amp;rdquo; programmers (I did not test any of them). Both of these cost &amp;gt;50 EUR.&lt;/p&gt;&#xA;&lt;p&gt;A good alternative, presented in this post, is to modify the &lt;strong&gt;&lt;a href=&#34;https://www.microchip.com/developmenttools/ProductDetails/attiny817-xmini&#34;&gt;ATtiny817 Xplained Mini&lt;/a&gt;&lt;/strong&gt; board (costs ~10 EUR) and use it as the UPDI programmer:&lt;/p&gt;&#xA;&lt;figure&gt;&#xA;&lt;p&gt;&lt;img src=&#34;images/2674883-40.jpg&#34; alt=&#34;ATTINY817-XMINI - ZkuÅ¡ebnÃ­ Sada, ATtiny817/816/814/417 MCU, Xplained Mini, IntegrovanÃ½ Debugger, KapacitnÃ­ Dotek&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>PN7120 won&#39;t not respond on the I2C bus unless CORE_RESET_CMD is sent in &lt;1sec after power-up</title>
      <link>http://localhost:1313/posts/2018/2018-08-03-pn7120-does-not-respond-on-the-i2c-bus/</link>
      <pubDate>Fri, 03 Aug 2018 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2018/2018-08-03-pn7120-does-not-respond-on-the-i2c-bus/</guid>
      <description>&lt;p&gt;NXP&amp;rsquo;s &lt;a href=&#34;https://www.nxp.com/products/identification-and-security/nfc/nfc-reader-ics/nfc-controller-supporting-all-nfc-forum-modes-with-integrated-firmware-and-nci-interface:PN7120&#34;&gt;PN7120&lt;/a&gt; is NFC controller for contactless communication at 13.56MHz. It interfaces with the host CPU via the I2C bus. The I2C slave address of  PN7120 is 0b010100Lx, where L is a configurable LSB of the address (by pin B2, I2CADDR0), and x is the standard I2C R/W bit. Hence the normal I2C address is either 0x28 or 0x29:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;// write to device at address 0x28, R/W=Write&#xA;i2c_master_write_byte(cmd, (0x28 &amp;lt;&amp;lt; 1) | WRITE_BIT, ACK_CHECK_EN);&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;According to &lt;a href=&#34;https://www.nxp.com/docs/en/user-guide/UM10819.pdf&#34;&gt;UM10819&lt;/a&gt; User Manual, Fig. 23 on page 35, the first NCI command after reset must be the CORE_RESET_CMD, which is followed by an appropriate response from PN7120.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Tale of a GCC Upgrade</title>
      <link>http://localhost:1313/posts/2018/2018-01-21-the-tale-of-a-gcc-upgrade/</link>
      <pubDate>Sun, 21 Jan 2018 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2018/2018-01-21-the-tale-of-a-gcc-upgrade/</guid>
      <description>&lt;p&gt;Once upon a time, I decided it is a good time to upgrade the version of gcc compiler we use in our ARM926-based firmware project. Historically, this project uses gcc version 4.6, which is quite outdated nowadays (January 2018). In a different project, built around ARM-Cortex, we already successfully use the gcc version 5.4.1 (Linaro release in January 2017), so I wanted to upgrade our ARM926 project to this newer gcc version.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Did you know: Unaligned accesses in ARM</title>
      <link>http://localhost:1313/posts/2016/2016-09-21-did-you-know-unaligned-accesses-in-arm/</link>
      <pubDate>Wed, 21 Sep 2016 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2016/2016-09-21-did-you-know-unaligned-accesses-in-arm/</guid>
      <description>&lt;p&gt;The X86 has always supported unaligned accesses. In the ARM world the first architecture that supported unaligned accesses in hardware was ARMv6. The architecture was implemented in the ARM11 core around the year 2002 and onward. There is an excellent article at ARM Infocenter giving technical details:&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.faqs/ka15414.html&#34;&gt;http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.faqs/ka15414.html&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;The support for unaligned accesses must be enabled in an ARM core explicitly. This is done by setting the bit A in the register SCTLR. Still, unaligned accesses will be allowed only on Normal memory; accesses to  Device memory type are always checked and will throw exceptions on misaligned accesses.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Connecting MCU and FPGA at 100Mbit/s Using Ethernet RMII [Part 2]</title>
      <link>http://localhost:1313/posts/2016/2016-01-23-connecting-mcu-and-fpga-at-100mbits-using-ethernet-rmii-part-2/</link>
      <pubDate>Sat, 23 Jan 2016 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2016/2016-01-23-connecting-mcu-and-fpga-at-100mbits-using-ethernet-rmii-part-2/</guid>
      <description>&lt;p&gt;&lt;em&gt;This is Part 2 of a two-part series on Ethernet RMII. In &lt;a href=&#34;http://localhost:1313/2016/01/connecting-mcu-and-fpga-at-100mbits-using-ethernet-rmii-part-1/&#34;&gt;Part 1&lt;/a&gt; I described my hardware setup and basic Ethernet operation. In the second and final part I will describe the design of specialized MAC cores I implemented on FPGA, and there will be measurements to see how much throughput and latency the system can achieve.&lt;/em&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Connecting MCU and FPGA at 100Mbit/s Using Ethernet RMII [Part 1]</title>
      <link>http://localhost:1313/posts/2016/2016-01-19-connecting-mcu-and-fpga-at-100mbits-using-ethernet-rmii-part-1/</link>
      <pubDate>Tue, 19 Jan 2016 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2016/2016-01-19-connecting-mcu-and-fpga-at-100mbits-using-ethernet-rmii-part-1/</guid>
      <description>&lt;p&gt;&lt;em&gt;This is Part 1 of the two-part series on Ethernet RMII. &lt;a href=&#34;http://localhost:1313/2016/01/connecting-mcu-and-fpga-at-100mbits-using-ethernet-rmii-part-2/&#34;&gt;Part 2&lt;/a&gt; is also available.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;Imagine your application requires a non-standard periphery controlled by an embedded processor. What options do you have? The periphery can be implemented in an FPGA; depending on periphery complexity you can choose an optimal FPGA that fits your budget. Where the processor goes? There are three possibilities: (a) inside FPGA as a soft-core → it will increase the cost of FPGA (larger type needed) and complicate HDL and software design. Or (b) inside FPGA as a hard-core → a nice compact solution and quite possible with heterogeneous FPGA from &lt;a href=&#34;http://www.xilinx.com/products/silicon-devices/soc/zynq-7000.html&#34;&gt;Xilinx (Zynq)&lt;/a&gt; and &lt;a href=&#34;https://www.altera.com/products/soc/overview.html&#34;&gt;Altera (SoC)&lt;/a&gt;. But the cost of these modern devices could still be too high for price sensitive applications. You must fit both your software and HDL to pre-engineered combinations of FPGA and ARM CPU sizes (perhaps a small Cortex-M core would suffice but you must pay for a gigahertz-class Cortex A cores).&lt;/p&gt;&#xA;&lt;p&gt;The third option (c) is using a stand-alone MCU (maybe even not an ARM) and a standard FPGA. How do you connect them? You are limited to interfaces offered by the MCU. In modern low-end MCUs (by that I mean smaller STM32Fxxx devices) you have I2C (400 kbit/s), UART (115 kbit/s), SPI (~10Mbit/s), Fast Ethernet (100 Mbit/s). So what about the Ethernet core in the MCU? Could it be used to interface with FPGA? Sure it can!&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to: Altium Circuit Maker PCB to OSH-Park</title>
      <link>http://localhost:1313/posts/2015/2015-11-18-how-to-altium-circuit-maker-pcb-to-osh-park/</link>
      <pubDate>Wed, 18 Nov 2015 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2015/2015-11-18-how-to-altium-circuit-maker-pcb-to-osh-park/</guid>
      <description>&lt;p&gt;How to export PCB design from the free &lt;a href=&#34;http://www.circuitmaker.com/&#34;&gt;Altium Circuit Maker&lt;/a&gt; v1.0.4 so that it can be submitted to &lt;a href=&#34;https://oshpark.com/&#34;&gt;OSH Park&lt;/a&gt; fab. This took me an evening to figure out; OSH Park service was bitching about missing &amp;ldquo;outline&amp;rdquo; and/or drill files.&lt;/p&gt;</description>
    </item>
    <item>
      <title>[vid] A little ping-pong after the work</title>
      <link>http://localhost:1313/posts/2015/2015-02-14-vid-a-little-ping-pong-after-the-work/</link>
      <pubDate>Sat, 14 Feb 2015 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2015/2015-02-14-vid-a-little-ping-pong-after-the-work/</guid>
      <description>&lt;p&gt; &lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.youtube.com/watch?v=dQuFrbmcv-0&#34;&gt;https://www.youtube.com/watch?v=dQuFrbmcv-0&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>[Pic] BGA Dead-Bug Style</title>
      <link>http://localhost:1313/posts/2015/2015-01-20-pic-bga-dead-bug/</link>
      <pubDate>Tue, 20 Jan 2015 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2015/2015-01-20-pic-bga-dead-bug/</guid>
      <description>&lt;p&gt; &lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2015/01/DSC_0194_web.jpg&#34;&gt;&lt;img src=&#34;images/DSC_0194_web.jpg&#34; alt=&#34;DSC_0194_web&#34;&gt;&lt;/a&gt;[half-way through; click a pic to see hi-res]&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2015/01/DSC_0219_web.jpg&#34;&gt;&lt;img src=&#34;images/DSC_0219_web.jpg&#34; alt=&#34;DSC_0219_web&#34;&gt;&lt;/a&gt;[connections to bga]&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2015/01/DSC_0221_web.jpg&#34;&gt;&lt;img src=&#34;images/DSC_0221_web.jpg&#34; alt=&#34;DSC_0221_web&#34;&gt;&lt;/a&gt;[finished &amp;ldquo;product&amp;rdquo;]&lt;/p&gt;&#xA;&lt;p&gt;And it (almost) worked! Though not at-speed, because of wire inductances.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A Fistful of Radios</title>
      <link>http://localhost:1313/posts/2015/2015-01-05-a-fistful-of-radios/</link>
      <pubDate>Mon, 05 Jan 2015 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2015/2015-01-05-a-fistful-of-radios/</guid>
      <description>&lt;p&gt;During pre-Christmas sale on &lt;a href=&#34;https://www.seeedstudio.com&#34;&gt;Seeed Studio Bazaar&lt;/a&gt;  they offered &lt;a href=&#34;http://www.seeedstudio.com/depot/nRF24L01Module-p-1394.html&#34;&gt;these digital radio modules&lt;/a&gt; with the &lt;a href=&#34;https://www.nordicsemi.com/kor/node_176/2.4GHz-RF/nRF24L01P&#34;&gt;nRF24L01+&lt;/a&gt; chip for only US$0.81 each. So I bought 10 of them outright :-)&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2015/01/fistful_of_radios.jpg&#34;&gt;&lt;img src=&#34;images/fistful_of_radios.jpg&#34; alt=&#34;Fistful of radios&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;What would YOU  suggest to do with them? Build a wireless flower life-support monitoring network? A mobile voice communications radio system? Retrofit them into talking toasters and robotic vacuum cleaners? Let me know!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Error: jtag status contains invalid mode value - communication failure = SOLVED!</title>
      <link>http://localhost:1313/posts/2014/2014-10-22-error-jtag-status-contains-invalid-mode-value-communication-failure-solved/</link>
      <pubDate>Wed, 22 Oct 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-10-22-error-jtag-status-contains-invalid-mode-value-communication-failure-solved/</guid>
      <description>&lt;p&gt;This issue bugged me a long time, finally I solved it this evening. Debugging code on my &lt;a href=&#34;http://localhost:1313/pip-watch/&#34; title=&#34;PIP-Watch&#34;&gt;PIP-Watch&lt;/a&gt; using my &lt;a href=&#34;http://www.st.com/web/catalog/tools/FM146/CL1984/SC724/SS1677/PF251168?sc=internet/evalboard/product/251168.jsp&#34;&gt;ST-LINK-v2&lt;/a&gt; JTAG debugger was very painful because the debugger software &amp;ndash; &lt;a href=&#34;http://openocd.sourceforge.net/&#34;&gt;OpenOCD&lt;/a&gt; and GDB &amp;ndash; kept failing randomly during debug sessions with a rather cryptic message:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;Error: jtag status contains invalid mode value - communication failure&#xA;Polling target stm32f1x.cpu failed, GDB will be halted. Polling again in 100ms&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;I scratched my head, updated firmware in ST-Link, looked at JTAG/SWDIO signals using a scope&amp;hellip; But nothing helped.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Bluetooth Power Modes</title>
      <link>http://localhost:1313/posts/2014/2014-09-29-bluetooth-power-modes/</link>
      <pubDate>Mon, 29 Sep 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-09-29-bluetooth-power-modes/</guid>
      <description>&lt;p&gt;In &lt;a href=&#34;http://localhost:1313/2014/09/processor-low-power-optimizations-in-pip-watch/&#34; title=&#34;Processor Low-power Optimizations in PIP-Watch&#34;&gt;previous post&lt;/a&gt; we discussed CPU power consumption in &lt;a href=&#34;http://localhost:1313/pip-watch/&#34; title=&#34;PIP-Watch&#34;&gt;PIP-Watch&lt;/a&gt;. Today we look into Bluetooth power consumption because it is significant as much as the CPU power.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Processor Low-power Optimizations in PIP-Watch</title>
      <link>http://localhost:1313/posts/2014/2014-09-28-processor-low-power-optimizations-in-pip-watch/</link>
      <pubDate>Sun, 28 Sep 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-09-28-processor-low-power-optimizations-in-pip-watch/</guid>
      <description>&lt;h1 id=&#34;processor-power&#34;&gt;Processor Power&lt;/h1&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;http://localhost:1313/pip-watch/&#34; title=&#34;PIP-Watch&#34;&gt;PIP-Watch&lt;/a&gt; is a battery-powered device that will be continuously on, hence the average power consumption is one of the most important engineering aspects.&lt;/p&gt;&#xA;&lt;p&gt;In this post I will go through two simple steps of optimizing CPU power - sleep modes and lowering the clock frequency. In a &lt;a href=&#34;http://localhost:1313/2014/09/bluetooth-power-modes/&#34; title=&#34;Bluetooth Power Modes&#34;&gt;next separate post&lt;/a&gt; we will look into Bluetooth module power.&lt;/p&gt;</description>
    </item>
    <item>
      <title>PIP-Watch Boards &amp; Assembly</title>
      <link>http://localhost:1313/posts/2014/2014-09-17-pip-watch-boards-assembly/</link>
      <pubDate>Wed, 17 Sep 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-09-17-pip-watch-boards-assembly/</guid>
      <description>&lt;p&gt;The printed circuit boards for PIP-Watch Zero came from Pragoboard fab on Friday 12 Sept. I ordered three pieces because the cost is practically identical as for two or one.&lt;/p&gt;&#xA;&lt;p&gt;[caption id=&amp;ldquo;attachment_484&amp;rdquo; align=&amp;ldquo;aligncenter&amp;rdquo; width=&amp;ldquo;845&amp;rdquo;]&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2014/09/pipwatch_zero_pcbs.jpg&#34;&gt;&lt;img src=&#34;images/pipwatch_zero_pcbs.jpg&#34; alt=&#34;PIP-Watch Zero: Pristine PCBs from fab&#34;&gt;&lt;/a&gt; PIP-Watch Zero: Pristine PCBs from fab[/caption]&lt;/p&gt;&#xA;&lt;p&gt;On Saturday I assembled one board, and on Sunday I tested it and started working on firmware. I had some problems with PLL in the microcontroller  - the CPU hard-resetted the instant the PLL  was enabled. Eventually I found a bad solder joint on one of the CPU&amp;rsquo;s power supply pins.&lt;/p&gt;</description>
    </item>
    <item>
      <title>PIP-Watch &#34;Zero&#34; - Schematic, BOM, and Layout</title>
      <link>http://localhost:1313/posts/2014/2014-09-07-pip-watch-zero-schematic-bom-and-layout/</link>
      <pubDate>Sun, 07 Sep 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-09-07-pip-watch-zero-schematic-bom-and-layout/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://github.com/jsyk/PIP-Watch/blob/master/pipwatch_zero/pipwatch_zero-hw02.pdf?raw=true&#34;&gt;Schematic [PDF]&lt;/a&gt;, BOM, and PCB layout for my PIP-Watch &amp;ldquo;Zero&amp;rdquo; was completed during this week. Layout data was sent to a local PCB fab - pragoboard.cz. The board should be ready and shipped during the next week.&lt;/p&gt;&#xA;&lt;p&gt;The PCB is is 80mm*35mm. The top side is dedicated to the EPD display, battery (underneath the display), 3 push-buttons and 4 LEDs. The bottom side carries all the main electronics - processor, bluetooth modem, display driver, and power source.&lt;/p&gt;</description>
    </item>
    <item>
      <title>FreeRTOS tasks and queues</title>
      <link>http://localhost:1313/posts/2014/2014-07-27-freertos-tasks-and-queues/</link>
      <pubDate>Sun, 27 Jul 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-07-27-freertos-tasks-and-queues/</guid>
      <description>&lt;p&gt;In my previous homebrew projects I did not use any operating system in the embedded processors. Software was programmed on a bare-metal hardware. In my &lt;a href=&#34;http://localhost:1313/talking-clock/&#34; title=&#34;Talking Clock&#34;&gt;Talking Clock&lt;/a&gt; project I created a simple cooperative event-processing abstraction layer, but it was very limited.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Framebuffer Drawing with u8glib [VIDEO]</title>
      <link>http://localhost:1313/posts/2014/2014-07-02-framebuffer-drawing-with-u8glib/</link>
      <pubDate>Wed, 02 Jul 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-07-02-framebuffer-drawing-with-u8glib/</guid>
      <description>&lt;p&gt;GDE021A1 is a graphics display with a resolution 172x72 pixels, each pixel is 2 bits deep (4 shades of grey). The display has an internal controller SSD1606 with a framebuffer. The framebuffer size is 172*72*2/8=3096 Bytes. When the display is powered up, the system processor sends initialization sequence that first sets up controller&amp;rsquo;s internal registers (the controller SSD1606 is fairly generic) and then sends new framebuffer content. The display controller then autonomously pushes the framebuffer contents to the physical screen.&lt;/p&gt;&#xA;&lt;p&gt;The display controller can be configured to orient the framebuffer almost any way. I configured it into a landscape mode, with the X-axis going right and the Y-axis down, as shown on the photo.&lt;/p&gt;</description>
    </item>
    <item>
      <title>EPD Display Working!</title>
      <link>http://localhost:1313/posts/2014/2014-06-18-epd-display-working/</link>
      <pubDate>Wed, 18 Jun 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-06-18-epd-display-working/</guid>
      <description>&lt;p&gt;Today I have managed to get the &lt;a href=&#34;http://localhost:1313/2014/04/mailbag-epaper-display-module/&#34; title=&#34;Mailbag: ePaper Display Module&#34;&gt;GDE021A1&lt;/a&gt; ePaper display (EPD) working! I used my &lt;a href=&#34;http://localhost:1313/2014/05/attempt-at-soldering-an-fpc-connector-with-0-5mm-pitch-and-a-prototyping-pcb-design/&#34; title=&#34;Foolish Attempt at Soldering an FPC Connector with 0.5mm Pitch, and a Prototyping PCB Design&#34;&gt;minimal EPD-Driver board&lt;/a&gt;, which implements a flat-flex cable connector and a booster circuit for the display. The booster generates high voltages needed for display operation (around +-25V). The display is driven by &lt;a href=&#34;http://www.st.com/web/catalog/mmc/FM141/SC1169/SS1031/LN1567/PF164483&#34;&gt;STM32F101&lt;/a&gt; Cortex-M3 CPU, mounted on a universal PCB. The picture below depicts my workbench setup (click to see a full-size image):&lt;/p&gt;&#xA;&lt;p&gt;[caption id=&amp;ldquo;attachment_410&amp;rdquo; align=&amp;ldquo;aligncenter&amp;rdquo; width=&amp;ldquo;1205&amp;rdquo;]&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2014/06/epd_driver_proto-topview-text.png&#34;&gt;&lt;img src=&#34;images/epd_driver_proto-topview-text.png&#34; alt=&#34;EPD Driver Prototype-workbench view with captions&#34;&gt;&lt;/a&gt; EPD Driver Prototype-workbench view with captions[/caption]&lt;/p&gt;</description>
    </item>
    <item>
      <title>Li-On Battery Charging (and Discharging)</title>
      <link>http://localhost:1313/posts/2014/2014-06-11-li-on-battery-charging-and-discharging/</link>
      <pubDate>Wed, 11 Jun 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-06-11-li-on-battery-charging-and-discharging/</guid>
      <description>&lt;p&gt;In my &lt;a href=&#34;http://localhost:1313/pip-watch/&#34; title=&#34;PIP-Watch&#34;&gt;PIP-Watch&lt;/a&gt; project I will use a Li-On battery to provide power. Li-On batteries are easy to use in hobby projects: they are light, small, with high capacity, and they come in variety of sizes. Most (not all) Li-On batteries have nominal voltage 3.7V, hence you can directly power your standard 3.3V digital logic directly, using only a simple low-drop linear regulator (e.g. LD59015).&lt;/p&gt;&#xA;&lt;p&gt;For my first experiments I chose &lt;a href=&#34;http://www.cpkb.org/wiki/Nokia_BL-4C_battery&#34;&gt;Nokia BL-4C&lt;/a&gt; Li-On battery. It&amp;rsquo;s nominal voltage is 3.7V, charging (maximal) voltage is 4.2V, the capacity is 860mAh.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Voltcraft VC-870 Multimeter Used With UNI-T UT-D04 USB Cable</title>
      <link>http://localhost:1313/posts/2014/2014-06-05-voltcraft-vc-870-multimeter-used-with-uni-t-ut-d04-usb-cable/</link>
      <pubDate>Thu, 05 Jun 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-06-05-voltcraft-vc-870-multimeter-used-with-uni-t-ut-d04-usb-cable/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Target hardware:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;http://www.conrad.de/ce/de/product/124603/VOLTCRAFT-VC870-Digital-Multimeter-m-Leistungsmessadapter-VC800-Serie-40000-Counts-CAT-IV-600-V?ref=searchDetail&#34;&gt;VOLTCRAFT VC-870 Multimeter&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;http://sigrok.org/wiki/Device_cables#UNI-T_UT-D04&#34;&gt;UNI-T UT-D04 USB Cable&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;strong&gt;Software repository location:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://github.com/jsyk/VC870_USB_Datalog&#34;&gt;https://github.com/jsyk/VC870_USB_Datalog&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;strong&gt;The issue this software solves:&lt;/strong&gt; Although the Voltcraft multimeter and the UNI-T USB cable are  hardware compatible (the USB cable adapter fits into the multimeter connector perfectly), the software requirements are different. Original Voltcraft USB cable, which costs tripple the UNI-T cable by the way, mimics RS232 adapter when plugged in USB host PC. The UNI-T cable uses different chip internally and behaves like a HID device. On the other hand, UNI-T multimeters use different communication protocol over the serial line than the &lt;a href=&#34;https://github.com/jsyk/VC870_USB_Datalog/blob/master/doc/vc870_protocol.pdf?raw=true&#34;&gt;VC870 does&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fun with a switching regulator MC34063A</title>
      <link>http://localhost:1313/posts/2014/2014-05-24-fun-with-mc34063a/</link>
      <pubDate>Sat, 24 May 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-05-24-fun-with-mc34063a/</guid>
      <description>&lt;p&gt;Being mostly &amp;lsquo;digital&amp;rsquo; guy, I&amp;rsquo;ve always shied off from switching mode power supplies because they are too much analog to my liking. I decided to break my habit by playing around with &lt;a href=&#34;http://www.ti.com/product/mc34063a&#34;&gt;MC34063A&lt;/a&gt;, a 1.5-A Boost/Buck/Inverting Switching Regulator.&lt;/p&gt;&#xA;&lt;p&gt;I tried an inverting topology that generates -12V from +6V power supply. A copy of schema from datasheet is below, and an implementation on a breadboard can be seen above at the page tile:&lt;/p&gt;&#xA;&lt;p&gt;[caption id=&amp;ldquo;attachment_372&amp;rdquo; align=&amp;ldquo;aligncenter&amp;rdquo; width=&amp;ldquo;827&amp;rdquo;]&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2014/05/mc34063a-inverting-dsschema.png&#34;&gt;&lt;img src=&#34;images/mc34063a-inverting-dsschema.png&#34; alt=&#34;MC34063A: Inverting topology&#34;&gt;&lt;/a&gt; MC34063A: Inverting topology[/caption]&lt;/p&gt;&#xA;&lt;p&gt;The converter works by first charging coil L by a current drawn through transistor Q1. When Q1 is switched off the energy stored in the coil is discharged through diode 1N5819 into output capacitor Co. Because current through the coil L goes always from top to bottom (as drawn in the schematic above), the discharging phase is effectively pulling the output voltage below ground level.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Logic Voltage Levels</title>
      <link>http://localhost:1313/posts/2014/2014-05-22-logic-voltage-levels/</link>
      <pubDate>Thu, 22 May 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-05-22-logic-voltage-levels/</guid>
      <description>&lt;p&gt;Again and again I need to look up the logic voltage levels of various logic gate standards like HC, HCT, LVT, and so on. I found a nice article on &lt;a href=&#34;http://www.eetimes.com/document.asp?doc_id=1230846&#34;&gt;EETimes: A brief recap of popular logic standards&lt;/a&gt;. The page has &lt;a href=&#34;http://m.eet.com/media/1102811/FigSB3.gif&#34;&gt;a picture&lt;/a&gt; that recaps all the popular standards along with their Voh, Vih, Vil, and Vol voltage levels. However, the picture resolution is very low quality, and it is also not evident at the first glance what is the relation between standards. So I redraw the picture in &lt;a href=&#34;http://www.inkscape.org/&#34;&gt;Inkscape&lt;/a&gt;, an open-source SVG editor. The result is here (click to see large image):&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2014/05/logic_voltage_stds.png&#34;&gt;&lt;img src=&#34;images/logic_voltage_stds.png&#34; alt=&#34;Logic Voltage Standards&#34;&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Bluetoothing to Android Tablet</title>
      <link>http://localhost:1313/posts/2014/2014-05-18-bluetoothing-to-a-tablet/</link>
      <pubDate>Sun, 18 May 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-05-18-bluetoothing-to-a-tablet/</guid>
      <description>&lt;p&gt;Today I tried pairing my UART-to-Bluetooth adapter to a Nexus 7 tablet to see how it works. On the tablet I used &lt;a href=&#34;https://play.google.com/store/apps/details?id=es.pymasde.blueterm&amp;amp;hl=en&#34;&gt;BlueTerm&lt;/a&gt;, an open-source terminal emulator for communicating with any serial device using a bluetooth serial adapter.&lt;/p&gt;&#xA;&lt;p&gt;I connected my Bluetooth adapter through a USB/UART adapter to a PC. On the PC in a terminal emulator the following sequence of commands is sent to the BT adapter:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;///&#xA;at*agln=&amp;#34;PIP-Watch&amp;#34;,0&#xA;at*agfp=&amp;#34;1234&amp;#34;,0&#xA;at*addm&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The three slashes are an escape sequence to put the adapter into the AT-mode. Then we set BT device name and a PIN. Finally we exit the AT-mode, entering data mode. The adapter now awaits BT connections.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Foolish Attempt at Soldering an FPC Connector with 0.5mm Pitch, and a Prototyping PCB Design</title>
      <link>http://localhost:1313/posts/2014/2014-05-17-attempt-at-soldering-an-fpc-connector-with-0-5mm-pitch-and-a-prototyping-pcb-design/</link>
      <pubDate>Sat, 17 May 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-05-17-attempt-at-soldering-an-fpc-connector-with-0-5mm-pitch-and-a-prototyping-pcb-design/</guid>
      <description>&lt;p&gt;Mechanical drawing of my &lt;a href=&#34;http://www.jsykora.info/?p=229&#34; title=&#34;Mailbag: ePaper Display Module&#34;&gt;EPD ePaper display GDE021A1&lt;/a&gt; is shown below. Signals to the display are connected via a 24-pin flex flat cable. The pitch between pins is only 0.5mm. A suitable matching connector is &lt;a href=&#34;http://www.molex.com/molex/products/datasheet.jsp?part=active/0524352471_FFC_FPC_CONNECTORS.xml&#34;&gt;MOLEX 52435-2471 FPC RCPT 24PIN 1ROW&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2014/05/GDE021A1_mechanical.png&#34;&gt;&lt;img src=&#34;images/GDE021A1_mechanical.png&#34; alt=&#34;GDE021A1_mechanical&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;On Thursday I tried soldering thin wires directly on the MOLEX connector I got from Farnell. However, my attempt was very naïve because the pitch between pins on the connector is only 0.5mm. So I failed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>New Project: PIP-Watch</title>
      <link>http://localhost:1313/posts/2014/2014-05-17-new-project-pip-watch/</link>
      <pubDate>Sat, 17 May 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-05-17-new-project-pip-watch/</guid>
      <description>&lt;p&gt;I started a new project called &lt;strong&gt;&lt;a href=&#34;http://localhost:1313/pip-watch/&#34; title=&#34;PIP-Watch&#34;&gt;PIP-Watch: Personal Information Panel/Watch&lt;/a&gt;&lt;/strong&gt;. It will be a kind of &lt;a href=&#34;http://en.wikipedia.org/wiki/Smartwatch&#34;&gt;smartwatch&lt;/a&gt;.  It will use an ePaper display and a bluetooth connection to a smart-phone.&lt;/p&gt;&#xA;&lt;p&gt;I also registered the &lt;a href=&#34;http://hackaday.io/project/1181-PIP-Watch&#34;&gt;project on hackaday.io&lt;/a&gt;, to take part in this year&amp;rsquo;s Hackaday Prize, which will send one hacker into space!&lt;/p&gt;</description>
    </item>
    <item>
      <title>PIP-Watch</title>
      <link>http://localhost:1313/pages/2014/2014-05-17-pip-watch/</link>
      <pubDate>Sat, 17 May 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/pages/2014/2014-05-17-pip-watch/</guid>
      <description>&lt;p&gt;&lt;strong&gt;PIP-Watch (Personal Information Panel)&lt;/strong&gt; is an open-source smart watch with an ePaper display, a bluetooth modem and a Li-Ion accumulator.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2014/05/pipwatch-zero-angleshot.jpg&#34;&gt;&lt;img src=&#34;images/pipwatch-zero-angleshot.jpg&#34; alt=&#34;pipwatch-zero-angleshot&#34;&gt;&lt;/a&gt;&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2014/05/pipwatch-zero-enface.jpg&#34;&gt;&lt;img src=&#34;images/pipwatch-zero-enface.jpg&#34; alt=&#34;pipwatch-zero-enface&#34;&gt;&lt;/a&gt;&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2014/05/pipwatch-zero-usbside.jpg&#34;&gt;&lt;img src=&#34;images/pipwatch-zero-usbside.jpg&#34; alt=&#34;pipwatch-zero-usbside&#34;&gt;&lt;/a&gt;&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2014/05/pipwatch-zero-resetside.jpg&#34;&gt;&lt;img src=&#34;images/pipwatch-zero-resetside.jpg&#34; alt=&#34;pipwatch-zero-resetside&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;This is a work in progress&amp;hellip; And this project &lt;strong&gt;&lt;a href=&#34;http://hackaday.io/project/1181-PIP-Watch&#34;&gt;takes part&lt;/a&gt;&lt;/strong&gt; in the &lt;a href=&#34;http://hackaday.io/prize/&#34;&gt;HACKADAY Prize&lt;/a&gt; contest!&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://hackaday.io/project/1181-PIP-Watch&#34;&gt;&lt;img src=&#34;images/hackaday_prize.jpg&#34; alt=&#34;hackaday_prize&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;&lt;em&gt;&amp;hellip;Show&lt;/em&gt;&lt;/strong&gt; Pip-Watch uses a small ePaper/eInk electrophoretic display (EPD). Electrophoretic displays have high contrast even in sun light, and very low power consumption, making them suitable for always-on battery-powered embedded devices. Low power consumption comes from the fact that the EPD draws no power when just displaying still image; it needs energy only when redrawing the screen.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Philips PM3310 Digital Storage Oscilloscope</title>
      <link>http://localhost:1313/posts/2014/2014-05-14-philips-pm3310-digital-storage-oscilloscope/</link>
      <pubDate>Wed, 14 May 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-05-14-philips-pm3310-digital-storage-oscilloscope/</guid>
      <description>&lt;p&gt;I got myself an old &lt;strong&gt;Philips PM3310 Digital Storage Oscilloscope&lt;/strong&gt; (DSO). The scope has a classic CRT screen, but otherwise it is a fully digital device. The scope has two channels. Analogue bandwidth of the input attenuator/amplifier is 60MHz, which is not bad at all. Sampling frequency in real-time mode, however, is only 50 Mega samples per second. Each sampling &amp;lsquo;run&amp;rsquo; after a trigger stores 256 samples into a RAM. The sample RAM has capacity for 4 independent waveforms. The 50M sampling speed allows single-shot time base up to 500ns/div, and a recurrent time base up to 5ns/div (sampling of repetitive signals in &lt;a href=&#34;http://www.tek.com/document/application-note/real-time-versus-equivalent-time-sampling&#34;&gt;equivalent time&lt;/a&gt;). The internal CPU switches between the modes as needed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Bluetooth Module (Re-)Investigation</title>
      <link>http://localhost:1313/posts/2014/2014-05-12-bluetooth-module-re-investigation/</link>
      <pubDate>Mon, 12 May 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-05-12-bluetooth-module-re-investigation/</guid>
      <description>&lt;p&gt;Some five years ago I bought a nice UART-over-Bluetooth adapter module. The module emulates a serial port (UART) over a Bluetooth connection. All necessary chips and an antenna are mounted on a small PCB board depicted below.&lt;/p&gt;&#xA;&lt;p&gt;The type I&amp;rsquo;ve got is the &lt;a href=&#34;https://github.com/jsyk/PIP-Watch/raw/master/doc/third-party/BT_to_Serial_converter-em_ds_oemspa_310.pdf&#34;&gt;cB-OEMSPA310i-04&lt;/a&gt; with an internal antenna. The module requires only a 3.3V power.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2014/05/cb-OEMSPA-module.png&#34;&gt;&lt;img src=&#34;images/cb-OEMSPA-module.png&#34; alt=&#34;cb-OEMSPA-module&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Communication with the module is over serial UART at 3.3V logic levels. The basic RXD/TXD signal pair is complemented with hardware flow control via RTS/CTS, and an optional BT connection status via DSR/DTR. A three-colour LED (red, blue, green) can be directly connected to dedicated pins on the module to visually indicate the state of module to the user.&lt;/p&gt;&#xA;&lt;p&gt;The BT module is &lt;a href=&#34;https://github.com/jsyk/PIP-Watch/raw/master/doc/third-party/Serial_Port_Adapter_AT_Commands.pdf&#34;&gt;controlled by standard AT commands&lt;/a&gt;. When powered up or after a reset the module is in a data mode with no connection over BT. Local application microcontroller connected to the RXD/TXD/RTS/CTS signals first sends an escape sequence, which normally consists of three forward slashes &amp;lsquo;///&amp;rsquo;. This puts the module into the AT mode. In AT mode the strings sent over the local UART are interpreted as commands, while in data mode all data is passed through to bluetooth and over the air.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Talking Clock: COMPLETED!</title>
      <link>http://localhost:1313/posts/2014/2014-05-06-talking-clock-completed/</link>
      <pubDate>Tue, 06 May 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-05-06-talking-clock-completed/</guid>
      <description>&lt;p&gt;Finally I declare the Talking Clock project complete! Hardware is built and is working, documentation has been written.&lt;/p&gt;&#xA;&lt;p&gt;The permanent &lt;strong&gt;&lt;a href=&#34;http://www.jsykora.info/?page_id=240&#34; title=&#34;Talking Clock&#34;&gt;project web page is here&lt;/a&gt;&lt;/strong&gt;. I have also created a &lt;a href=&#34;http://hackaday.io/project/1082-Talking-Nixie-Clock&#34;&gt;parallel page on hackaday.io&lt;/a&gt;. Enjoy!&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2014/04/tc_front.jpg&#34;&gt;&lt;img src=&#34;images/tc_front.jpg&#34; alt=&#34;tc_front&#34;&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Talking Clock</title>
      <link>http://localhost:1313/pages/2014/2014-04-27-talking-clock/</link>
      <pubDate>Sun, 27 Apr 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/pages/2014/2014-04-27-talking-clock/</guid>
      <description>&lt;p&gt;The &lt;strong&gt;talking clock&lt;/strong&gt; can tell the current time aloud in English. Time announcement is triggered by pressing a button on a remote controller. When I awake at night I cannot recognize digits on any wall clock because I don&amp;rsquo;t have my dioptric glasses on. But I can easily find remote controller and press the trigger button just by touch, and thus learn that I don&amp;rsquo;t have to get up just yet (ideally).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Mailbag: ePaper Display Module</title>
      <link>http://localhost:1313/posts/2014/2014-04-24-mailbag-epaper-display-module/</link>
      <pubDate>Thu, 24 Apr 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-04-24-mailbag-epaper-display-module/</guid>
      <description>&lt;p&gt;Look what I&amp;rsquo;ve got by post today from our Chinese comrades at &amp;lsquo;&lt;a href=&#34;http://www.good-display.com/products_detail/&amp;amp;productId=07992b88-6ac5-4a0e-ba84-d7cadcd55ebe.html&#34;&gt;Good Display&lt;/a&gt;&amp;rsquo; factory: a nice small 2.04-inch &lt;a href=&#34;http://en.wikipedia.org/wiki/Electronic_paper&#34;&gt;electrophoretic display&lt;/a&gt; (EPD), or better known as ePaper/eInk display or &amp;rsquo;electronic paper&amp;rsquo;.&lt;/p&gt;&#xA;&lt;p&gt;[caption id=&amp;ldquo;attachment_232&amp;rdquo; align=&amp;ldquo;alignnone&amp;rdquo; width=&amp;ldquo;856&amp;rdquo;]&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2014/04/epd-front.jpg&#34;&gt;&lt;img src=&#34;images/epd-front.jpg&#34; alt=&#34;ePaper EPD display front side view&#34;&gt;&lt;/a&gt; ePaper EPD display front side view[/caption]&lt;/p&gt;&#xA;&lt;p&gt;[caption id=&amp;ldquo;attachment_231&amp;rdquo; align=&amp;ldquo;aligncenter&amp;rdquo; width=&amp;ldquo;632&amp;rdquo;]&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2014/04/epd-back.jpg&#34;&gt;&lt;img src=&#34;images/epd-back.jpg&#34; alt=&#34;ePaper EPD display back side&#34;&gt;&lt;/a&gt; ePaper EPD display back side[/caption]&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://en.wikipedia.org/wiki/Electronic_paper&#34;&gt;Electrophoretic displays&lt;/a&gt; (EPD) do not require any power to retain  an image. Power is needed only when redrawing the screen. The technology is thus used in electronic paper readers such as &lt;a href=&#34;http://en.wikipedia.org/wiki/Amazon_Kindle&#34;&gt;Amazon Kindle&lt;/a&gt; or the &lt;a href=&#34;http://en.wikipedia.org/wiki/Pebble_%28watch%29&#34;&gt;Pebble smartwatch&lt;/a&gt; &lt;em&gt;(correction: Pebble uses different display: &lt;a href=&#34;http://www.sharpmemorylcd.com/1-26-inch-memory-lcd.html&#34;&gt;Memory LCD&lt;/a&gt;)&lt;/em&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Talking Nixie Clock</title>
      <link>http://localhost:1313/posts/2014/2014-04-06-talking-nixie-clock/</link>
      <pubDate>Sun, 06 Apr 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-04-06-talking-nixie-clock/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve just assembled both PCB boards of my talking nixie clock together and went &amp;lsquo;whoa, this thing IS really beautiful!&amp;rsquo;.  Check it out below, electronics porn at its best!&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2014/04/nixclock-boards_speaker.jpg&#34;&gt;&lt;img src=&#34;images/nixclock-boards_speaker-1024x678.jpg&#34; alt=&#34;nixclock-boards_speaker&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2014/04/nixclock-closeup.jpg&#34;&gt;&lt;img src=&#34;images/nixclock-closeup-1024x678.jpg&#34; alt=&#34;nixclock-closeup&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2014/04/nixclock-in_dark.jpg&#34;&gt;&lt;img src=&#34;images/nixclock-in_dark-1024x678.jpg&#34; alt=&#34;nixclock-in_dark&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;The first two pictures were taken with a flash to get good details, the last one without, hence a poorer picture quality. But you at least get the idea how those nixie puppies shine!&lt;/p&gt;&#xA;&lt;p&gt;Later I&amp;rsquo;ll get my documentation together and create a proper project page with all schematics, pcbs, source codes, better pictures etc etc.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Talking Clock Prototype</title>
      <link>http://localhost:1313/posts/2014/2014-02-02-talking-clock-prototype/</link>
      <pubDate>Sun, 02 Feb 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-02-02-talking-clock-prototype/</guid>
      <description>&lt;p&gt;I am working on a talking clock with a remote IR control. The idea is that when I awake at night I don&amp;rsquo;t have my  glasses on, hence I cannot recognize digits on a clock display. So I figured out that what I need is a talking clock that could tell me the time aloud. The audible announcement is triggered by a button press on a standard infrared remote, normally used to control my hi-fi equipment.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ZedBoard: Late Xmas present has arrived!</title>
      <link>http://localhost:1313/posts/2014/2014-01-17-zedboard-late-xmas-present-has-arrived/</link>
      <pubDate>Fri, 17 Jan 2014 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2014/2014-01-17-zedboard-late-xmas-present-has-arrived/</guid>
      <description>&lt;p&gt;Finally, after much waiting, my ZedBoard arrived on Tuesday. See it shining in the picture above, isn&amp;rsquo;t it lovely?&lt;/p&gt;&#xA;&lt;p&gt;So far I managed only to unbox it and turn it on&amp;hellip; Hence only a few notes on the beginnings:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&lt;strong&gt;Running Vivado 2013.3 in Fedora Linux&lt;/strong&gt;: see my &lt;a href=&#34;http://www.jsykora.info/?p=131&#34; title=&#34;Xilinx Vivado 2013.3 on Fedora 18: Working around a D-Bus bug&#34;&gt;previous&lt;/a&gt; post.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Running the demo Linux bitstream from the supplied SD card&lt;/strong&gt;: you need to reconfigure switches, at least JP8, JP9 should be at 3V3 side. Best to see the README on the SD card. The default configuration (JP7-11 at GND) is for JTAG download.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Installing USB-JTAG cable drivers in Linux&lt;/strong&gt;: surprisingly, all I needed to do was to run Vivado/2013.3/data/xicom/cable_drivers/lin64/digilent/digilent.adept.runtime_2.14.3-x86_64/install.sh as root.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Missing &lt;em&gt;impact&lt;/em&gt; tool in Vivado 2013.3&lt;/strong&gt;: &lt;em&gt;impact&lt;/em&gt; is deprecated. Use Hardware Manager / Open Target tabs in Vivado GUI.&lt;/li&gt;&#xA;&lt;/ol&gt;</description>
    </item>
    <item>
      <title>Xilinx Vivado 2013.3 on Fedora 18: Working around a D-Bus bug</title>
      <link>http://localhost:1313/posts/2013/2013-11-10-xilinx-vivado-2013-3-on-fedora-18-working-around-a-d-bus-bug/</link>
      <pubDate>Sun, 10 Nov 2013 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2013/2013-11-10-xilinx-vivado-2013-3-on-fedora-18-working-around-a-d-bus-bug/</guid>
      <description>&lt;p&gt;Running Xilinx &lt;strong&gt;Vivado 2013.3&lt;/strong&gt; (webpack license) on &lt;strong&gt;Fedora 18&lt;/strong&gt; may fail with the following error message:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;$ vivado&#xA;&#xA;****** Vivado v2013.3 (64-bit)&#xA;  **** SW Build 329390 on Wed Oct 16 18:26:55 MDT 2013&#xA;  **** IP Build 192953 on Wed Oct 16 08:44:02 MDT 2013&#xA;    ** Copyright 1986-1999, 2001-2013 Xilinx, Inc. All Rights Reserved.&#xA;&#xA;INFO: [Common 17-78] Attempting to get a license: Implementation&#xA;process 17688: arguments to dbus_move_error() were incorrect, assertion &amp;#34;(dest) == NULL || !dbus_error_is_set ((dest))&amp;#34; failed in file dbus-errors.c line 282.&#xA;This is normally a bug in some application using the D-Bus library.&#xA;  D-Bus not built with -rdynamic so unable to print a backtrace&#xA;Abnormal program termination (6)&#xA;Please check &amp;#39;/home/jara/hdl/hs_err_pid17688.log&amp;#39; for details&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The workaround is to make the D-Bus communication socket file &lt;strong&gt;/var/run/dbus/system_bus_socket&lt;/strong&gt; unavailable when the Xilinx tools run.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hardware/Software Co-Simulation (PORTAL)</title>
      <link>http://localhost:1313/posts/2013/2013-05-25-portal/</link>
      <pubDate>Sat, 25 May 2013 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2013/2013-05-25-portal/</guid>
      <description>&lt;p&gt;I devised &lt;strong&gt;PORTAL&lt;/strong&gt; as a means for validating our hardware accelerator cores (&lt;a href=&#34;http://localhost:1313/p/ddecs2012-asvp.pdf&#34;&gt;ASVP&lt;/a&gt; in &lt;a href=&#34;http://localhost:1313/?page_id=46&#34; title=&#34;SMECY&#34;&gt;SMECY&lt;/a&gt;) in a co-simulated environment together with control software. The basic structure of PORTAL is shown below:&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2013/05/portal-hw-sw.png&#34;&gt;&lt;img src=&#34;images/portal-hw-sw.png&#34; alt=&#34;portal-hw-sw&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;PORTAL is a a communication library that connects a hardware model simulated in ModelSim to its control software running on a PC. Communication is done over TCP/IP.&lt;/p&gt;&#xA;&lt;p&gt;In PORTAL the primitive communication abstraction is a &lt;strong&gt;shared memory&lt;/strong&gt;. All PORTAL clients have a common access to a (virtually) shared 32-bit address space. Any client can dynamically claim and register any unoccupied memory range in the address space and start to serve read/write requests generated by other clients. Management of the virtual address space is dedicated to the central sever, PHUB.&lt;/p&gt;</description>
    </item>
    <item>
      <title>MASSTEST: Automated validation/verification testing</title>
      <link>http://localhost:1313/posts/2013/2013-05-22-masstest-automated-validationverification-testing/</link>
      <pubDate>Wed, 22 May 2013 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/2013/2013-05-22-masstest-automated-validationverification-testing/</guid>
      <description>&lt;p&gt;In 2009 I joined UTIA and started working on the &lt;a href=&#34;http://localhost:1313/?page_id=28&#34; title=&#34;Apple-CORE&#34;&gt;Apple-CORE&lt;/a&gt; project. The project was already in its second year, hence there had been already plenty of implementation work done. My first assignment was to prepare a test suite of simple assembly-level programs for validation of the UTLEON3 processor. The initial approach was quite naive, though: I produced a test program, observed that it does not run as intended, and reported a bug via e-mail to my colleagues. However, it quickly turned out that bugs were so proliferated that fixing one place often broke other things&amp;hellip; Running validation tests had to be automated, and the MASSTEST was born.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Asynchronous and Dynamic Virtualisation through performance ANalysis to support Concurrency Engineering (ADVANCE)</title>
      <link>http://localhost:1313/pages/2013/2013-05-08-advance/</link>
      <pubDate>Wed, 08 May 2013 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/pages/2013/2013-05-08-advance/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://www.project-advance.eu/&#34;&gt;http://www.project-advance.eu/&lt;/a&gt;, Funded by EU FP7 My involvement: &lt;em&gt;March 2012 - August 2012&lt;/em&gt;.&lt;/p&gt;&#xA;&lt;p&gt;I worked on project ADVANCE during my 6 months stay at &lt;a href=&#34;http://www.hw.ac.uk/&#34;&gt;Heriot Watt University&lt;/a&gt; in Edinburgh. This endeavour was kindly arranged and supported by &lt;a href=&#34;http://www.macs.hw.ac.uk/staff-directory/sven-bodo-scholz.htm&#34;&gt;prof. Scholz&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;In ADVANCE the project goal was to develop general methods for optimization of parallel systems, composed of computing &lt;em&gt;boxes&lt;/em&gt; and communication streams, connected in a network. System infrastructure would observe execution in boxes, gather statistics, and construct a model of the system. Based on the model the system would automatically optimize placement of boxes on compute nodes (processor cores).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Architecture Paradigms and Programming Languages for Efficient programming of multiple CORES (Apple-CORE)</title>
      <link>http://localhost:1313/pages/2013/2013-05-07-apple-core/</link>
      <pubDate>Tue, 07 May 2013 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/pages/2013/2013-05-07-apple-core/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://www.apple-core.info/&#34;&gt;http://www.apple-core.info/&lt;/a&gt;, Funded by EU, FP7-ICT-215215. My involvement: &lt;em&gt;August 2009 - January 2011&lt;/em&gt;.&lt;/p&gt;&#xA;&lt;p&gt;When I started my Ph.D. study in 2009 the first project I worked on was &lt;a href=&#34;http://www.apple-core.info/&#34;&gt;Apple-CORE&lt;/a&gt;. Our research group in UTIA was tasked with developing an FPGA prototype of a micro-threading (~multi-threading) processor based on the specification provided by project partners. The processor that we developed is called &lt;strong&gt;UTLEON3&lt;/strong&gt;. It is based on the &lt;a href=&#34;http://www.gaisler.com/index.php/products/processors/leon3?task=view&amp;amp;id=13&#34;&gt;LEON3&lt;/a&gt; from &lt;a href=&#34;http://www.gaisler.com/&#34;&gt;Aeroflex Gaisler&lt;/a&gt;, a commercial open-source implementation of the SPARCv8 RISC architecture. UTLEON3 was &lt;a href=&#34;http://sp.utia.cz/index.php?ids=utleon3&#34;&gt;released as an open-source&lt;/a&gt; under the GPL license as a supplement to &lt;a href=&#34;http://www.springer.com/engineering/circuits+%26+systems/book/978-1-4614-2409-3&#34;&gt;our book&lt;/a&gt; about the implementation.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Projects</title>
      <link>http://localhost:1313/pages/2013/2013-05-07-projects/</link>
      <pubDate>Tue, 07 May 2013 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/pages/2013/2013-05-07-projects/</guid>
      <description>&lt;p&gt;Projects, mostly home-brew:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://www.jsykora.info/x65-8-16-bit-computer/&#34;&gt;2023-ongoing: X65 8/16-bit computer&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;http://localhost:1313/vfd-watch-v2-1/&#34;&gt;2019 DIY VFD-Watch v2.1&lt;/a&gt; (finished)&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://www.jsykora.info/analog-curve-tracer/&#34;&gt;2019 DIY Analog Curve Tracer&lt;/a&gt; (finished)&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;http://www.jsykora.info/?page_id=328&#34; title=&#34;PIP-Watch&#34;&gt;2014 DIY PIP-Watch&lt;/a&gt; (never to be finished)&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;http://www.jsykora.info/?page_id=240&#34; title=&#34;Talking Clock&#34;&gt;2010 DIY Talking Clock&lt;/a&gt; (finished)&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;http://www.jsykora.info/?page_id=46&#34; title=&#34;SMECY&#34;&gt;2013 SMECY&lt;/a&gt; (&lt;em&gt;February 2011 – January 2013&lt;/em&gt;)&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;http://www.jsykora.info/?page_id=62&#34; title=&#34;ADVANCE&#34;&gt;2012 ADVANCE&lt;/a&gt; (&lt;em&gt;March 2012 – August 2012&lt;/em&gt;)&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;http://www.jsykora.info/?page_id=28&#34; title=&#34;Apple-CORE&#34;&gt;2011 Apple-CORE&lt;/a&gt; (&lt;em&gt;August 2009 – January 2011&lt;/em&gt;)&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
    <item>
      <title>Smart Multicore Embedded SYstems (SMECY)</title>
      <link>http://localhost:1313/pages/2013/2013-05-07-smecy/</link>
      <pubDate>Tue, 07 May 2013 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/pages/2013/2013-05-07-smecy/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://www.smecy.eu/&#34;&gt;http://www.smecy.eu/&lt;/a&gt; , Funded by EU Artemis JU 100230. My involvement: &lt;em&gt;February 2011 - January 2013&lt;/em&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Project SMECY was the second research project I worked on, right after the &lt;a href=&#34;http://www.jsykora.info/?page_id=28&#34; title=&#34;Apple-CORE&#34;&gt;Apple-CORE&lt;/a&gt; has ended. SMECY focused on developing tools for programming large multicore systems.&lt;/p&gt;&#xA;&lt;p&gt;In SMECY our task in UTIA was to augment existing FPGA-based accelerator platform and make it available to project partners so that they will create &lt;em&gt;parallelizing&lt;/em&gt; compilers from higher languages. We closely cooperated with our industrial partner &lt;a href=&#34;http://www.cip.cz/&#34;&gt;CIP plus&lt;/a&gt; to develop a demo application: an FPGA-based board with a camera module and with an embedded system for live video motion detection.&lt;/p&gt;</description>
    </item>
    <item>
      <title>About the Author</title>
      <link>http://localhost:1313/pages/2013/2013-05-06-welcome/</link>
      <pubDate>Mon, 06 May 2013 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/pages/2013/2013-05-06-welcome/</guid>
      <description>&lt;p&gt;You may contact me at:&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.jsykora.info/wp-content/uploads/2013/05/jara-email.png&#34;&gt;&lt;img src=&#34;images/jara-email.png&#34; alt=&#34;jara-email&#34;&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Publications</title>
      <link>http://localhost:1313/pages/2013/2013-05-06-publications/</link>
      <pubDate>Mon, 06 May 2013 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/pages/2013/2013-05-06-publications/</guid>
      <description>&lt;h2 id=&#34;phd-thesis&#34;&gt;Ph.D. Thesis&lt;/h2&gt;&#xA;&lt;p&gt;See &lt;a href=&#34;https://www.jsykora.info/thesis/&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;books&#34;&gt;Books&lt;/h2&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://www.springer.com/engineering/circuits+%26+systems/book/978-1-4614-2409-3&#34;&gt;&lt;strong&gt;UTLEON3: Exploring Fine-Grain Multi-Threading in FPGAs&lt;/strong&gt;&lt;/a&gt;. Martin Daněk, Leoš Kafka, Lukáš Kohout, Jaroslav Sýkora, Roman Bartosinski. Monography, 237 pages. ISBN 978-1461424093. Springer, (New York 2012) Circuits &amp;amp; Systems, 2012.&lt;/p&gt;&#xA;&lt;h2 id=&#34;journal-papers&#34;&gt;Journal Papers&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;Hardware Support for Fine-Grain Multi-Threading in LEON3&lt;/strong&gt;. &lt;em&gt;Martin Daněk, Leoš Kafka, Lukáš Kohout, Jaroslav Sýkora&lt;/em&gt;. In Carpathian Journal of Electronic and Computer Engineering, Volume 4, Number 1 – 2011. ISSN 1844-9689.&lt;/p&gt;&#xA;&lt;h2 id=&#34;conference-papers&#34;&gt;Conference Papers&lt;/h2&gt;&#xA;&lt;h3 id=&#34;2013&#34;&gt;2013&lt;/h3&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://localhost:1313/p/ddecs2013-ftl.pdf&#34;&gt;&lt;strong&gt;Composing Data-driven Circuits Using Handshake in the Clock-Synchronous Domain&lt;/strong&gt;.&lt;/a&gt;, [&lt;a href=&#34;http://localhost:1313/p/ftl-poster2-v5.2.pdf&#34;&gt;Poster&lt;/a&gt;] &lt;em&gt;Jaroslav Sýkora&lt;/em&gt;. In Proceedings of the 2013 IEEE 16th International Symposium on Design and Diagnostics of Electronic Circuits and Systems (DDECS), 2013. IEEE CS, 2013, s. 211-214, ISBN 978-1-4673-6133-0&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
