10 Apr, 2019

2 commits

  • The csf_additional_images.txt example should match with
    mx6_mx7_secure_boot.txt guide.

    Fix addresses provided in csf_additional_images.txt CSF
    example.

    Reviewed-by: Ye Li
    Signed-off-by: Breno Lima
    (cherry picked from commit 17c3af7a1935a40057c01459766d41ff0a19723b)

    Breno Lima
     
  • When booting in low power or dual boot modes the M4 binary is
    authenticated by the M4 ROM code.

    Add an option in hab_status command so users can retrieve M4 HAB
    failure and warning events.

    => hab_status m4

    Secure boot disabled

    HAB Configuration: 0xf0, HAB State: 0x66
    No HAB Events Found!

    Add command documentation in mx6_mx7_secure_boot.txt guide.

    As HAB M4 API cannot be called from A7 core the code is parsing
    the M4 HAB persistent memory region. The HAB persistent memory
    stores HAB events, public keys and others HAB related information.

    The HAB persistent memory region addresses and sizes can be found
    in AN12263 "HABv4 RVT Guidelines and Recommendations".

    Reviewed-by: Utkarsh Gupta
    Reviewed-by: Ye Li
    Signed-off-by: Breno Lima
    (cherry picked from commit 0efff16579fabcf57acb9c8857afac8fb58de355)

    Breno Lima
     

26 Feb, 2019

4 commits

  • Fix a typo in path provided for imx-mkimage iMX8QM and iMX8QXP directories.

    Reported-by: Marius Grigoras
    Signed-off-by: Breno Lima
    Reviewed-by: Ye Li
    (cherry picked from commit c75243c1a87a10f003377d9c144bcf412ba80440)

    Breno Lima
     
  • The commands included in introduction guide should not be used as
    reference for programming the SRK Hash fuses as they are in big
    endian.

    Add a note to avoid a possible mistake.

    Reported-by: Clement Le Marquis
    Signed-off-by: Breno Lima
    Reviewed-by: Ye Li
    (cherry picked from commit 137319826cc32d98a9b6890f35dd6670e104c2a5)

    Breno Lima
     
  • Since commit 771b824728ca ("MLK-20919 imx8: ahab: Add command to
    close the chip") the U-Boot is able to move the lifecycle from
    NXP closed to OEM closed.

    Update AHAB guides to use U-Boot ahab_close command instead of SCFW CLI.

    As the procedure is now independent of SCFW terminal we can remove
    this condition from documentation.

    Signed-off-by: Breno Lima
    Reviewed-by: Ye Li
    (cherry picked from commit 6f93d877e1454024f666a4810d24148cf595429e)

    Breno Lima
     
  • Starting in L4.14.78 release, the OP-TEE CAAM driver does not set the
    JROWN_NS field in case LMID is locked.

    We need to include the Unlock MID command in CSF file otherwise device
    will fail to boot in HAB closed mode.

    Add section to avoid crash when OP-TEE is enabled.

    Reported-by: Frank Zhang
    Signed-off-by: Breno Lima
    Reviewed-by: Ye Li
    (cherry picked from commit af03284ad38bd03ef1f0d4942842629db93d2c11)

    Breno Lima
     

14 Feb, 2019

2 commits


14 Dec, 2018

4 commits


26 Nov, 2018

2 commits

  • The HABv4 secure boot procedure is now documented in different files:

    .
    └── habv4
    ├── csf_examples
    │   ├── additional_images
    │   │   └── csf_additional_images.txt
    │   ├── mx6_mx7
    │   │   ├── csf_uboot_fast_authentication.txt
    │   │   └── csf_uboot.txt
    │   └── mx8m_mx8mm
    │   ├── csf_fit.txt
    │   └── csf_spl.txt
    ├── guides
    │   ├── mx6_mx7_secure_boot.txt
    │   ├── mx8m_mx8mm_secure_boot.pdf
    │   └── mx8m_mx8mm_secure_boot.txt
    ├── introduction_habv4.txt
    └── script_examples
    └── genIVT.pl

    The old documentation secure_boot.txt can be removed.

    Reviewed-by: Utkarsh Gupta
    Signed-off-by: Breno Lima

    Breno Lima
     
  • Add HABv4 documentation for i.MX8M and i.MX8MM targets covering the
    following topics:

    - How to sign an securely boot an flash.bin image.
    - How to extend the root of trust for additional boot images.
    - Add 2 CSF examples.

    Reviewed-by: Utkarsh Gupta
    Signed-off-by: Breno Lima

    Breno Lima
     

03 Nov, 2018

2 commits


23 Oct, 2018

2 commits

  • Add HABv4 documentation for u-boot-dtb.imx targets covering the
    following topics:

    - How to sign an securely boot an u-boot-dtb.imx image.
    - How to extend the root of trust for additional boot images.
    - Add 3 CSF examples.
    - Add IVT generation script example.

    Reviewed-by: Ye Li
    Reviewed-by: Utkarsh Gupta
    Signed-off-by: Breno Lima

    Breno Lima
     
  • The HABv4 is supported in i.MX 50, i.MX 53, i.MX 6, i.MX 7,
    series and i.MX 8M, i.MX8MM devices.

    Add an introductory document containing the following topics:

    - HABv4 Introduction
    - HABv4 Secure Boot
    - HABv4 Encrypted Boot
    - HAB PKI tree generation
    - HAB Fast Authentication PKI tree generation
    - SRK Table and SRK Hash generation

    Reviewed-by: Ye Li
    Reviewed-by: Utkarsh Gupta
    Signed-off-by: Breno Lima

    Breno Lima
     

09 Oct, 2018

8 commits


11 Mar, 2018

2 commits

  • The README.mxc_hab is outdated and need improvements, add the following
    modifications:

    - Reorganize document and remove duplicate content
    - Add CST download link
    - Update CST package name
    - Align command lines with CST v2.3.3
    - Update U-Boot binary name
    - Remove CSF padding since is not documented in AN4581

    Signed-off-by: Breno Lima

    Breno Lima
     
  • Currently the High Assurance Boot procedure is documented in two
    places:

    - doc/README.imx6
    - doc/README.mxc_hab

    It is better to consolidate all HAB related information into
    README.mxc_hab file, so move the content from README.imx6 to
    README.mxc_hab.

    Signed-off-by: Breno Lima
    Reviewed-by: Fabio Estevam

    Breno Lima
     

24 Feb, 2018

1 commit


10 Feb, 2018

1 commit

  • README.efi describes two different concepts:
    * U-Boot exposing the UEFI API
    * U-Boot running on top of UEFI.

    This patch splits the document in two.
    Religious references are removed.

    The separation of the concepts makes sense before detailing the internals
    of U-Boot exposing the UEFI API in a future patch.

    Signed-off-by: Heinrich Schuchardt
    Signed-off-by: Alexander Graf

    Heinrich Schuchardt
     

08 Feb, 2018

1 commit


04 Feb, 2018

5 commits

  • Tom Rini
     
  • The original text is from the time that the config options were not
    converted to Kconfig.

    After the conversion to Kconfig only CONFIG_SECURE_BOOT and
    CONFIG_CMD_DEKBLOB need to be selected by the user.

    The other config options are automatically selected by the Kconfig
    logic.

    Signed-off-by: Fabio Estevam
    Reviewed-by: Breno Lima

    Fabio Estevam
     
  • The EFI implementation does not fit into any of the existing categories.

    Provide LOGC_EFI so that EFI related message can be filtered.

    Signed-off-by: Heinrich Schuchardt
    Reviewed-by: Simon Glass

    Heinrich Schuchardt
     
  • When functions return an error it propagates up the stack to the point
    where it is reported. Often the error code provides enough information
    about the root cause of the error that this is obvious what went wrong.

    However in some cases the error may be hard to trace. For example if a
    driver uses several devices to perform an operation, it may not be
    obvious which one failed.

    Add a log_ret() macro to help with this. This can be used to wrap any
    error-return value. The logging system will then output a log record when
    the original error is generated, making it easy to trace the call stack
    of the error.

    This macro can significantly impact code size, so its use is controlled
    by a Kconfig option, which is enabled for sandbox.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • Add some notes about recent new features.

    Signed-off-by: Simon Glass

    Simon Glass
     

31 Jan, 2018

1 commit


30 Jan, 2018

1 commit


29 Jan, 2018

1 commit


26 Jan, 2018

1 commit