1. 15 Mar, 2018 15 commits
  2. 14 Mar, 2018 3 commits
  3. 13 Mar, 2018 1 commit
  4. 08 Mar, 2018 3 commits
    • davidcunado-arm's avatar
      Merge pull request #1303 from soby-mathew/sm/fix_juno_fwu · 16b05e94
      davidcunado-arm authored
      Juno: Fixes for firmware update
      16b05e94
    • davidcunado-arm's avatar
      Merge pull request #1277 from hzhuang1/testing/bl2_el3_v0.6 · bf35944b
      davidcunado-arm authored
      hikey: migrate to BL2_EL3
      bf35944b
    • Soby Mathew's avatar
      Juno: Change the Firmware update detect mechanism · 7b56928a
      Soby Mathew authored
      
      
      Previously, Juno used to depend on the SSC_GPRETN register to inform
      about the reset syndrome. This method was removed when SCP migrated
      to the SDS framework. But even the SDS framework doesn't report the
      reset syndrome correctly and hence Juno failed to enter Firmware
      update mode if BL2 authentication failed.
      
      In addition to that, the error code populated in V2M_SYS_NVFLAGS register
      does not seem to be retained any more on Juno across resets. This could
      be down to the motherboard firmware not doing the necessary to preserve
      the value.
      
      Hence this patch modifies the Juno platform to use the same mechanism to
      trigger firmware update as FVP which is to corrupt the FIP TOC on
      authentication failure. The implementation in `fvp_err.c` is made common
      for ARM platforms and is moved to the new `arm_err.c` file in
      plat/arm/common folder. The BL1 and BL2 mmap table entries for Juno
      are modified to allow write to the Flash memory address.
      
      Change-Id: Ica7d49a3e8a46a90efd4cf340f19fda3b549e945
      Signed-off-by: default avatarSoby Mathew <soby.mathew@arm.com>
      7b56928a
  5. 07 Mar, 2018 3 commits
  6. 06 Mar, 2018 3 commits
  7. 05 Mar, 2018 12 commits