1. 21 May, 2021 1 commit
    • Igor Opaniuk's avatar
      feat(plat/imx8m): add SiP call for secondary boot · 9ce232fe
      Igor Opaniuk authored
      In iMX8MM it is possible to have two copies of bootloader in
      SD/eMMC and switch between them. The switch is triggered either
      by the BootROM in case the bootloader image is faulty OR can be
      enforced by the user. To trigger that switch the
      PERSIST_SECONDARY_BOOT bit should be set in GPR10 SRC register.
      As the bit is retained after WARM reset, that permits to control
      BootROM behavior regarding what boot image it will boot after
      reset: primary or secondary.
      
      This is useful for reliable bootloader A/B updates, as it permits
      switching between two copies of bootloader at different offsets of
      the same storage.
      
      If the PERSIST_SECONDARY_BOOT is 0, the boot ROM uses address
      0x8400 for the primary image. If the PERSIST_SECONDARY_BOOT is 1,
      the boot ROM reads that secondary image table from address 0x8200
      on the boot media and uses the address specified in the table for
      the secondary image.
      
      Secondary Image Table contains the sector of secondary bootloader
      image, exluding the offset to that image (explained below in the
      note). To generate the Secondary Image Table, use e.g.:
      $ printf '\x0\x0\x0\x0\x0\x0\x0\x0\x33\x22\x11'
               '\x00\x00\x10\x0\x0\x00\x0\x0\x0'
        > /tmp/sit.bin
      $ hexdump  -vC /tmp/sit.bin
        00000000  00 00 00 00
        00000004  00 00 00 00
        00000008  33 22 11 00 <--- This is the "tag"
        0000000c  00 10 00 00 <--- This is the "firstSectorNumber"
        00000010  00 00 00 00
      
      You can also use NXP script from [1][2] imx-mkimage tool for
      SIT generation. Note that the firstSectorNumber is NOT the offset
      of the IVT, but an offset of the IVT decremented by Image Vector
      Table offset (Table 6-25. Image Vector Table Offset and Initial
      Load Region Size for iMX8MM/MQ), so for secondary SPL copy at
      offset 0x1042 sectors, firstSectorNumber must be 0x1000
      (0x42 sectors * 512 = 0x8400 bytes offset).
      
      In order to test redundant boot board should be closed and
      SD/MMC manufacture mode disabled, as secondary boot is not
      supported in the SD/MMC manufacture mode, which can be disabled
      by blowing DISABLE_SDMMC_MFG (example for iMX8MM):
      > fuse prog -y 2 1 0x00800000
      
      For additional details check i.MX 8M Mini Apllication Processor
      Reference Manual, 6.1.5.4.5 Redundant boot support for
      expansion device chapter.
      
      [1] https://source.codeaurora.org/external/imx/imx-mkimage/
      
      
      [2] scripts/gen_sit.sh
      Change-Id: I0a5cea7295a4197f6c89183d74b4011cada52d4c
      Signed-off-by: default avatarIgor Opaniuk <igor.opaniuk@foundries.io>
      9ce232fe
  2. 22 Apr, 2021 2 commits
  3. 21 Apr, 2021 3 commits
  4. 20 Apr, 2021 24 commits
  5. 16 Apr, 2021 1 commit
    • Sandrine Bailleux's avatar
      Arm: Fix error message printing in board makefile · 5eea0193
      Sandrine Bailleux authored
      
      
      Remove an incorrect tabulation in front of an $(error) function call
      outside of a recipe, which caused the following text to be displayed:
      
        plat/arm/board/common/board_common.mk:36: *** recipe commences before first target.  Stop.
      
      instead of:
      
        plat/arm/board/common/board_common.mk:36: *** "Unsupported ARM_ROTPK_LOCATION value".  Stop.
      
      Change-Id: I8592948e7de8ab0c4abbc56eb65a53eb1875a83c
      Signed-off-by: default avatarSandrine Bailleux <sandrine.bailleux@arm.com>
      5eea0193
  6. 15 Apr, 2021 1 commit
  7. 14 Apr, 2021 1 commit
  8. 13 Apr, 2021 2 commits
  9. 09 Apr, 2021 1 commit
    • Manish Pandey's avatar
      plat/arm: don't provide NT_FW_CONFIG when booting hafnium · 2b6fc535
      Manish Pandey authored
      
      
      NT_FW_CONFIG file is meant to be passed from BL31 to be consumed by
      BL33, fvp platforms use this to pass measured boot configuration and
      the x0 register is used to pass the base address of it.
      
      In case of hafnium used as hypervisor in normal world, hypervisor
      manifest is expected to be passed from BL31 and its base address is
      passed in x0 register.
      
      As only one of NT_FW_CONFIG or hypervisor manifest base address can be
      passed in x0 register and also measured boot is not required for SPM so
      disable passing NT_FW_CONFIG.
      Signed-off-by: default avatarManish Pandey <manish.pandey2@arm.com>
      Change-Id: Ifad9d3658f55ba7d70f468a88997d5272339e53e
      2b6fc535
  10. 08 Apr, 2021 3 commits
  11. 06 Apr, 2021 1 commit