Hi Martin,
On 17/01/2019 13:22, Martin Husemann wrote:
Hi folks,
I am trying to get a new u-boot on my Odroid C2 following the instructions in board/amlogic/odroid-c2/README.
Unfortunately these tell me to use not only the vendor provided blobs, but also their tools. This is painfull:
file $DIR/fip/fip_create odroid-c2/fip/fip_create: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=0dc4b0e1bd118ffc3c0f77e815b6d86acc1f25c2, not stripped
so I need to set up an environment where I can run that.
There are alternatives, so the instructions should probably be updated to use them. I have "fiptool" from ARM trusted firmware v2.0, and "fiptool create" should be able to do what fip_create did. Also I have meson-tools installed, providing amlbootsig which could replace aml_encrypt_gxb.
Has someone used these alternate tools instead of the vendor binaries? How do the fip_create options from the README translate to fiptool?
Yes, Andreas Faerber has developed some tools for that : https://github.com/afaerber/meson-tools
You are free to join #linux-amlogic on Freenode and open source the missing bits, but for now we haven't got issues with the ATF binary blobs provided by Amlogic and we focused to have a clean and stable implementation of U-Boot & Linux.
The BL31 has already landed on ARM ATF repo : https://github.com/ARM-software/arm-trusted-firmware/tree/master/plat/meson/...
Seems a couple of hackers are trying to reverse-engineer the BL2 and SCPI blobs, but it's a complex job...
But note the GXBB SoC on he Odroid-C2 is deprecated and not supported anymore by Amlogic, we focus mainly on the new platforms while trying to maintain the GXBB SoCs working with the new features introduced.
Neil
Martin _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot