Problems related to arm-image-installer-2.15-1.fc31.noarch and rpi && rock64

[Peter Hjalmarsson]

Hi,

The newly released arm-image-installer-2.15-1.fc31.noarch has some problems I like to point out with regards to raspberry pi and the newly introduced support for rock64.
Lets start with rock64:
The boards.d file is named "rock64". This filename is supposed to match the folder name from uboot-images-armv8-2019.10-2.fc31.noarch, however that folder is named "rock64-rk3328".
This results in the following:
[root@localhost ~]# update-uboot --target=rock64-rk3328 --media=/dev/mmcblk0
/usr/bin/update-uboot: line 124: /usr/share/arm-image-installer/boards.d/rock64-rk3328: No such file or directory
[root@localhost ~]# update-uboot --target=rock64 --media=/dev/mmcblk0
= No U-Boot files found for rock64.
= Complete!
----
UGLYWORKAROUND:
[root@localhost ~]# mv /usr/share/arm-image-installer/boards.d/rock64 /usr/share/arm-image-installer/boards.d/rock64-rk3328
[root@localhost ~]# update-uboot --target=rock64-rk3328 --media=/dev/mmcblk0
= Writing idbloader.img for rock64-rk3328 .... on media /dev/mmcblk0
686+1 records in
686+1 records out
351280 bytes (351 kB, 343 KiB) copied, 0.105989 s, 3.3 MB/s
= Writing u-boot FIT image for rock64-rk3328 .... on media /dev/mmcblk0
1409+1 records in
1409+1 records out
721580 bytes (722 kB, 705 KiB) copied, 0.226429 s, 3.2 MB/s
= Complete!
---

Now for Raspberry Pi.
This release dropped "rpi-uboot-update", which essentially took the corresponding raspberry pi uboot file files from uboot-images-armv8 and copied them to the correct location renaming to the correct name depending on if rpi2 or rpi3.
The problem is that dropping this script removed the only "easy" way to update uboot for raspberry pi, since "update-uboot" has files for rpi2 and rpi3 which does nothing but setting the correct console-parameters.
My proposal is to reintroduce "rpi-uboot-update" until update-uboot has information added for updating also the rpi2 and rpi3 unless there was a good reason for dropping this script?

Best Regards,
Peter Hjalmarsson

[Paul Whalen]

Hi Peter,

----- Original Message -----
> Hi,
>
> The newly released arm-image-installer-2.15-1.fc31.noarch has some problems I
> like to point out with regards to raspberry pi and the newly introduced
> support for rock64.
> Lets start with rock64:

Thanks, I merged the PR without looking at it closely, will be fixed on the next
release.
> The boards.d file is named "rock64". This filename is supposed to match the
> folder name from uboot-images-armv8-2019.10-2.fc31.noarch, however that
> folder is named "rock64-rk3328".
> This results in the following:
> [root@localhost ~]# update-uboot --target=rock64-rk3328 --media=/dev/mmcblk0
> /usr/bin/update-uboot: line 124:
> /usr/share/arm-image-installer/boards.d/rock64-rk3328: No such file or
> directory
> [root@localhost ~]# update-uboot --target=rock64 --media=/dev/mmcblk0
> = No U-Boot files found for rock64.
> = Complete!
>
> UGLYWORKAROUND:
> [root@localhost ~]# mv /usr/share/arm-image-installer/boards.d/rock64
> /usr/share/arm-image-installer/boards.d/rock64-rk3328
> [root@localhost ~]# update-uboot --target=rock64-rk3328 --media=/dev/mmcblk0
> = Writing idbloader.img for rock64-rk3328 .... on media /dev/mmcblk0
> 686+1 records in
> 686+1 records out
> 351280 bytes (351 kB, 343 KiB) copied, 0.105989 s, 3.3 MB/s
> = Writing u-boot FIT image for rock64-rk3328 .... on media /dev/mmcblk0
> 1409+1 records in
> 1409+1 records out
> 721580 bytes (722 kB, 705 KiB) copied, 0.226429 s, 3.2 MB/s
> = Complete!
>
> Now for Raspberry Pi.
> This release dropped "rpi-uboot-update", which essentially took the
> corresponding raspberry pi uboot file files from uboot-images-armv8 and
> copied them to the correct location renaming to the correct name depending
> on if rpi2 or rpi3.
> The problem is that dropping this script removed the only "easy" way to
> update uboot for raspberry pi, since "update-uboot" has files for rpi2 and
> rpi3 which does nothing but setting the correct console-parameters.
> My proposal is to reintroduce "rpi-uboot-update" until update-uboot has
> information added for updating also the rpi2 and rpi3 unless there was a
> good reason for dropping this script?

Will be readded next release which should be in koji shortly. Just waiting to 
hear back about another issue and will do a build.

Thanks for the feedback, apologies for the issues :)

Paul
> Best Regards,
> Peter Hjalmarsson
> _______________________________________________
> arm mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Peter Hjalmarsson]

Hi,

Thanks for the update.
Are there any interest in adding rpi2/rpi3 support into update-uboot
instead of having rpi-firmware-update?

Regards,
Hjalmarsson

Den tis 7 jan. 2020 kl 23:00 skrev Paul Whalen :
> Hi Peter,
>
> ----- Original Message -----
> > Hi,
> >
> > The newly released arm-image-installer-2.15-1.fc31.noarch has some problems I
> > like to point out with regards to raspberry pi and the newly introduced
> > support for rock64.
> > Lets start with rock64:
>
> Thanks, I merged the PR without looking at it closely, will be fixed on the next
> release.
> > The boards.d file is named "rock64". This filename is supposed to match the
> > folder name from uboot-images-armv8-2019.10-2.fc31.noarch, however that
> > folder is named "rock64-rk3328".
> > This results in the following:
> > [root@localhost ~]# update-uboot --target=rock64-rk3328 --media=/dev/mmcblk0
> > /usr/bin/update-uboot: line 124:
> > /usr/share/arm-image-installer/boards.d/rock64-rk3328: No such file or
> > directory
> > [root@localhost ~]# update-uboot --target=rock64 --media=/dev/mmcblk0
> > = No U-Boot files found for rock64.
> > = Complete!
> >
> > UGLYWORKAROUND:
> > [root@localhost ~]# mv /usr/share/arm-image-installer/boards.d/rock64
> > /usr/share/arm-image-installer/boards.d/rock64-rk3328
> > [root@localhost ~]# update-uboot --target=rock64-rk3328 --media=/dev/mmcblk0
> > = Writing idbloader.img for rock64-rk3328 .... on media /dev/mmcblk0
> > 686+1 records in
> > 686+1 records out
> > 351280 bytes (351 kB, 343 KiB) copied, 0.105989 s, 3.3 MB/s
> > = Writing u-boot FIT image for rock64-rk3328 .... on media /dev/mmcblk0
> > 1409+1 records in
> > 1409+1 records out
> > 721580 bytes (722 kB, 705 KiB) copied, 0.226429 s, 3.2 MB/s
> > = Complete!
> >
> > Now for Raspberry Pi.
> > This release dropped "rpi-uboot-update", which essentially took the
> > corresponding raspberry pi uboot file files from uboot-images-armv8 and
> > copied them to the correct location renaming to the correct name depending
> > on if rpi2 or rpi3.
> > The problem is that dropping this script removed the only "easy" way to
> > update uboot for raspberry pi, since "update-uboot" has files for rpi2 and
> > rpi3 which does nothing but setting the correct console-parameters.
> > My proposal is to reintroduce "rpi-uboot-update" until update-uboot has
> > information added for updating also the rpi2 and rpi3 unless there was a
> > good reason for dropping this script?
>
> Will be readded next release which should be in koji shortly. Just waiting to
> hear back about another issue and will do a build.
>
> Thanks for the feedback, apologies for the issues :)
>
> Paul
> > Best Regards,
> > Peter Hjalmarsson
> > _______________________________________________
> > arm mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedoraproject.org/archives/list/[e-mail]

[Paul Whalen]

Hi Peter,

----- Original Message -----
> Hi,
>
> Thanks for the update.
> Are there any interest in adding rpi2/rpi3 support into update-uboot
> instead of having rpi-firmware-update?

Yes that is the plan, just wanted to fix it quickly for now. I under estimated its
usage :)

Paul
> Regards,
> Hjalmarsson
>
> Den tis 7 jan. 2020 kl 23:00 skrev Paul Whalen :
> > Hi Peter,
> >
> > ----- Original Message -----
> > > Hi,
> > >
> > > The newly released arm-image-installer-2.15-1.fc31.noarch has some
> > > problems I
> > > like to point out with regards to raspberry pi and the newly introduced
> > > support for rock64.
> > > Lets start with rock64:
> >
> > Thanks, I merged the PR without looking at it closely, will be fixed on the
> > next
> > release.
> > > The boards.d file is named "rock64". This filename is supposed to match
> > > the
> > > folder name from uboot-images-armv8-2019.10-2.fc31.noarch, however that
> > > folder is named "rock64-rk3328".
> > > This results in the following:
> > > [root@localhost ~]# update-uboot --target=rock64-rk3328
> > > --media=/dev/mmcblk0
> > > /usr/bin/update-uboot: line 124:
> > > /usr/share/arm-image-installer/boards.d/rock64-rk3328: No such file or
> > > directory
> > > [root@localhost ~]# update-uboot --target=rock64 --media=/dev/mmcblk0
> > > = No U-Boot files found for rock64.
> > > = Complete!
> > >
> > > UGLYWORKAROUND:
> > > [root@localhost ~]# mv /usr/share/arm-image-installer/boards.d/rock64
> > > /usr/share/arm-image-installer/boards.d/rock64-rk3328
> > > [root@localhost ~]# update-uboot --target=rock64-rk3328
> > > --media=/dev/mmcblk0
> > > = Writing idbloader.img for rock64-rk3328 .... on media /dev/mmcblk0
> > > 686+1 records in
> > > 686+1 records out
> > > 351280 bytes (351 kB, 343 KiB) copied, 0.105989 s, 3.3 MB/s
> > > = Writing u-boot FIT image for rock64-rk3328 .... on media /dev/mmcblk0
> > > 1409+1 records in
> > > 1409+1 records out
> > > 721580 bytes (722 kB, 705 KiB) copied, 0.226429 s, 3.2 MB/s
> > > = Complete!
> > >
> > > Now for Raspberry Pi.
> > > This release dropped "rpi-uboot-update", which essentially took the
> > > corresponding raspberry pi uboot file files from uboot-images-armv8 and
> > > copied them to the correct location renaming to the correct name
> > > depending
> > > on if rpi2 or rpi3.
> > > The problem is that dropping this script removed the only "easy" way to
> > > update uboot for raspberry pi, since "update-uboot" has files for rpi2
> > > and
> > > rpi3 which does nothing but setting the correct console-parameters.
> > > My proposal is to reintroduce "rpi-uboot-update" until update-uboot has
> > > information added for updating also the rpi2 and rpi3 unless there was a
> > > good reason for dropping this script?
> >
> > Will be readded next release which should be in koji shortly. Just waiting
> > to
> > hear back about another issue and will do a build.
> >
> > Thanks for the feedback, apologies for the issues :)
> >
> > Paul
> > > Best Regards,
> > > Peter Hjalmarsson
> > > _______________________________________________
> > > arm mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > Fedora Code of Conduct:
> > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > List Archives:
> > > https://lists.fedoraproject.org/archives/list/[e-mail]