Hi,
When I include mcuimage.bin from Apr 9 as bl30 in fip, my system gets caught in an endless reboot sequence.
I use latest HiKey ATF and it works fine without bl30.
With ATF from June it works fine to include bl30.
Is this expected behaviour ?
Thanks,
Stefan
Hi Stefan,
Can you try with mcuimage.bin in [1]? I think some recent changes in ARM-TF require an update of mcuimage.bin. Well that's what I concluded when I got a similar problem to yours, but the other way round: I was trying to use the latest mcuimage.bin (from [1]) while I was still using an older ARM-TF from April or June.
[1] https://github.com/96boards/edk2/commit/83b92eb6907ae1e9b27c976b1d7c4053685d...
HTH,
Hi all,
On Wed, Sep 02, 2015 at 01:48:20PM +0200, Jerome Forissier wrote:
Hi Stefan,
Can you try with mcuimage.bin in [1]? I think some recent changes in ARM-TF require an update of mcuimage.bin. Well that's what I concluded when I got a similar problem to yours, but the other way round: I was trying to use the latest mcuimage.bin (from [1]) while I was still using an older ARM-TF from April or June.
[1] https://github.com/96boards/edk2/commit/83b92eb6907ae1e9b27c976b1d7c4053685d...
Thanks for Jerome reminding.
Sorry for i have not send out notification early in mailing list for upgrading MCU firmware.
Please update latest A-T-F and MCU firmware (BL3-0) together, the new MCU firmware supports CPUFreq and CPUIdle, and it also can really power off CPU for hotplug; But there also have some corresponding modification for A-T-F for new MCU firmware. So in case all of us can be make sure on the same page, please follow below steps:
- Update A-T-F with new MCU firmware (BL3-0) to generate fip.bin; - Also need update Linux kernel (3.18 or 4.1rc2) to latest code base, which will use mailbox driver to communicate with new MCU FW;
In case if you want to directly use pre-build boot images, you can get related binaries from: https://builds.96boards.org/snapshots/hikey/linaro/uefi/latest/
Thanks, Leo Yan
On Wed, Sep 2, 2015 at 11:33 AM, Stefan Johansson < stefan.johansson@t2data.com> wrote:
Hi,
When I include mcuimage.bin from Apr 9 as bl30 in fip, my system gets caught in an endless reboot sequence.
I use latest HiKey ATF and it works fine without bl30.
With ATF from June it works fine to include bl30.
Is this expected behaviour ?
Thanks,
Stefan
Dev mailing list Dev@lists.96boards.org https://lists.96boards.org/mailman/listinfo/dev
Dev mailing list Dev@lists.96boards.org https://lists.96boards.org/mailman/listinfo/dev
Hi Stefan,
Please see below more detailed comments.
On Wed, Sep 02, 2015 at 09:33:14AM +0000, Stefan Johansson wrote:
Hi,
When I include mcuimage.bin from Apr 9 as bl30 in fip, my system gets caught in an endless reboot sequence.
If A-T-F loads BL30 (MCU FW) into sram, but have not initailized it successfully, MCU will trigger reset. So finally it will reset system for every time's booting.
I use latest HiKey ATF and it works fine without bl30.
If don't include BL30, then it will not support CPUFreq and CPUIdle; if you use old kernel without CPUIdle, it will be fine, but the latest kernel has enabled CPUIdle, so if you uses latest kernel + latest ATF, the system will hang in this case.
With ATF from June it works fine to include bl30.
This also because you are using old A-T-F + old BL30 + old kernel.
Thanks, Leo Yan
-
Jerome Forissier -
Leo Yan -
Stefan Johansson