<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>networking on BitBanged</title><link>https://bitbanged.com/tags/networking/</link><description>Recent content in networking on BitBanged</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>utkarsh@bitbanged.com (Utkarsh Verma)</managingEditor><webMaster>utkarsh@bitbanged.com (Utkarsh Verma)</webMaster><lastBuildDate>Wed, 12 Jul 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://bitbanged.com/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>Network booting a Raspberry Pi 4</title><link>https://bitbanged.com/posts/streamlining-rpi-osdev/network-booting-a-raspberry-pi-4/</link><pubDate>Wed, 12 Jul 2023 00:00:00 +0000</pubDate><author>utkarsh@bitbanged.com (Utkarsh Verma)</author><guid>https://bitbanged.com/posts/streamlining-rpi-osdev/network-booting-a-raspberry-pi-4/</guid><description>As highlighted in the previous articles, the flashing process for a Raspberry Pi 4 is far from ideal. It demands manual involvement from the developer and this article aims to fix that. We want as little manual involvement as possible for automation purposes.
Luckily, the firmware on RPi 4 supports network booting which enables it to fetch the boot dependencies from the network, without the need of an SD card. Since the will fetched from a network share, this opens up the possibility of modifying the OS files from the development machine without needing to touch the board.</description></item></channel></rss>