On Friday, 23 April 2021 at 15:49, Dennis Gilmore wrote:
> On Fri, Apr 23, 2021 at 7:14 AM Dominik 'Rathann' Mierzejewski
> <dominik@greysector.net> wrote:
> >
> > On Thursday, 22 April 2021 at 18:07, Paul Whalen wrote:
> > >
> > > Hi Everyone,
> > >
> > > Please help to test the Fedora 34 RC on your favourite ARM or AArch64
> > > device, and add your results to the Fedora Wiki:
> > >
> > > https://fedoraproject.org/wiki/Test_Results:Fedora_34_RC_1.1_Summary
> > >
> > > All testing is greatly appreciated!
> >
> > I'd be happy to test on my Pinebook Pro, but I'd appreciate some
> > instructions on how to flash the U-Boot SPI image (idbloader.spi?)
> > onto the SPI. Peter pointed me to
> > https://marcin.juszkiewicz.com.pl/2020/06/17/ebbr-on-rockpro64/ on IRC,
> > but it's for a different board. How can I find out the correct address
> > for load and sf update/write commands?
>
> There is no need to know the memory locations, there are variables
> defined for that. On my RockPro64 I ran the following
>
> sf probe
> load mmc 1:1 ${fdt_addr_r} idbloader.spi
> sf update ${fdt_addr_r} 0 ${filesize}
> load mmc 1:1 ${fdt_addr_r} u-boot.itb
> sf update ${fdt_addr_r} 60000 ${filesize}
>
> reset and it booted off of SPI,I created the sdcard that I booted off
> and contained u-boot by running
>  spi-flashing-disk --media=/dev/sda --target rockpro64-rk3399
>
> my desktop has nvme drives so the first USB drive shows up as /dev/sda
>
> you may need to use mmc info to get the right device or run
> ls mmc 0:1
> ls mmc 1:1
> until you see the device that contains the right bits, then set the
> correct device to load from

Thanks, I actually knew as much. How can I make sure that the
${fdt_addr_r} variable contains the correct address, though?

Regards,
Dominik
--
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
        -- from "Collected Sayings of Muad'Dib" by the Princess Irulan