Thank you all for engaging into the conversation!
Exactly, I tried with all the instructions to upgrading the firmware in our img using the Old Pi, but that did not solve the boot issues using the New Pi.
I have included the `vcgencmd version` output together with a summary of the commands run in the code blocks below. I have also added a description of what I tried. Please also find attached the terminal output following the full upgrading process in the first section using our Custom IMG on the Old RPi here: https://pastebin.com/0bchMFde.
I have two RPi:
- Old Pi: RPi 3B+ R5 Rev 1.3
- New Pi: RPi 3B+ R9 Rev 1.4
Using our 'Custom IMG' based on Stretch OS:
This has worked perfectly fine on the Old Pis until we received the New Pi with the revised R9 hardware. These are some of the things I tried to make the Custom IMG boot on the New RPi:
- Update the firmware as instructed in the documentation: https://www.raspberrypi.com/documentati ... e-software and 'Upgrading Pi Firmware' whitepaper. I run these commands on the Old Pi with the Custom IMG loaded.
- Replacing the Boot Files (startup*.elf, fixup*.dat and bootcode.bin) with the new firmware boot files from a clean Bookworm OS install as well from the firmware github repo.
- Replacing the config.txt file to that one of the new firmware files.
None of these has worked, so I was not able to make our Custom IMG boot successfully on the New RPi with the revised hardware. Every time, the result has been the Error flash code of 4 long + 7 short.
Using a Clean IMG of Stretch OS: (from https://downloads.raspberrypi.org/raspb ... h-lite.zip)
- The New RPi does not boot with the unmodified Clean IMG.
- However, the New RPi boots successfully when I replace the Boot Files on a Clean IMG of Stretch OS. In this case, both Old and New RPis boot successfully.
Therefore, the revised hardware is compatible with the Stretch OS, but will not boot on our Custom IMG.
Thanks a lot for you help!
Report output of "vcgencmd version" on the working and not working system.
It sounds like replacing the firmware files was not successful.
Exactly, I tried with all the instructions to upgrading the firmware in our img using the Old Pi, but that did not solve the boot issues using the New Pi.
I have included the `vcgencmd version` output together with a summary of the commands run in the code blocks below. I have also added a description of what I tried. Please also find attached the terminal output following the full upgrading process in the first section using our Custom IMG on the Old RPi here: https://pastebin.com/0bchMFde.
I have two RPi:
- Old Pi: RPi 3B+ R5 Rev 1.3
- New Pi: RPi 3B+ R9 Rev 1.4
Using our 'Custom IMG' based on Stretch OS:
This has worked perfectly fine on the Old Pis until we received the New Pi with the revised R9 hardware. These are some of the things I tried to make the Custom IMG boot on the New RPi:
- Update the firmware as instructed in the documentation: https://www.raspberrypi.com/documentati ... e-software and 'Upgrading Pi Firmware' whitepaper. I run these commands on the Old Pi with the Custom IMG loaded.
- Replacing the Boot Files (startup*.elf, fixup*.dat and bootcode.bin) with the new firmware boot files from a clean Bookworm OS install as well from the firmware github repo.
- Replacing the config.txt file to that one of the new firmware files.
None of these has worked, so I was not able to make our Custom IMG boot successfully on the New RPi with the revised hardware. Every time, the result has been the Error flash code of 4 long + 7 short.
Code:
[OLD RPi - CUSTOM IMG - NO CHANGES]$ vcgencmd versionAug 15 2019 12:06:42 Copyright (c) 2012 Broadcomversion 0e6daa5106dd4164474616408e0dc24f997ffcf3 (clean) (release) (start)$ uname -aLinux 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux$ sudo apt update$ sudo apt full-upgrade$ uname -aLinux nodename 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux$ vcgencmd versionAug 15 2019 12:06:42 Copyright (c) 2012 Broadcomversion 0e6daa5106dd4164474616408e0dc24f997ffcf3 (clean) (release) (start)$ sudo rpi-update[First try fails at the end, but second updates the firmware successfully. See details on the attached txt with the terminal output]$ sudo reboot now$ uname -aLinux nodename 6.6.42-v7+ #1787 SMP Thu Jul 25 17:42:40 BST 2024 armv7l GNU/Linux$ vcgencmd versionVCHI initialization failed$ sudo vcgencmd versionJul 25 2024 15:01:17 Copyright (c) 2012 Broadcomversion 8a2829a2ff4d4808cc14e10de7068e6afb45c96d (tainted) (release) (start)[REPLACED BOOT FILES FOR THOSE FOUND IN BOOKWORKM 32-BIT CLEAN INSTALL]$ uname -aLinux nodename 6.6.42-v7+ #1787 SMP Thu Jul 25 17:42:40 BST 2024 armv7l GNU/Linux$ sudo vcgencmd versionMay 24 2024 15:31:28 Copyright (c) 2012 Broadcomversion 4942b7633c0ff1af1ee95a51a33b56a9dae47529 (clean) (release) (start)Using a Clean IMG of Stretch OS: (from https://downloads.raspberrypi.org/raspb ... h-lite.zip)
- The New RPi does not boot with the unmodified Clean IMG.
- However, the New RPi boots successfully when I replace the Boot Files on a Clean IMG of Stretch OS. In this case, both Old and New RPis boot successfully.
Therefore, the revised hardware is compatible with the Stretch OS, but will not boot on our Custom IMG.
Code:
[OLD RPI - CLEAN IMG STRETCH OS -]$ vcgencmd versionMar 27 2019 15:45:53 Copyright (c) 2012 Broadcomversion 2e98b31d18547962e564bdf88e57b3df7085c29b (clean) (release) (start)$ uname -aLinux raspberrypi 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l GNU/Linux$ sudo rpi-update[same as above, first try failed. Second try succeed. See attached txt for details since the same exact output was obtained in this case]$ sudo reboot now$ uname -aLinux raspberrypi 6.6.42-v7+ #1787 SMP Thu Jul 25 17:42:40 BST 2024 armv7l GNU/Linux$ sudo vcgencmd versionJul 25 2024 15:01:17 Copyright (c) 2012 Broadcomversion 8a2829a2ff4d4808cc14e10de7068e6afb45c96d (tainted) (release) (start)Code:
[NEW RPI BOOTS OK - CLEAN IMG STRETCH OS UPDATED FW]$ uname -aLinux raspberrypi 6.6.42-v7+ #1787 SMP Thu Jul 25 17:42:40 BST 2024 armv7l GNU/Linuxpi@raspberrypi:~ $ sudo vcgencmd versionJul 25 2024 15:01:17 Copyright (c) 2012 Broadcomversion 8a2829a2ff4d4808cc14e10de7068e6afb45c96d (tainted) (release) (start)Thanks a lot for you help!
Statistics: Posted by gasparHs82 — Thu Aug 01, 2024 10:07 am