Friday, September 7, 2018

[fedora-arm] Re: Fedora 29 new U-Boot/arm-trusted-firmware and Raspberry Pi firmware heads up

Did a bit more digging.

Perhaps adding update-uboot to

might make sense?  So that the steps to update uboot are clearer from
the beginning.

Fedora uses understand 'dnf update'.  Updating uboot needing an extra
step is different.

Hmmm.  Thought more about what device uboot is on, and I realize that it
may be really hard to get that right.  Like when I have uboot on my uSD
card and nothing else on it and the partitions on the sata drive. 
Assuming that the uboot device is the same as the one that contains
/boot is not always right.

I just looked at one Cubieboard2 system set up this way (OK, it is
Centos7, not Fedora2x).  The sata is /dev/sda.  The 'USB external' drive
is /dev/sdb.  I am guessing from looking in /dev that uboot is on
/dev/mmcblk0?  I looked at the beginning of the console capture, at it
does not indicate where it found uboot:

U-Boot SPL 2018.09-rc2 (Aug 14 2018 - 16:45:15 +0000)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1

U-Boot 2018.09-rc2 (Aug 14 2018 - 16:45:15 +0000) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: Cubietech Cubieboard2
I2C:   ready
DRAM:  1 GiB
Loading Environment from FAT... Unable to use mmc 0:2... HDMI connected:
 up a 1920x1080 dvi console (overscan 0x0)



On 09/07/2018 09:48 AM, Peter Robinson wrote:
> On Fri, Sep 7, 2018 at 1:41 PM Robert Moskowitz <> wrote:
>> Peter,
>> I have scanned update-uboot. I am not really all that skilled at script
>> writing, but I get the drift that you need to provide a koji image name
>> to download and get the uboot directory.
> No, you don't, that's just an option. Generally you do "dnf upgrade
> --refresh" and if a new version of U-Boot rpms get installed you would
> then run something like:
> "update-uboot --target=udoo_neo --media=/dev/mmcblk0"
> of course updating the target and the media/
>> It would seem to be 'cleaner' if the update testing repo had a uboot rpm
>> that could be installed to get all the forthcoming ubbot images? Then
>> dd from there?
> That is exactly what it does.
>> How is one to figure out which koji image to specify?
> You don't, see above.
>> Seems like a great beginning of a great tool.
>> On 09/07/2018 05:32 AM, Peter Robinson wrote:
>>> Hi All,
>>> There's a new update headed to testing for Fedora 29. It makes some
>>> adjustments to how we handle a few things, in particular the Raspberry
>>> Pi firmware:
>>> I don't expect anyone to see anything issues in particular especially
>>> for the vast majority of people that just use a SD card or HDD with
>>> their ARM device but there might be some corner cases for people with
>>> slightly more esoteric setups when they upgrade. If anyone sees any
>>> issues please open a bug [1] or reply to this or reach out on
>>> #fedora-arm. The change has been in rawhide for a little while and
>>> I've not seen any fall out there.
>>> Also the new U-Boot will have some slight improvements for those
>>> running AllWinner 64 bit devices as we've moved to the upstream ARM
>>> trusted firmware. It's just a snapshot at the moment but the previous
>>> fork was quite old and had it's issues on certain devices so I expect
>>> this to be an overall win for people there, but again I can't test
>>> everything so if anyone sees issues please reach out.
>>> All please add karma to the above update when you do test it. People
>>> can update U-Boot on a running system with the update-uboot command
>>> with similar syntax to arm-image-installer.
>>> Peter
>>> [1]
>>> _______________________________________________
>>> arm mailing list --
>>> To unsubscribe send an email to
>>> Fedora Code of Conduct:
>>> List Guidelines:
>>> List Archives:
arm mailing list --
To unsubscribe send an email to
Fedora Code of Conduct:
List Guidelines:
List Archives:

No comments:

Post a Comment