Date: Thu, 9 Jan 2025 11:42:17 +0100 (CET) From: Ronald Klop <ronald-lists@klop.ws> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-arm@freebsd.org, "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Subject: Re: Raspbery Pi support (release notes/wiki page) update? Message-ID: <1284671542.924.1736419337261@localhost> In-Reply-To: <68B36F4A-76AD-4CEC-ACBA-3EEF6863BB04@yahoo.com> References: <668r286o-584q-616o-5nq3-0233r3259qsr@yvfgf.mnoonqbm.arg> <E4887386-91C4-4B59-A119-D11C14F4991B@yahoo.com> <7sp0np90-0rnn-n327-qps0-358493p411rs@yvfgf.mnoonqbm.arg> <68B36F4A-76AD-4CEC-ACBA-3EEF6863BB04@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_923_316014044.1736419337122 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi Mark, I just noticed an RPI5 with 16GB RAM became available [1]. Which triggers my interest in an upgrade of my current RPI4/8GB used to build aarch64 ports. I see that you have quite some experience in setting up the RPI5 with knowledge expressed in several emails. Would you mind to setup a https://wiki.freebsd.org/arm/RPI5 page and collect your knowledge/experience there? When RPI5 works well in the future we can then merge the information into https://wiki.freebsd.org/arm/Raspberry%20Pi. Regards, Ronald. [1] https://www.raspberrypi.com/news/16gb-raspberry-pi-5-on-sale-now-at-120/ Van: Mark Millard <marklmi@yahoo.com> Datum: maandag, 2 december 2024 22:43 Aan: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> CC: freebsd-arm@freebsd.org Onderwerp: Re: Raspbery Pi support (release notes/wiki page) update? > > On Dec 2, 2024, at 12:43, Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net> wrote: > > > On Wed, 27 Nov 2024, Mark Millard wrote: > > > > I assume that all also means there's no way on FreeBSD to update the > > eeprom contents on the RPi4/5[1] (contents replaced the bootcode.bin on > > older PIs.) > > I update the EEPROM's via booting a standard RaspiOS64 (my abbreviation). > That includes updating some defaults/definitions that can be stored in > the EEPROM. (For example, I enable more debug output than is the > default. That includes enabling BOOT_UART .) > > There are commands like: sudo -E rpi-eeprom-config --edit > > I'm not aware of FreeBSD having any such software, even via the ports > tree. > > However, the description of the command is: > > QUOTE > Editing the current bootloader configuration > The following command loads the current bootloader configuration into a text editor. When the editor is closed, rpi-eeprom-configapplies the updated configuration to latest available bootloader release and uses rpi-eeprom-update to schedule an update when the system is rebooted: > END QUOTE > > In essence doing a (after the edit): sudo rpi-eeprom-update -a > > I do not have the references handy, but as I remember, this puts a > file in the msdosfs that, if found at (re)boot, is automatically > used to do the EEPROM update, well before U-boot is involved. > > So: putting a correctly formed file in the right place with the > right name for a reboot to pick up is basic to the EEPROM update > operation. > > The EEPROM contains the bootloader. The RPi5B has less that goes > in the msdosfs (on the microsd card I use to boot the RPi5 via > a separate USB3 drive): > > # find /RPi5-edk2/ -print > /RPi5-edk2/ > /RPi5-edk2/RPI_EFI.fd > /RPi5-edk2/config.txt > /RPi5-edk2/bcm2712-rpi-5-b.dtb > > Nothing analogous to start4*.elf or fixup4*.dat is involved. > > # more /RPi5-edk2/config.txt > armstub=RPI_EFI.fd > device_tree_address=0x1f0000 > device_tree_end=0x210000 > > # Force 32 bpp framebuffer allocation. > framebuffer_depth=32 > > # Disable compensation for displays with overscan. > disable_overscan=1 > > # Force maximum USB power regardless of the power supply. > usb_max_current_enable=1 > > # Force maximum CPU speed. > force_turbo=1 > > # > # Local additions: > enable_uart=1 > uart_2ndstage=1 > dtdebug=1 > disable_commandline_tags=1 > # > [pi5] > over_voltage_delta=100000 > arm_freq=2600 > [all] > > > /bz > > > > > > [1] https://github.com/raspberrypi/rpi-eeprom/tree/master/ > > Releases: https://github.com/raspberrypi/rpi-eeprom/releases > > Tagged: https://github.com/raspberrypi/rpi-eeprom/tags > > (More is tagged than is eventually declared to also be a > release.) > > === > Mark Millard > marklmi at yahoo.com > > > > > ------=_Part_923_316014044.1736419337122 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <html><head></head><body>Hi Mark,<br> <br> I just noticed an RPI5 with 16GB RAM became available [1]. Which triggers my interest in an upgrade of my current RPI4/8GB used to build aarch64 ports.<br> <br> I see that you have quite some experience in setting up the RPI5 with knowledge expressed in several emails.<br> Would you mind to setup a <a href="https://wiki.freebsd.org/arm/RPI5">https://wiki.freebsd.org/arm/RPI5</a>; page and collect your knowledge/experience there?<br> <br> When RPI5 works well in the future we can then merge the information into <a href="https://wiki.freebsd.org/arm/Raspberry%20Pi">https://wiki.freebsd.org/arm/Raspberry%20Pi</a>.<br>; <br> Regards,<br> Ronald.<br> <br> [1] <a href="https://www.raspberrypi.com/news/16gb-raspberry-pi-5-on-sale-now-at-120/">https://www.raspberrypi.com/news/16gb-raspberry-pi-5-on-sale-now-at-120/</a><br>; <p><strong>Van:</strong> Mark Millard <marklmi@yahoo.com><br> <strong>Datum:</strong> maandag, 2 december 2024 22:43<br> <strong>Aan:</strong> "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net><br> <strong>CC:</strong> freebsd-arm@freebsd.org<br> <strong>Onderwerp:</strong> Re: Raspbery Pi support (release notes/wiki page) update?</p> <blockquote style="padding-right: 0px; padding-left: 5px; margin-left: 5px; border-left: #000000 2px solid; margin-right: 0px"> <div class="MessageRFC822Viewer" id="P"> <div class="TextPlainViewer" id="P.P">On Dec 2, 2024, at 12:43, Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net> wrote:<br> <br> > On Wed, 27 Nov 2024, Mark Millard wrote:<br> ><br> > I assume that all also means there's no way on FreeBSD to update the<br> > eeprom contents on the RPi4/5[1] (contents replaced the bootcode.bin on<br> > older PIs.)<br> <br> I update the EEPROM's via booting a standard RaspiOS64 (my abbreviation).<br> That includes updating some defaults/definitions that can be stored in<br> the EEPROM. (For example, I enable more debug output than is the<br> default. That includes enabling BOOT_UART .)<br> <br> There are commands like: sudo -E rpi-eeprom-config --edit<br> <br> I'm not aware of FreeBSD having any such software, even via the ports<br> tree.<br> <br> However, the description of the command is:<br> <br> QUOTE<br> Editing the current bootloader configuration<br> The following command loads the current bootloader configuration into a text editor. When the editor is closed, rpi-eeprom-configapplies the updated configuration to latest available bootloader release and uses rpi-eeprom-update to schedule an update when the system is rebooted:<br> END QUOTE<br> <br> In essence doing a (after the edit): sudo rpi-eeprom-update -a<br> <br> I do not have the references handy, but as I remember, this puts a<br> file in the msdosfs that, if found at (re)boot, is automatically<br> used to do the EEPROM update, well before U-boot is involved.<br> <br> So: putting a correctly formed file in the right place with the<br> right name for a reboot to pick up is basic to the EEPROM update<br> operation.<br> <br> The EEPROM contains the bootloader. The RPi5B has less that goes<br> in the msdosfs (on the microsd card I use to boot the RPi5 via<br> a separate USB3 drive):<br> <br> # find /RPi5-edk2/ -print<br> /RPi5-edk2/<br> /RPi5-edk2/RPI_EFI.fd<br> /RPi5-edk2/config.txt<br> /RPi5-edk2/bcm2712-rpi-5-b.dtb<br> <br> Nothing analogous to start4*.elf or fixup4*.dat is involved.<br> <br> # more /RPi5-edk2/config.txt<br> armstub=RPI_EFI.fd<br> device_tree_address=0x1f0000<br> device_tree_end=0x210000<br> <br> # Force 32 bpp framebuffer allocation.<br> framebuffer_depth=32<br> <br> # Disable compensation for displays with overscan.<br> disable_overscan=1<br> <br> # Force maximum USB power regardless of the power supply.<br> usb_max_current_enable=1<br> <br> # Force maximum CPU speed.<br> force_turbo=1<br> <br> #<br> # Local additions:<br> enable_uart=1<br> uart_2ndstage=1<br> dtdebug=1<br> disable_commandline_tags=1<br> #<br> [pi5]<br> over_voltage_delta=100000<br> arm_freq=2600<br> [all]<br> <br> > /bz<br> ><br> ><br> > [1] <a href="https://github.com/raspberrypi/rpi-eeprom/tree/master/">https://github.com/raspberrypi/rpi-eeprom/tree/master/</a><br>; <br> Releases: <a href="https://github.com/raspberrypi/rpi-eeprom/releases">https://github.com/raspberrypi/rpi-eeprom/releases</a><br>; <br> Tagged: <a href="https://github.com/raspberrypi/rpi-eeprom/tags">https://github.com/raspberrypi/rpi-eeprom/tags</a><br>; <br> (More is tagged than is eventually declared to also be a<br> release.)<br> <br> ===<br> Mark Millard<br> marklmi at yahoo.com<br> <br> </div> <hr></div> </blockquote> <br> </body></html> ------=_Part_923_316014044.1736419337122--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1284671542.924.1736419337261>