SPRADK6 September   2024 TMS320F280039 , TMS320F280039-Q1 , TMS320F280039C , TMS320F280039C-Q1 , TMS320F280049 , TMS320F280049-Q1 , TMS320F280049C , TMS320F280049C-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2Challenge of Implementing LLC Control in MCU
    1. 2.1 Frequency Changing Requires Multiple PWM Configuration update
    2. 2.2 No Fixed Timing Relationship Between Control and Switching Frequency
  6. 3Corner Cases and Real-Case Challenges
    1. 3.1 Software Workaround
    2. 3.2 CLB-Based Hardware Workaround
  7. 4Summary
  8. 5References

CLB-Based Hardware Workaround

Though the software workaround is simple, but would require extra code and CPU bandwidth to monitor the PWM time base counter, and needs to spend CPU cycles waiting for the available timing for PWM register update. For a typical register update including TBPRD, CMPx and TBPHS register, it requires ~50 CPU cycles, which equals ~0.5μs for a 100Mhz CPU, which takes 5% for 100kHz interrupt.

 CLB Workaround Block DiagramFigure 3-3 CLB Workaround Block Diagram

Another options is to implement the PWM updating nesting logic in the configurable logic block (CLB). The solution introduce original control interrupt signal and a PWM updating forbidden signal in to CLB, and generate another CLB interrupt to trigger the real control loop interrupt. With the logic inside CLB, all the original control interrupts happen during the PWM updating forbidden signal will be nested, so no control loop interrupt will be triggered, and all the risk of PWM disorder will the eliminated.

 CLB Tile ConfigurationFigure 3-4 CLB Tile Configuration
 CLB Workaround Testing ResultFigure 3-5 CLB Workaround Testing Result