Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 8621

Troubleshooting • Issue getting new Rpi5 to boot of old Rpi5 SD card

$
0
0
BACKGROUND

I am trying to trouble shoot a python project which was going on a old Rpi5 but then I had to replace the hardware and the old SD card wouldnt boot, and the project doesn't run normally on a fresh install from my Repo - it drops samples.

INTRODUCTION

I am using a RPi5 8Gb loading bookworm from a SD to process streamed data from a Software Defined Radio (SDR connected via USB) in a python project. All was working very nicely until my Rpi5 8Gb died and I had to get a new one.

I assumed I could insert the old SD card into the new RPi5 and be up and running again, but this has not been the case.

REPLACEMENT RPI5

Since I am doing lots of read/write operations to a database when I got the new Rpi5 I decided to use the Pimoroni card to add a M.2 SSD and it is waaay faster in sequential and random r/w operations. During the install of the Pimoroni I upgraded the eeprom.

Then when I cloned my github project to the Rpi and ran the code I started to get LOTS of dropped samples.

htop showed I still had plenty of RAM and CPU power left.

STEPS TRIED TO FIX

I decided to try to boot the old working SD card. The boot process fails with:

[ 0.543645] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---

The only link I can find to this error is here : https://hub.mender.io/t/asynchronous-se ... issue/7275 which talks alot about the BCM2712d0.dtbo file being missing?

and here : https://github.com/agherzan/meta-raspbe ... ssues/1394 which has a smilar discussion.

The link above talks about editing editing local.conf, quote After adding RPI_KERNEL_DEVICETREE_OVERLAYS:append = " overlays/bcm2712d0.dtbo" to my local.conf, the kernel panic has been fixed. Tested on the scarthgap branch.

I noticed bcm2712.dtbo seems to be missing so I have tried to add a copy of bcm2712.dtbo from a working Rpi to the folder /boot/formware/overlays or should it be boot/overlays or both?

If I do this however I just get a - when I try to boot and no output.

I also note that the working SD has in /boot/firmware :

al@rasp:/boot/firmware $ ls -l |grep bcm2712
-rwxr-xr-x 1 root root 78235 Mar 20 05:49 bcm2712d0-rpi-5-b.dtb
-rwxr-xr-x 1 root root 78227 Mar 20 05:49 bcm2712-d-rpi-5-b.dtb
-rwxr-xr-x 1 root root 78187 Mar 20 05:49 bcm2712-rpi-500.dtb
-rwxr-xr-x 1 root root 78231 Mar 20 05:49 bcm2712-rpi-5-b.dtb
-rwxr-xr-x 1 root root 78873 Mar 20 05:49 bcm2712-rpi-cm5-cm4io.dtb
-rwxr-xr-x 1 root root 78939 Mar 20 05:49 bcm2712-rpi-cm5-cm5io.dtb
-rwxr-xr-x 1 root root 78914 Mar 20 05:49 bcm2712-rpi-cm5l-cm4io.dtb
-rwxr-xr-x 1 root root 78980 Mar 20 05:49 bcm2712-rpi-cm5l-cm5io.dtb
But if I mount the old non working SD card I can only find /media/al/rootfs/boot/firmware which is empty.

I am wondering if I should downgrade the eeprom to a old version since there seems to be quite a few file system differences between the odl and new installations?

How do I get the old SD card to boot?

Statistics: Posted by bigal.nz — Sun Apr 06, 2025 1:21 am



Viewing all articles
Browse latest Browse all 8621

Trending Articles