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.

IWR6843AOP: ePWM peripheral

Part Number: IWR6843AOP
Other Parts Discussed in Thread: IWR6843, AWR6843

Hi mmWave Team,

 For a current application I need a high frequency PWM signal output.

Here's what I already found (e2e thread more than two years ago): ePWM is not yet supported in mmWave SDK. We will consider supporting this in future Releases 

When can I expect a sdk driver for the ePWM peripheral? Is there a workaround until then (e.g. header files for setting manual configuration)?

thanks.

best regards, ruben

  • Hello

    The peripheral driver set for mmWave family of devices is common and IWR6843 doesn't have the peripheral support in SDK.

    As on now we do not plan to include this support. Can you please let us know how and where you are planning to utilize this module in your application so that we can consider the context for future inclusion.

    If you wish to use the peripheral we suggest you to see the technical reference manual of the device to get an understanding of the module and use it.

    Please make sure you understand the pinmux requirements wile doing so.

    Thank you,

    Vaibhav

  • Hello,

    I tried to implement the PWM signal on register level myself:

    • set pinmux via "Pinmux_Set_FuncSel()" - okay
    • set appropriate bits in the register memory - okay
    • set the ePWM peripheral clock "VCLK3"
      • I can't find details for "VCLK3" in the mmWave documentation in particular Clock Management? Is VCLK3 the same as MSS_VCKL? 
      • I tried to enable the clock, but the function failed:
        • "SOC_setPeripheralClock(socHandle, SOC_MODULE_EPWM1, SOC_CLKSOURCE_VCLK, 1, &errCode);"
        • How to enable the peripheral clock?

    best regards, ruben

  • Hello

    Can you please make sure all the elements in that line are defined and look for error code  definition sent out on the console.

    Thank you,

    Vaibhav

  • Hi,

    The Error Code says: "MMWAVE_ERRNO_SOC_BASE" + "Invalid Argument."

    But I can't see which argument is wrong:

    • socHandle … is a valid handle (see OOBDemo main.c) 

    • SOC_MODULE_EPWM1... is part of "enum SOC_ModuleId_e" (SDK3.4.0.3)
    • SOC_CLKSOURCE_VCLK … is part of "enum SOC_PeripheralClkSource_e" (SDK3.4.0.3)
    • clkDivisor == 1 -> why not?

    I call the function right after SOC_init() - hence before  BIOS_start(). I'm stumped!?

    best regards, ruben

  • Hello

    Have you looked at the content of the function and see how the module that is passed would be used within the function.

    That module doesn't need the clock to be configured separately it gets the default clock - please the Technical Reference Manual.

    I would suggest doing writes/read to the register area of the module and try configuring it based on the definitions provided in the TRM. If you see issues please let us know.

    Thank you,

    Vaibhav

  • Hi Valibhav,

     Oh. Yes. The ePWM module just work fine. The peripheral clock VCLK3 doesn't need to be enabled separately. Sorry, I missed that.

    Thank you! best regards, ruben

  • Hi Vaibhav,

    I have two similar questions.

    I am working with mmWave Carrier Card Platform and AWR6843 Standard Antenna Plug-in module. 

    • I have confusion regarding what clock ePWM module uses because there are different references to what drives TBCLK. The documentation I am using is TRM Literature Number: SWRU520E May 2017 – Revised May 2020.
      • In Figure 21-3. Time-Base Submodule Signals and Registers - page 2309, VCLK4 is mentioned as the source.
      • At all other places e.g 21.2.2.1 Purpose of the Time-Base Submodule, VCLK3 is mentioned as the source.
    • And my second question is there is no mention of what VCLK3 or VCLK4 are, what is their relation to MSS_VCLK.

    Kindly can you clarify both of these queries? Thanks in advance.

    Regards,

    Waleed

  • Hello Waheed,

    Seems like you have already filed a new ticket asking  the adjoint question. Lets continue there, if not please file one.

    Closing this one out.

    Thank you,

    Vaibhav