• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 786 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

F29H850TU: About F29 HSM Q&A

Lawrence Wang
Intellectual 1400 points

Part Number: F29H850TU

Tool/software:

Hi, experts

My customer asked a few questions about F29 HSM.


1. When build cfg is set to FLASH, two bin files will be compiled, one with Cert and one without (as shown below).


a) Which one do they use when programming? What is the difference between the two?
b) For the bin file with the cert, will the chip's internal ROM boot validate it even if the HSM module is not used?


2.Is there any other way to disable the chip's JTAG/Debug port without using HSM to push Lifecycle?

  • 0
    TI__Genius 11081 points
    Lawrence Wang said:
    a) Which one do they use when programming? What is the difference between the two?

    The _cert.bin should always be used. F29x will not boot Flash code without a certificate. The first one is just the output of the compiler/linker; the build scripts then attach the certificate to satisfy the device boot requirements.

    Lawrence Wang said:

    b) For the bin file with the cert, will the chip's internal ROM boot validate it even if the HSM module is not used?

    Yes. If the certificate specifies so, an integrity check can be performed on the code even in HS-FS state. The default certificate does not enable the integrity check so there is no effect. Regardless, a certificate must always be present at 0x10000000.

    Lawrence Wang said:
    2.Is there any other way to disable the chip's JTAG/Debug port without using HSM to push Lifecycle?

    Yes. SSU JTAG and debug ZONE passwords can be enabled in SSUMODE3. If any of these passwords is set to all 0s or all Fs and the device is placed in SSUMODE3, the effect is that the debug port/ZONE is permanently locked. Please see the SSU chapter in the TRM for more details. Support for SSUMODE3 and setting passwords will be enabled in an upcoming release of the F29x SDK.

    Best regards,
    Ibukun

  • 0 in reply to Ibukun Olumuyiwa
    TI__Intellectual 1400 points
    1. The default certificate does not perform an integrity check. Does the integrity check for "non-default certificates" require the integration of HSM?
    2. Will there be a demo project or a user guide available to help my customer quickly utilize this feature (integrity check by certificate)? If so, when can  be released?
  • 0 in reply to Lawrence Wang
    TI__Intellectual 1460 points

    Hi Lawrence,

    In any case HSM is required, you can enable integrity check by changing the argument passed to the signing script in the post build steps:

    $(PYTHON) ${COM_TI_MCU_SDK_INSTALL_DIR}/tools/boot/signing/mcu_rom_image_gen.py --image-bin ${ProjName}.bin --core C29 --swrv 1 --loadaddr 0x10001000 --sign-key ${COM_TI_MCU_SDK_INSTALL_DIR}/tools/boot/signing/mcu_gpkey.pem --out-image ${ProjName}_cert.bin --device f29h85x --boot FLASH --img_integ no;

    regards,

    Anand