I got a batch of Hikey960 boards which I’m almost unable to reflash properly.
I’m using https://github.com/96boards-hikey/tools-images-hikey960/blob/master/build-from-source/README-ATF-UEFI-build-from-source.md
to rebuild edk2/atf/l-loader etc.
It looks like the trigger is change in UFS chip. With older boards using chip marked “KLU8G…” (Samsung?) everything works like a charm using tools-image-hikey960 script then flashing l-loader’s ptable-aosp-32g.img, l-loader.bin, fip.bin.
Now with boards using chips marked “THGBF…” (Toshiba?), I get issues flashing ptable, or board not booting after BL2 stage such as:
when flashing ptable
Downloading 24576 bytes
24576 / 24576 bytes downloaded (100%)
Flashing partition ptable
Synchronous Exception at 0x0000000000000000
or later when booting:
NOTICE: BL2: Built : 13:46:43, Mar 29 2018
INFO: BL2: Doing platform setup
INFO: UFS LUN0 contains 1024 blocks with 4096-byte size
INFO: UFS LUN1 contains 1024 blocks with 4096-byte size
INFO: UFS LUN2 contains 2048 blocks with 4096-byte size
INFO: UFS LUN3 contains 7805952 blocks with 4096-byte size
INFO: ufs: change power mode success
INFO: BL2: Loading image id 2
WARNING: Firmware Image Package header check failed.
WARNING: Failed to obtain reference to image id=2 (-2)
ERROR: BL2: Failed to load image (-2)
Do you know about flashing issues after switching to this UFS chip and how to stabilize it?
Thanks and Regards.