Re: Building U-Boot for Compulab's imx8mm-cl-iot-gate board

1 Jul 2021


      Hi Fabio,
We have dfu_alt_info set. So that we can capsule update from UEFI.
First, "setenv -e -nv -bs -rt -v OsIndications =0x04"
And then we can "efidebug capsule update -v ${loadaddr}".
To make the capsule binary, we need to create a capsule1.itb with the
following content:
/dts-v1/;
/ {
       description = "Automatic U-Boot environment update";
       #address-cells = <2>;
images {
               flash-bin {
                       description = "U-Boot binary on SPI Flash";
                       data = /incbin/("flash.bin");
                       compression = "none";
                       type = "firmware";
                       arch = "arm64";
                       load = <0>;
                       hash-1 {
                               algo = "sha1";
                       };
               };
               u-boot-itb {
                       description = "U-Boot binary";
                       data = /incbin/("u-boot.itb");
                       compression = "none";
                       type = "firmware";
                        arch = "arm64";
                       load = <0>;
                       hash-1 {
                               algo = "sha1";
                       };
               };
       };
};
And then "./tools/mkimage -f capsule1.its capsule1.itb"
"./tools/mkeficapsule --fit capsule1.itb --index 1 capsule1.bin"
And we can tftp the capsule1.bin to ${loadaddr} and then use the capsule
update.
Yours,
Paul
On Fri, 2 Jul 2021 at 00:39, Fabio Estevam festevam@gmail.com wrote:
...
Hi Paul,
On Thu, Jul 1, 2021 at 12:45 PM Paul Liu paul.liu@linaro.org wrote:
...
Hi Fabio,
Yes. It is able to not provide the fip,bin.
If you use bl31.bin as bl31.bin then fip.bin can be empty.
If you use bl2.bin as bl31.bin then you have to have the fip.
This depends on how TF-A are being built.
If you build TF-A without NEED_BL2=yes. Then you don't need the fip.bin.
If you build TF-A with NEED_BL2=yes. Then FIP is needed. And you have to
use bl2.bin generated by TF-A and rename it to bl31.bin. I think maybe I
can fix the README. If you can do that then that's perfect because my
English is always not very good. So that means I sometimes need more review
on my English sentences.
Thanks for the clarification.
I can work on creating a README file for this board after I manage to boot
it.
What is the process of flashing the flash.bin and u-boot.itb binaries
to the eMMC?
Do you use the uuu tool? If so, what is the  uuu_script script that you
use?
Thanks,
Fabio Estevam