Hi.
I have a Juno R2 board and followed the process described here: https://github.com/OP-TEE/build/blob/master/README.md
...to build op-tee and all the other related components. I copied all the relevant bits to my Juno to update the firmware and other images but things hang here:
[cut] NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.2(release):0d6e84b NOTICE: BL1: Built : 17:32:54, May 3 2017 NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.2(release):0d6e84b NOTICE: BL2: Built : 17:32:54, May 3 2017 NOTICE: BL1: Booting BL31 NOTICE: BL31: v1.2(release):0d6e84b NOTICE: BL31: Built : 17:32:54, May 3 2017
So, it appears the bootloader never gets started.
Anyone have ideas as to what I might be missing? ...I'll start further analysis and debug, but was expecting the canned build process to produce something that worked out of the box.
Thanks, Stuart
Hi Stuart,
On Thu, May 04, 2017 at 12:17:31PM -0500, Stuart Yoder wrote:
Hi.
I have a Juno R2 board and followed the process described here: https://github.com/OP-TEE/build/blob/master/README.md
Did you follow this also? https://github.com/OP-TEE/build/blob/master/docs/juno.md
...to build op-tee and all the other related components. I copied all the relevant bits to my Juno to update the firmware and other images but things hang here:
[cut] NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.2(release):0d6e84b NOTICE: BL1: Built : 17:32:54, May 3 2017 NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.2(release):0d6e84b NOTICE: BL2: Built : 17:32:54, May 3 2017 NOTICE: BL1: Booting BL31 NOTICE: BL31: v1.2(release):0d6e84b NOTICE: BL31: Built : 17:32:54, May 3 2017
So, it appears the bootloader never gets started.
Anyone have ideas as to what I might be missing?
No, hard to say without having the device in front of me. Are running latest (juno.xml) or are you running latest stable (juno_stable.xml)? The latter was tested for the 2.4.0 release on the first Juno board (R1?), see: https://github.com/OP-TEE/optee_os/blob/master/CHANGELOG.md#tested-on https://github.com/OP-TEE/optee_os/pull/1426#issuecomment-289725773
...I'll start further analysis and debug, but was expecting the canned build process to produce something that worked out of the box.
Yes, it should work, having that said, we're not using the Juno device on daily basis and it's not in our (SWG's) CI/test loop (yet), so there might be a change that patches merged the last week or so eventually could have introduced some regression.
On 5/4/17 12:46 PM, Joakim Bech wrote:
Hi Stuart,
On Thu, May 04, 2017 at 12:17:31PM -0500, Stuart Yoder wrote:
Hi.
I have a Juno R2 board and followed the process described here: https://github.com/OP-TEE/build/blob/master/README.md
Did you follow this also? https://github.com/OP-TEE/build/blob/master/docs/juno.md
Oh, I missed that there was a doc directory under build. (might be good to add some links to those)
I read the juno.md...I'm not flashing my images via tftp, but don't think that matters. Only thing that seemed possible relevant was the possible issue of overwriting images in flash. It seems that the Juno flash map may have changed (?). On my board there is about 13MB free at 0x01800000 so don't think ramdisk size is the issue. Plus my kernel Image file is about 14MB and if I adjusted things as per the instructions "to extend the Juno flash block size reserved location for the ramdisk.img" it would overlap the kernel.
So, I don't "think" it's an issue with the ramdisk or kernel overlapping or something.
The bootloader (u-boot in this case) is part of the fip.bin and I'd at least expect to see the bootloader try to start.
...to build op-tee and all the other related components. I copied all the relevant bits to my Juno to update the firmware and other images but things hang here:
[cut] NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.2(release):0d6e84b NOTICE: BL1: Built : 17:32:54, May 3 2017 NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.2(release):0d6e84b NOTICE: BL2: Built : 17:32:54, May 3 2017 NOTICE: BL1: Booting BL31 NOTICE: BL31: v1.2(release):0d6e84b NOTICE: BL31: Built : 17:32:54, May 3 2017
So, it appears the bootloader never gets started.
Anyone have ideas as to what I might be missing?
No, hard to say without having the device in front of me. Are running latest (juno.xml) or are you running latest stable (juno_stable.xml)?
I tried juno.xml...will try the juno_stable to sanity check things.
Thanks, Stuart
On 5/4/17 1:48 PM, Stuart Yoder wrote:
On 5/4/17 12:46 PM, Joakim Bech wrote:
Hi Stuart,
On Thu, May 04, 2017 at 12:17:31PM -0500, Stuart Yoder wrote:
Hi.
I have a Juno R2 board and followed the process described here: https://github.com/OP-TEE/build/blob/master/README.md
Did you follow this also? https://github.com/OP-TEE/build/blob/master/docs/juno.md
Oh, I missed that there was a doc directory under build. (might be good to add some links to those)
I read the juno.md...I'm not flashing my images via tftp, but don't think that matters. Only thing that seemed possible relevant was the possible issue of overwriting images in flash. It seems that the Juno flash map may have changed (?). On my board there is about 13MB free at 0x01800000 so don't think ramdisk size is the issue. Plus my kernel Image file is about 14MB and if I adjusted things as per the instructions "to extend the Juno flash block size reserved location for the ramdisk.img" it would overlap the kernel.
So, I don't "think" it's an issue with the ramdisk or kernel overlapping or something.
The bootloader (u-boot in this case) is part of the fip.bin and I'd at least expect to see the bootloader try to start.
...to build op-tee and all the other related components. I copied all the relevant bits to my Juno to update the firmware and other images but things hang here:
[cut] NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.2(release):0d6e84b NOTICE: BL1: Built : 17:32:54, May 3 2017 NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.2(release):0d6e84b NOTICE: BL2: Built : 17:32:54, May 3 2017 NOTICE: BL1: Booting BL31 NOTICE: BL31: v1.2(release):0d6e84b NOTICE: BL31: Built : 17:32:54, May 3 2017
So, it appears the bootloader never gets started.
Anyone have ideas as to what I might be missing?
No, hard to say without having the device in front of me. Are running latest (juno.xml) or are you running latest stable (juno_stable.xml)?
I tried juno.xml...will try the juno_stable to sanity check things.
juno_stable.xml worked for me...so looks like there may be a regression, as you suggested.
Thanks, Stuart
On Fri, May 5, 2017 at 12:37 AM, Stuart Yoder stuart.yoder@arm.com wrote:
On 5/4/17 1:48 PM, Stuart Yoder wrote:
On 5/4/17 12:46 PM, Joakim Bech wrote:
Hi Stuart,
On Thu, May 04, 2017 at 12:17:31PM -0500, Stuart Yoder wrote:
Hi.
I have a Juno R2 board and followed the process described here: https://github.com/OP-TEE/build/blob/master/README.md
Did you follow this also?
Oh, I missed that there was a doc directory under build. (might be good to add some links to those)
I read the juno.md...I'm not flashing my images via tftp, but don't think that matters. Only thing that seemed possible relevant was the possible issue of overwriting images in flash. It seems that the Juno flash map may have changed (?). On my board there is about 13MB free at 0x01800000 so don't think ramdisk size is the issue. Plus my kernel Image file is about 14MB and if I adjusted things as per the instructions "to extend the Juno flash block size reserved location for the ramdisk.img" it would overlap the kernel.
So, I don't "think" it's an issue with the ramdisk or kernel overlapping or something.
The bootloader (u-boot in this case) is part of the fip.bin and I'd at least expect to see the bootloader try to start.
...to build op-tee and all the other related components. I copied
all the relevant bits to my Juno to update the firmware and other images but things hang here:
[cut] NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.2(release):0d6e84b NOTICE: BL1: Built : 17:32:54, May 3 2017 NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.2(release):0d6e84b NOTICE: BL2: Built : 17:32:54, May 3 2017 NOTICE: BL1: Booting BL31 NOTICE: BL31: v1.2(release):0d6e84b NOTICE: BL31: Built : 17:32:54, May 3 2017
So, it appears the bootloader never gets started.
Hmmm... hangs at the same place as https://github.com/OP-TEE/optee_os/issues/1511
Anyone have ideas as to what I might be missing?
No, hard to say without having the device in front of me. Are running latest (juno.xml) or are you running latest stable (juno_stable.xml)?
I tried juno.xml...will try the juno_stable to sanity check things.
juno_stable.xml worked for me...so looks like there may be a regression, as you suggested.
Please try https://github.com/jforissier/optee_os/commit/372c32024c71 and it that fixes the problem then it's the same issue as #1511.
Thanks,
Hi,
On Thu, May 04, 2017 at 01:48:54PM -0500, Stuart Yoder wrote:
On 5/4/17 12:46 PM, Joakim Bech wrote:
On Thu, May 04, 2017 at 12:17:31PM -0500, Stuart Yoder wrote:
Oh, I missed that there was a doc directory under build. (might be good to add some links to those)
Actually there is a link to that in the instructions (first in section 7), but it's easy to miss it, I'll submit a patch that will make it a bit clearer.
-
Jerome Forissier -
Joakim Bech -
Stuart Yoder