Page MenuHomePhabricator

Hikey960 problem reading FIP
Open, Needs TriagePublic

Description

i'm having trouble getting arm trusted firmware on hikey960
I followed all the steps in this guide https://github.com/ARM-software/arm-trusted-firmware/blob/master/docs/plat/hikey960.rst
the problem seems to be in reading the fip.bin, because it fails to load images based an a uuid
the code in question is in 'drivers/io/io_fip.c', in function fip_file_open
the first uuid read from the fip image is the second uuid present in the fip.bin
If anyone could give me any pointers as to what the problem might be, that'd be great

Event Timeline

Hi David, Sorry for the delay in replying.

The question you ask is best answered by the hikey960 platform maintainer as the details are platform specific.

Details from the maintainers.rst file:

HiSilicon HiKey and HiKey960 platform ports

:M: Haojian Zhuang <haojian.zhuang@linaro.org>
:G: hzhuang1_
:F: docs/plat/hikey.rst
:F: docs/plat/hikey960.rst
:F: plat/hisilicon/hikey/
:F: plat/hisilicon/hikey960/

hzhuang1 claimed this task.Sep 17 2019, 4:42 AM
hzhuang1 added a subscriber: hzhuang1.

Hi David,

Excuse me that I just know your issue today. Could you share more details on it? Are you using the latest TF-A?

Hi there!

Turns out the problem is that I was performing the partition table update wrongly.
And so ATF was attempting to read the fip image from the wrong address. As a quick fix I made calculation to the fip image in the factory table partition.
Later I figured out how to update the partition table.

Best regards,
David Cerdeira

hzhuang1 added a comment.EditedSep 17 2019, 8:41 AM

Hi David,

Yes, there's an issue on loading FIP image with hacking address. I have a fix on it. (https://github.com/hzhuang1/arm-trusted-firmware/tree/topic/partition)

But I have the email address issue in gerrit. So I can't submit my patches for review. You can pick up the patches and verify it on your platform.