From mboxrd@z Thu Jan  1 00:00:00 1970
From: Craig Setera <craigjunk@setera.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Updates to u-boot script for Raspberry Pi 4b devices
Date: Sun, 22 Sep 2024 15:01:40 -0500
Message-ID: <6bdcbd8c-d598-402d-ae11-bf1be906bb27@setera.org>
In-Reply-To: <d18a71c1-d6d0-42ef-bff9-ed3f0eec883a@setera.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5286043615501243271=="
List-Id: <development.lists.ipfire.org>

--===============5286043615501243271==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Today I tried to use this process to upgrade to latest core version 
(188) and the resulting card is not properly working, despite this 
process working for the last couple of releases. Looking in Git, it 
doesn't seem like there were other boot.cmd changes that might have 
caused issues, so thought I'd check here to see if anyone knew what 
might have changed in the most recent release relative to u-boot on RPi?

Thanks for any insights.

Craig

On 6/16/24 10:28 AM, Craig Setera wrote:
> FWIW... I just used my updated u-boot script to update the image for 
> 186 and went through the setup process using serial console for my 
> Raspberry Pi.  My process:
>
> * Download backup from IPFire
> * Flash new image to SD Card
> * Update u-boot script
> * Make new image using script
> * Boot and do initial setup via serial console
> * Login to web admin and restore backup
>
> Even though this is a few more steps than just doing an "in place" 
> upgrade, I actually like that I am keeping the previous SD card and 
> can swap back if something goes wrong.
>
> Craig
>

--===============5286043615501243271==--