I have a yocto rock branch revision 73fcbccf23492e53df49ca0870edce8713a5033c, kernel is 4.9.78-ltsi-altera and U-Boot 2017.09 (Apr 24 2018 - 16:44:35 -0700).
I were able to create an bootable sd card based on the produced binaries. But, the problem is I couldn’t load the soc_system.rbf. I ran ‘run bridge_enable_handoff’ and the u-boot was throwing an errors:
Starting application at 0x3FF7A530 …
pc : [<3ff7a530>] lr : [<3ff52b67>]
reloc pc : [<01029570>] lr : [<01001ba7>]
sp : 3bf49a08 ip : 00000000 fp : 00000002
r10: 3bf54f58 r9 : 3bf4eee8 r8 : 3ffb3f88
r7 : 3ff52b3d r6 : 00000002 r5 : 3ff7a530 r4 : 3bf54f5c
r3 : 3ff7a530 r2 : 3bf54f5c r1 : 3bf54f5c r0 : 00000001
Flags: nzCv IRQs off FIQs off Mode SVC_32
Resetting CPU …
I do believe the branch that I got has a wrong u-boot?. I would like to know what is the latest altera cyclone v meta-layer branch for yocto where I can get it?.
I really appreciate if someone give me some references to point me which yocto and altera-meta branch should I use in order to build a fully functional system?.
Fully functional system - able to load soc_system.rbf, boot the linux.
I have been wondering the exact same thing. The rocko meta-altera layer’s 2017.09 u-boot comes from the mainline u-boot repo (SRC_URI = “git://git.denx.de/u-boot.git;branch=master”). The mainline version does not seem to have any support for loading the FPGA from the HPS. The altera cyclone v u-boot repo is a fork of u-boot 2013.01.01. This fork appears to be actively maintained, and does have support for loading the FPGA from the HPS.
Unless I am missing something, it seems like the altera repo u-boot is the correct one to use if you want to load the fpga from the HPS. The instructions for using the more recent tagged versions of the altera repo would be very similar to the instructions found on the rocketboards site. I have no idea why the “official” Yocto meta-altera layer does not have a recipe for building the “official” altera-supported u-boot.
I created my own recipe to build the altera version of u-boot, and I put the recipe in my own layer, so I could build the altera-maintained version of u-boot from yocto.
Can anyone comment on why the meta-altera u-boot recipe builds the mainline version of u-boot, rather than the version of u-boot maintained by altera? Am I missing something here?
I figured it out. There is a new u-boot command ‘bridge enable’ (without the quotes) that replaces ‘run bridge_enable_handoff’ from the old 2013.01.01 boot script. There is more complete detail here. Seems like a simple example from altera would have been really helpful here…