SPRADN0 December   2024 F29H850TU , F29H859TU-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Programming Fundamentals
  5. 2Introduction
    1. 2.1 Hardware Security Module
    2. 2.2 ROM Bootloader
    3. 2.3 Combined Image with X.509 Certificate
  6. 3Flash Kernel Implementation
    1. 3.1 CPU1 Firmware Upgrade (HS-FS)
    2. 3.2 Key Provision (HS-FS to HS-KP)
    3. 3.3 CPU1 Secure Firmware Upgrade (HS-KP/SE to HS-SE)
    4. 3.4 HSM Firmware Upgrade (HS-KP/SE to HS-SE)
    5. 3.5 SECCFG Code Provisioning (HS-KP/SE to HS-SE)
  7. 4Host Application: UART Flash Programmer
    1. 4.1 Overview
    2. 4.2 Build UART Flash Programmer with Visual Studio
    3. 4.3 Build UART Flash Programmer with CMake
    4. 4.4 Packet Format
    5. 4.5 Kernel Commands
  8. 5Example Usage
    1. 5.1 Loading the Flash Kernel onto the Device
      1. 5.1.1 Hardware Setup
      2. 5.1.2 Running the UART Flash Programmer
    2. 5.2 CPU1 Device Firmware Upgrade (HS-FS only)
    3. 5.3 Convert HS-FS to HS-SE
    4. 5.4 Loading a RAM-based HSMRt Image
    5. 5.5 Key Provision (HS-FS to HS-KP)
    6. 5.6 Code Provision (HS-KP/SE to HS-SE)
  9. 6Troubleshooting
    1. 6.1 General
    2. 6.2 UART Boot
    3. 6.3 Application Load
  10. 7Summary
  11. 8References

Build UART Flash Programmer with Visual Studio

UART flash programmer can be compiled and run as a Visual Studio project.

  1. Navigate to the uart_flash_programmer directory.
  2. Double click the uart_flash_programmer.sln to open the Visual Studio project.
  3. When Visual Studio opens, select Build → Build Solution.
  4. After Visual Studio completes the build, select Debug → uart_flash_programmer properties.
  5. Select Configuration Properties →Debugging.
  6. Select the input box next to the Command Arguments.
  7. Type the parameter arguments. The arguments are described in Section 4.1.
    • Example:
      -d f29h85x –k flash_kernel.bin –a application.bin –p COM34
  8. Click Apply and OK.
  9. Select Debug → Start Debugging to begin running the project.
  10. The output from Visual Studio command prompt needs to match what is shown in Figure 5-1.