On Wed, May 27, 2015 at 05:30:12PM +0100, Peter Griffin wrote:
[...]
Yes OK so apologies on that one, I also had two patches applied on top of the ATF SHA mentioned in the readme to get my l-loader.bin compiled from source working. One of those patches added barriers in the mmio routines and the other added the packed attribute to some USB structure, that got around the 1hz numbers bug. I believe both of those changes are merged in upstream ATF now.
Anyway I thought I should try u-boot with the latest ATF code and check it still works. However compiling the latest ATF / l-loader code from source I don't get something that boots :-( so there seems to be new issues there (probably pilot error as the pre-built binaries work OK for me). I've not debugged that any further.
By taking the latest pre-compiled l-loader.bin from here https://builds.96boards.org/snapshots/hikey/uefi/26 and using the latest u-boot (v1 patches sent to u-boot ML). I've had to make some small changes, as the latest ATF now secures the top 16Mb of RAM for trustzone which u-boot was using. Also the bl33 executable now gets linked at 0x35000000 rather than 0x37000000, and I'm back to having a working u-boot again :-)
Hi Peter,
Do you have any update for using latest ATF + uboot? :)
- I tried two ATF versions, one version is to follow up u-boot-readme.txt to checkout commit log:
git checkout 9a97502e8b3247dee95d4f0b48fc5d7154f40609
Finally i saw ATF will trap into exception, so this very likely with memory barrier issues we found before (Or caused by DDR init).
- Also tried latest ATF + uboot but cannot boot up; do you have some extra patches to fix this issue?
i found the memory node in DTB will be overwritten in uboot, so want to build uboot to debug this issue.
Thanks, Leo Yan