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.

LAUNCHXL-F28379D: Need information regarding Software implementation model for TI F28379D LaunchPad with BOOSTXL-BUCKCONV

Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: BOOSTXL-BUCKCONV

Dear Team,

Software implementation model (Matlab)for TI F280049C LaunchPad with BOOSTXL-BUCKCONV for Digital DC/DC Buck Converter Using Peak Current Mode Control example model one system initialization block is used, could you please let me know what is the purpose of this block. if I want to use TI F28379D LaunchPad then what change I have to do for this system initialization block. Adding existing block configuration for your reference.

configuration for F280049C LaunchPad. please share the configuration for TI F28379D LaunchPad.

link:in.mathworks.com/.../pcmc-example.html

Thanks,

Pratyay

  • Hi,

    I have reached to MathWorks team to support. Please expect response by tomorrow.

  • Sending a reminder to MW team this morning.

  • yes, waiting for a reply from the MW team.

  • I have sent reminder again this morning. It may be faster to post the question at MathWorks forum

    https://www.mathworks.com/matlabcentral/?s_tid=gn_mlc

  • Hi Pratyay,

    The System Initialization block enables us to add custom code within the generated code in the model_initialize() function.
    When this shipping example 'Digital DC/DC Buck Converter Using Peak Current Mode Control' is introduced, some of the features like ePWM XBAR are not supported by TI C2000 support package. Hence, the required changes are added as part of custom code using System Initialization block.

    The below code enables ePWM XBAR settings to enable the outputs of MUX1 and MUX0 for TRIP4 and TRIP5 respectively.
    This remains the same for F28379D as well to enable COMPL and COMPH outputs of CMPSS1 on TRIP4 and TRIP5 respectively.

    EPwmXbarRegs.TRIP4MUXENABLE.bit.MUX1 = 1; //Enable CMPSS1- COMPL trip on TRIP4 (TRIP4MUXENABLE)
    EPwmXbarRegs.TRIP5MUXENABLE.bit.MUX0 = 1; //Enable CMPSS1- COMPH trip on TRIP5 (TRIP5MUXENABLE)

    The below code is used to configure the internal reference voltage. This is not required for F28379D as it can be configured as required from config set of DAC and CMPSS.

    AnalogSubsysRegs.ANAREFCTL.all = 0;//3.3V Internal Ref
    AnalogSubsysRegs.CMPLPMXSEL.bit.CMP1LPMXSEL = 0x3;//ADCA source for COMPL-Postive input
    AnalogSubsysRegs.CMPHPMXSEL.bit.CMP1HPMXSEL = 0x3;//ADCA source for COMPH-Postive input

    The below code is used to drive T1 Trigger event of action qualifier in ePWM1. However, 0x8 is not supported by F28379D. The T1 event shall be selected from any of the supported events for F28379D and make the necessary configuration settings.

    EPwm1Regs.AQTSRCSEL.bit.T1SEL = 0x8; // CMPSS1- COMPH DCEVTFILT to drive Action qualifier T1 Trigger event

    The below code triggers ePWM1A to low on the configured trigger event for T1 and clears the Tripzone interrupt flags. This remains the same for F28379D as well.

    EPwm1Regs.AQCTLA2.bit.T1U = 1; // Set ePWMxA to low on T1 Trigger event
    EALLOW;
    EPwm1Regs.TZCLR.bit.DCAEVT1 = 1; // Clear COMPL Spurious Trip flags
    EPwm1Regs.TZCLR.bit.OST = 1; // Clear COMPL Spurious Trip flags
    EDIS;

    If you still face any difficulty in making the necessary configuration for F28379D, please contact MathWorks technical support team. When we have a support ticket, our internal process enables us to involve right people on this issue and we will immediately get in touch with you to understand the case in more detailed way.

    Please connect to us at:
    www.mathworks.com/support.html

    Best Regards,
    Ram Alla | MathWorks

  • Pratyay,

    I will close the thread from here. You can continue to debug on MathWorks forum if needed.