
    

    <?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://ocw.cs.pub.ro/courses/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://ocw.cs.pub.ro/courses/feed.php">
        <title>CS Open CourseWare ass:labs-2025:03:tasks</title>
        <description></description>
        <link>http://ocw.cs.pub.ro/courses/</link>
        <image rdf:resource="http://ocw.cs.pub.ro/courses/lib/tpl/arctic/images/favicon.ico" />
       <dc:date>2026-04-08T14:25:51+03:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://ocw.cs.pub.ro/courses/ass/labs-2025/03/tasks/01?rev=1754474195&amp;do=diff"/>
                <rdf:li rdf:resource="http://ocw.cs.pub.ro/courses/ass/labs-2025/03/tasks/02?rev=1754492627&amp;do=diff"/>
                <rdf:li rdf:resource="http://ocw.cs.pub.ro/courses/ass/labs-2025/03/tasks/03?rev=1754499842&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://ocw.cs.pub.ro/courses/lib/tpl/arctic/images/favicon.ico">
        <title>CS Open CourseWare</title>
        <link>http://ocw.cs.pub.ro/courses/</link>
        <url>http://ocw.cs.pub.ro/courses/lib/tpl/arctic/images/favicon.ico</url>
    </image>
    <item rdf:about="http://ocw.cs.pub.ro/courses/ass/labs-2025/03/tasks/01?rev=1754474195&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-08-06T12:56:35+03:00</dc:date>
        <title>01. Automatically booting our Linux</title>
        <link>http://ocw.cs.pub.ro/courses/ass/labs-2025/03/tasks/01?rev=1754474195&amp;do=diff</link>
        <description>01. Automatically booting our Linux

You are probably be tired of using u-boot CLI to load the Linux FIT uImage into RAM and booting it manually.
Surely, there must be something to be done to automate this... and you're right! Let's learn to do this!</description>
    </item>
    <item rdf:about="http://ocw.cs.pub.ro/courses/ass/labs-2025/03/tasks/02?rev=1754492627&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-08-06T18:03:47+03:00</dc:date>
        <title>02. Enabling networking on iMX93</title>
        <link>http://ocw.cs.pub.ro/courses/ass/labs-2025/03/tasks/02?rev=1754492627&amp;do=diff</link>
        <description>02. Enabling networking on iMX93

Notice that the FRDM-iMX93 has two Ethernet ports. But if you boot your previous Buildroot distro and try to see the available network: ip link show, notice that they are missing. Instead, you'll only have the loopback interface lo.</description>
    </item>
    <item rdf:about="http://ocw.cs.pub.ro/courses/ass/labs-2025/03/tasks/03?rev=1754499842&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-08-06T20:04:02+03:00</dc:date>
        <title>03. Writing &amp; packaging a GPIO app on Buildroot</title>
        <link>http://ocw.cs.pub.ro/courses/ass/labs-2025/03/tasks/03?rev=1754499842&amp;do=diff</link>
        <description>03. Writing &amp; packaging a GPIO app on Buildroot

An embedded device is designed to interface with the physical world via sensors and actuators.

The most common way to do this is by means of Generic Purpose Input/Output (GPIO): electrical connectors exposed by the SoC that can be freely controlled by software to be either input or output, read/write a logical signal (0-3.3/5V) with whatever they're connected too.</description>
    </item>
</rdf:RDF>
