TF-A June 2019

tf-a@lists.trustedfirmware.org

13 participants
12 discussions

Arm trusted firmware reads wrong fip file from flash on hikey960v2

by David Cerdeira

Greetings, i’m having trouble getting arm trusted firmware to work on hikey960v2 I followed all the steps in this guide https://github.com/ARM-software/arm-trusted-firmware/blob/master/docs/plat/…, and the steps in https://optee.readthedocs.io/building/devices/hikey960.html The problem seems to be in reading the fip.bin, or rather the problem is writing the fip file as it seems it is not properly flashed. ATF bl2 fails to find the UUID of the BL2_SCP image in the fip.bin output by the build process, the fip file it reads from flash only has the BL31 and BL33 UUIDs. I tried checking older versions of ATF, as I figured it might be a problem in current versions, but the same problems occurred. At this moment I feel the problem is in the flashing step. I tried moving the partitions in the partition tables, as well as the value of the macro HIKEY960_FIP_BASE present in hikey960_def.h to match what I thought would be the writing position of the file in the partition, but without success. If anyone could give me any idea as to what the problem might be, that’d be great Best regards, David Cerdeira

4 years, 10 months

Regression on Poplar eMMC

by Shawn Guo

Hi Tien, We recently found a regression on Poplar eMMC in U-Boot, which seems caused by commit 3d0f30bb544a ("drivers: synopsys: Fix synopsys MMC driver"). For some reason, the setup of FIFO threshold breaks eMMC support in U-Boot [1]. Would you please suggest a sensible fix for this regression? Thanks. Shawn [1] https://discuss.96boards.org/t/uboot-mmc-init-problem/8130/3

4 years, 10 months

2024

2023

2022

2021

2020

2019

2018

TF-A June 2019