SLAAEC9 july   2023 MSPM0L1306 , MSPM0L1306

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2LFU Bootloader Features Overview
  6. 3Hardware and Software Setup
    1. 3.1 Hardware Requirement
    2. 3.2 Software Setup
  7. 4LFU Bootloader Implementation
    1. 4.1 LFU Bootloader and Application Projects
    2. 4.2 Memory Allocation
    3. 4.3 LFU Bootloader Implemented
    4. 4.4 LFU Application Code Implementation
      1. 4.4.1 The Linker Command File for Application
      2. 4.4.2 Peripheral and Interrupt Initialization
      3. 4.4.3 Debug for Application Project
    5. 4.5 Invoke Firmware Upgrade Process
  8. 5Host GUI Tool Introduction
    1. 5.1 LFU Firmware Update
    2. 5.2 Application Project Link Files Generation
    3. 5.3 Non-Main Flash Configuration Firmware Generation
      1. 5.3.1 Steps to Generate the Non-Main Flash Configuration Firmware
      2. 5.3.2 UNIFLASH Tool to Program the NONMAIN Flash Configuration Data
  9. 6LFU Bootloader Protocol
    1. 6.1 Packet Format and Core Commands
    2. 6.2 Special Commands in LFU Bootloader
    3. 6.3 Host Device Firmware Upgrade Flow
  10. 7Migration to Other MSPM0 Devices
  11. 8References

4.4.3 Debug for Application Project

The application projects cannot be downloaded and executed by CCS directly due to below reasons:

  • The interrupt vector table in generated linker command (cmd) file is not assigned to default address 0x0000 for device bootup.
  • No device module initialization function in application projects.
  • No FreeRTOS delay function can be used in the flash shared area.

Here is the recommended workaround to debug application projects.

  • Use the default cmd file in the SDK examples that interrupt vector table is assigned to address 0x0000 for bootup.
  • Use sysconfig tool to generate peripheral initialization code for application projects.
  • Replace FreeRTOS delay function with the function delay_cycles(); that is defined in SDK.