This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

[参考译文] AM623:定制电路板-主要作者

Guru**** 2482105 points


请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1452636/am623-custom-board---key-writer

器件型号:AM623

工具与软件:

您好!

成功更改 keywriter_setvpp ()函数以启用1.8 Vpp 后,我仅使用./ gen_keywr_cert.sh -t tifek/ti_fek_public.pem --mSv 0xC0FFE 创建了一个证书以用于测试。

并进行了刷写;现在、它仅通过 HS-SE 安全映像进行引导。

问题1。  在刷写 ti_fek_public.pem 后是否成为 HS-SE  ?

问题2: 如何检查 vpp 不闪烁的键,有没有任何功能,我可以评论和测试?

问题3。 刷写自定义主板不能自动重启后、如何调试此问题?  

此致、

-RJ

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好!

    1.否、该器件仅在对 KEYREV 字段进行编程后才转换为 HSSE。

    您可以参考以下常见问题解答来检查器件类型:

    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1228618/faq-am6xx-how-to-check-if-device-type-is-hs-se-hs-fs-or-gp

    2.您可以注释`keywriter_processKeyConfig`函数、如下所示:

    diff --git a/sbl_keywriter/am62x-sk/r5fss0-0_nortos/main.c b/sbl_keywriter/am62x-sk/r5fss0-0_nortos/main.c
    index ae6b0a8..aa68cba 100644
    --- a/sbl_keywriter/am62x-sk/r5fss0-0_nortos/main.c
    +++ b/sbl_keywriter/am62x-sk/r5fss0-0_nortos/main.c
    @@ -57,7 +57,7 @@ int main()
         keywriter_setVpp();
         DebugP_log("Enabled VPP\r\n");
     
    -	keywriter_processKeyConfig();
    +	// keywriter_processKeyConfig();
     
         Drivers_close();
         System_deinit();
    

    3.请详细说明刷写步骤、启动模式等问题

    此致、

    Prashant

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    Prashant、您好!

    1. 否、器件仅在对 KEYREV 字段进行编程后才转换为 HSSE。

    这是我还想,但发生的是定制板被转换为 HS-SE ,

    SoC:   AM62X SR1.0 HS-SE
    Model: Texas Instruments AM625 SK
    EEPROM not available at 80, trying to read at 81
    Reading on-board EEPROM at 0x51 failed -121
    DRAM:  no bloblist found!2 GiB

    附加构建日志  

    /ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/scripts/cert_gen/am62x$ ./gen_keywr_cert.sh -t tifek/ti_fek_public.pem --msv 0xC0FFE
    # Using MSV[19:0]: 0x000C0FFE
    Generating Single signed certificate!!
    INFO: Using default key(s) for signing certificate(s)
    GEN: AES256 key generated, since not provided
    # encrypt aes256 key with tifek public part
    # encrypt SMPK-priv signed aes256 key(hash) with tifek public part
    # encrypt smpk-pub hash using aes256 key
    writing RSA key
    # encrypt smek (sym key) using aes256 key
    3994	primary_cert.bin
    3994	../../x509cert/final_certificate.bin
    # SHA512 Hashes of keys are stored in verify_hash.csv for reference..
    /ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/scripts/x509cert$ python3 ../../../../../tools/bin2c/bin2c.py final_certificate.bin keycert.h KEYCERT
    Traceback (most recent call last):
      File "/home/rj/ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/scripts/x509cert/../../../../../tools/bin2c/bin2c.py", line 13, in <module>
        *  Copyright (C) ''' + sys.argv[4] +''' Texas Instruments Incorporated
    IndexError: list index out of range
    /ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/scripts/x509cert$ python3 ../../../../../tools/bin2c/bin2c.py final_certificate.bin keycert.h KEYCERT 2022
    /ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/scripts/x509cert$
    
    
    /ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/am62x-sk/r5fss0-0_nortos/ti-arm-clang$ make -sj clean PROFILE=debug
    Cleaning: am62x:r5fss0-0:nortos:ti-arm-clang sbl_keywriter.debug.out ...
    /ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/am62x-sk/r5fss0-0_nortos/ti-arm-clang$ make -sj PROFILE=debug
    Generating SysConfig files ...
    Running script...
    Validating...
    Generating Code (example.syscfg)...
    Writing /home/rj/ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/am62x-sk/r5fss0-0_nortos/ti-arm-clang/generated/ti_dpl_config.c...
    Writing /home/rj/ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/am62x-sk/r5fss0-0_nortos/ti-arm-clang/generated/ti_dpl_config.h...
    Writing /home/rj/ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/am62x-sk/r5fss0-0_nortos/ti-arm-clang/generated/ti_drivers_config.c...
    Writing /home/rj/ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/am62x-sk/r5fss0-0_nortos/ti-arm-clang/generated/ti_drivers_config.h...
    Writing /home/rj/ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/am62x-sk/r5fss0-0_nortos/ti-arm-clang/generated/ti_drivers_open_close.c...
    Writing /home/rj/ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/am62x-sk/r5fss0-0_nortos/ti-arm-clang/generated/ti_drivers_open_close.h...
    Writing /home/rj/ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/am62x-sk/r5fss0-0_nortos/ti-arm-clang/generated/ti_pinmux_config.c...
    Writing /home/rj/ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/am62x-sk/r5fss0-0_nortos/ti-arm-clang/generated/ti_power_clock_config.c...
    Writing /home/rj/ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/am62x-sk/r5fss0-0_nortos/ti-arm-clang/generated/ti_board_config.c...
    Writing /home/rj/ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/am62x-sk/r5fss0-0_nortos/ti-arm-clang/generated/ti_board_config.h...
    Writing /home/rj/ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/am62x-sk/r5fss0-0_nortos/ti-arm-clang/generated/ti_board_open_close.c...
    Writing /home/rj/ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/am62x-sk/r5fss0-0_nortos/ti-arm-clang/generated/ti_board_open_close.h...
    Compiling: am62x:r5fss0-0:nortos:ti-arm-clang sbl_keywriter.debug.out: ../main.c
    Compiling: am62x:r5fss0-0:nortos:ti-arm-clang sbl_keywriter.debug.out: ../keywriter_utils.c
    Compiling: am62x:r5fss0-0:nortos:ti-arm-clang sbl_keywriter.debug.out: ../board.c
    Compiling: am62x:r5fss0-0:nortos:ti-arm-clang sbl_keywriter.debug.out: generated/ti_drivers_config.c
    Compiling: am62x:r5fss0-0:nortos:ti-arm-clang sbl_keywriter.debug.out: generated/ti_drivers_open_close.c
    Compiling: am62x:r5fss0-0:nortos:ti-arm-clang sbl_keywriter.debug.out: generated/ti_board_config.c
    Compiling: am62x:r5fss0-0:nortos:ti-arm-clang sbl_keywriter.debug.out: generated/ti_board_open_close.c
    Compiling: am62x:r5fss0-0:nortos:ti-arm-clang sbl_keywriter.debug.out: generated/ti_dpl_config.c
    Compiling: am62x:r5fss0-0:nortos:ti-arm-clang sbl_keywriter.debug.out: generated/ti_pinmux_config.c
    Compiling: am62x:r5fss0-0:nortos:ti-arm-clang sbl_keywriter.debug.out: generated/ti_power_clock_config.c
    .
    Linking: am62x:r5fss0-0:nortos:ti-arm-clang sbl_keywriter.debug.out ...
    Linking: am62x:r5fss0-0:nortos:ti-arm-clang sbl_keywriter.debug.out Done !!!
    .
    Boot image: am62x:r5fss0-0:nortos:ti-arm-clang /home/rj/ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_keywriter.debug.tiimage ...
    Boot image: am62x:r5fss0-0:nortos:ti-arm-clang /home/rj/ti/mcu_plus_sdk_am62x_09_02_01_06/source/security/sbl_keywriter/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_keywriter.debug.tiimage Done !!!
    

    谢谢!

    -RJ

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好!

    这是我也认为的,但发生了什么是定制板转换为 HS-SE ,

    使用该证书是不可能的。

    相反、您可能错误地启动了使用不同证书构建的 Keywriter 二进制(用于对密钥、keycnt 和 keyrev 进行编程)、从而将 SoC 转换为 HSSE。

    此致、

    Prashant