On 2021-01-06, Reco wrote: > On Tue, Oct 27, 2020 at 10:20:28PM +0300, Reco wrote: >> On Tue, Oct 27, 2020 at 10:21:01AM -0700, Vagrant Cascadian wrote: >> > Please file bugs and/or merge requests on u-boot and >> > arm-trusted-firmware if you want to get those parts enabled for Odroid >> > N2 and g12a. > > Thank you for paying attention to my bugreport, I see that they are > fixed by now. > But I'm kind of at loss on what to do next. > > I've installed u-boot-amlogic=2021.01~rc4+dfsg-2 and > arm-trusted-firmware=2.4+dfsg-1 from the experimental, but I don't see > any of the firmware mentioned by [1]. > > Should I sign /usr/lib/u-boot/odroid-n2/u-boot.bin with fiptool somehow? > How do I apply /usr/lib/arm-trusted-firmware/g12a/bl31.bin to it? ... > [1] https://salsa.debian.org/debian/u-boot/-/blob/master/doc/board/amlogic/odroid-n2.rst I've only done this on Odroid-C2, so take this with a grain of salt, but the instructions look similar... so reading odroid-n2.rst: Skip the "U-boot compilation" step, and in the "Image Creation" step, copy u-boot.bin from /usr/lib/u-boot/BOARD/u-boot.bin and bl31.bin from /usr/lib/arm-trusted-firmware/PLATFORM/bl31.bin, instead of using the vendor provided parts for those. All the other parts you'll need from the vendor u-boot. It is a little unclear weather there's a significance to the difference between bl31.img and bl31.bin ... you might first try using the vendor "bl31" instead, and then see if bl31.bin works; if the vendor bl31 works and the one from arm-trusted-firmware do not, we might need to adjust the arm-trusted-firmware package somehow... Good luck! live well, vagrant
Attachment:
signature.asc
Description: PGP signature