<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>TuringPi 2 on Nico Maas</title>
        <link>https://www.nico-maas.de/tags/turingpi-2/</link>
        <description>Recent content in TuringPi 2 on Nico Maas</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-us</language>
        <lastBuildDate>Sat, 16 Nov 2024 19:39:50 +0000</lastBuildDate><atom:link href="https://www.nico-maas.de/tags/turingpi-2/index.xml" rel="self" type="application/rss+xml" /><item>
            <title>Turing Pi 2 - Retrofitting an EMC2301 Fancontroller</title>
            <link>https://www.nico-maas.de/posts/2024-11-16-turing-pi-2-retrofitting-an-emc2301-fancontroller/</link>
            <pubDate>Sat, 16 Nov 2024 19:39:50 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2024-11-16-turing-pi-2-retrofitting-an-emc2301-fancontroller/</guid>
            <description>&lt;p&gt;The Turing Pi 2 (v.2.4) has actually some secrets that just start to get uncovered. Looking closely at the board, you will find the red marked area with what seems to be an unpopulated 4-pin fan header (J16) and an unpopulated IC spot (U109).&lt;/p&gt;&#xA;&lt;p&gt;&lt;img class=&#34;gallery-image&#34; data-flex-basis=&#34;238px&#34; data-flex-grow=&#34;99&#34; height=&#34;1210&#34; loading=&#34;lazy&#34; sizes=&#34;(max-width: 767px) calc(100vw - 30px), (max-width: 1023px) 700px, (max-width: 1279px) 950px, 1232px&#34; src=&#34;https://www.nico-maas.de/posts/2024-11-16-turing-pi-2-retrofitting-an-emc2301-fancontroller/turingPi2_EMC2301_00001.jpg&#34; srcset=&#34;https://www.nico-maas.de/posts/2024-11-16-turing-pi-2-retrofitting-an-emc2301-fancontroller/turingPi2_EMC2301_00001_hu_3c7d92ff4bf2d9ce.jpg 800w, https://www.nico-maas.de/posts/2024-11-16-turing-pi-2-retrofitting-an-emc2301-fancontroller/turingPi2_EMC2301_00001.jpg 1200w&#34; width=&#34;1200&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;These spots were, as &lt;a class=&#34;link&#34; href=&#34;https://github.com/turing-machines/BMC-Firmware/pull/125&#34;  title=&#34;found out&#34;&#xA;     target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;found out&lt;/a&gt; by Sam Edwards (CFSworks) actually a place to install Molex 47053-1000 4-pin fan connector and a Microchip EMC2301 fan controller. It is not clear why they were left out of the production model, probably for cost savings, but without that the Turing Pi 2 lost a nice smooth fan controller. However, thanks to Sam Edwards work, the chip is now supported by the Turing Pi 2 BMC, so that after retrofitting, this will just work out of the box!&lt;/p&gt;</description>
        </item><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><item>
            <title>Repairing a Turing Pi 2</title>
            <link>https://www.nico-maas.de/posts/2023-12-03-repairing-a-turingpi-2/</link>
            <pubDate>Sun, 03 Dec 2023 17:56:27 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2023-12-03-repairing-a-turingpi-2/</guid>
            <description>&lt;h2 id=&#34;intro&#34;&gt;Intro&#xA;&lt;/h2&gt;&lt;p&gt;In April 2023 I finally got my Turing Pi 2 - happy to finally got it into my hands I plugged it in, headed over to the Turing Pi 2 Github ( &lt;a class=&#34;link&#34; href=&#34;https://github.com/turing-machines/BMC-Firmware&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;https://github.com/turing-machines/BMC-Firmware&lt;/a&gt; ) got myself the latest BMC firmware and started to flash it. Thats when things got wrong: The power supply coils started to screech - and seconds later I was greeted with blue smoke and a dead Turing Pi 2. The firmware update actually flashed the board into a paper weight.&lt;/p&gt;</description>
        </item></channel>
</rss>
