<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Turing on Nico Maas</title>
        <link>https://www.nico-maas.de/tags/turing/</link>
        <description>Recent content in Turing on Nico Maas</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-us</language>
        <lastBuildDate>Fri, 13 Sep 2024 16:45:45 +0000</lastBuildDate><atom:link href="https://www.nico-maas.de/tags/turing/index.xml" rel="self" type="application/rss+xml" /><item>
            <title>Install a bootloader onto Turing RK1 eMMC memory</title>
            <link>https://www.nico-maas.de/posts/2024-09-13-install-a-bootloader-onto-turing-rk1-emmc-memory/</link>
            <pubDate>Fri, 13 Sep 2024 16:45:45 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2024-09-13-install-a-bootloader-onto-turing-rk1-emmc-memory/</guid>
            <description>&lt;p&gt;The Turing RK1 is a new Compute Module, made for the Turing Pi 2 board and with compability to the Nvidia Jetson cards in mind. While the board has some impressive specs ( &lt;a class=&#34;link&#34; href=&#34;https://docs.turingpi.com/docs/turing-rk1-specs-and-io-ports&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;https://docs.turingpi.com/docs/turing-rk1-specs-and-io-ports&lt;/a&gt; ) it had one small issue: The used Rockchip RK3588 needed a bootloader on its eMMC to be able to boot from an attached NVMe drive. As no isolated bootloader was available, most people flashed a whole OS onto the eMMC - just to be able to use the attched NVMe drive. This process can take quite a while via the Turing Pi 2 board ( e.g. 60 - 90 minutes: &lt;a class=&#34;link&#34; href=&#34;https://docs.turingpi.com/docs/turing-rk1-flashing-os&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;https://docs.turingpi.com/docs/turing-rk1-flashing-os&lt;/a&gt; ) it was never a good option.&lt;/p&gt;</description>
        </item></channel>
</rss>
