8
« Last Post by buzz53 on January 16, 2025, 04:37:57 pm »
Hi Ashley, many thanks for that. I was at a loose end today so investigated a bit further and it seems it is quite easily fixed with basic IT skills. I was on the right track yesterday, but the reason the standard fix didn’t work is that PAW uses the old NOOBS installer which I wasn't familiar with and which doesn’t directly load the operating system. This means you need to replace the old firmware files in 2 different places. In case it’s of interest to anybody else, this is what I did :
Get a copy of a recent Raspbery Pi distribution – I used Bookworm 32 bit. You will need 9 files from the distro root: bootcode.bin, start*.elf (4 files) and fixup*.dat (4 files). Ignore the ones with "4" in the filename - these are for Pi model 4.
Take the SD card from a working PAW installation and mount it on a Windows PC (other OS's are available but don't ask me!) using an adapter. You should see 2 volumes: BOOT and RECOVERY
1) In the BOOT volume root, you will see the old versions of the above 9 files. Overwrite them with the new ones.
The additional steps, that I was missing yesterday are:
2) In the RECOVERY volume root, overwrite bootcode.bin with the new version.
3) In the RECOVERY volume root, delete recovery.elf, copy in the new start.elf and rename it recovery.elf.
That’s it! If you are starting with a brand new PAW card that has not yet been run, and you don’t have an old version Pi in which you can do so in order to set everything up, then it’s a bit more fiddly but you get the idea.
I think Lee could probably update the official image quite easily to reflect this.
Kind regards, Alan