TMS570LC4357 eCAP module is not working correctly in capture mode

Umang Patel83

Other Parts Discussed in Thread: TMS570LC4357, HALCOGEN

I have been trying to get the eCAP modules up and running on the Hercules TMS570LC4357 Launchpad.The eCAP modules can be used for either PWM generation or as capture input. I was able to get eCAP2 and eCAP3 module up and running in capture mode. eCAP1 module is not accessible from any pin.

eCAP 4, eCAP 5, eCAP 6 modules are not working in the capture mode.

I have configured the eCAP modules 2-6 in PWM mode and was able to generate PWM using all of them. This means that the PINMUX is able to configure pins to the appropriate module. Could someone help me figure out what the problem might be?

over 10 years ago

0 Chuck Davenport over 10 years ago

TI__Guru 59540 points

Hello Umang,

I have forwarded your questions to one of our eCAP experts. They should get back with you shortly.

0 Sunil Oak over 10 years ago

TI__Mastermind 49120 points

Hi Umang,

Can you please upload your code project so I can take a look at the actual configuration of the eCAP modules and the PINMUX?

Regards,
Sunil

0 Umang Patel83 over 10 years ago in reply to Sunil Oak

Prodigy 200 points

4606.tms570_ecap.c 7142.tms570_ecap.h 4762.HL_pinmux.c

0 Sunil Oak over 10 years ago in reply to Umang Patel83

TI__Mastermind 49120 points

Thanks. Can you please upload the entire CCS project?

0 Umang Patel83 over 10 years ago in reply to Sunil Oak

Prodigy 200 points

Since part of my code is proprietary I don 't think I will be able to share my code without permission from my company's supervisor.

I have called the functions in the specified order in main.c

Test_eCAP();

eCAP_Init(eCAP2);
eCAP_Init(eCAP3);

eCAP_Sync_Clocks();

Where eCAP_Sync_Clocks will synchronize all modules initialized. Let me know if you need specific files from the project. If I try to initialize eCAP4 -eCAP6 it doesn't work. The counter does run and overflow in a synchronized manner but no inputs are triggered when a signal is provided to the respective pins on the Booster pack J6 and J8

0 Sunil Oak over 10 years ago in reply to Umang Patel83

TI__Mastermind 49120 points

Can you include the HALCoGen .dil and .hcg files? That will at least let me understand how the eCAP modules are initialized. I can then try and duplicate the setup on my end and analyze further.

Are you feeding a square wave as input to the eCAPx pins? On which pin(s) of the boosterpack connectors? What is the period and duty cycle of this square wave input?

0 Umang Patel83 over 10 years ago in reply to Sunil Oak

Prodigy 200 points

2821.LaunchpadTMS570LC4317.zip

Have a look at the HALCoGen project files above.

I don't think I have leveraged any code from the HALCogen project, expect maybe some section of the header files. Thanks a lot for the prompt response. I really appreciate it.

I am feeding all the capture pins with a square wave of 10 KHz and a duty cycle of 50 %. All the capture modules are triggered of the same signal. I have also initialized the proper ISRs. I tried forcing the interrupts for all modules which works and thus they are mapped correctly. Pins 4,5 for eCAP 4 and eCAP 5 respectively on J8 and Pin 3 for eCAP 6 on J6 connector.

Let me know if you need some specific files to recreate the project on your end.

You will need to add the ISRs to the s_vim_init[128U] array in the HL_sys_vim.c file and enable the interrupts channels 104-109 for all eCAP modules.

I am also attaching the header files that are in my project taken from the hcg/include folder in my project. I have leveraged my project from Project0 - blinky project provided by TI for the Launchpad TMS570LC4357

5545.HL_pinmux.h 4087.HL_ecap.h 6433.HL_reg_pcr.h

0 Sunil Oak over 10 years ago in reply to Umang Patel83

TI__Mastermind 49120 points

Can you please include the bodies of the Test_eCAP() and eCAP_Init() functions?

0 Umang Patel83 over 10 years ago in reply to Umang Patel83

Prodigy 200 points

Look below

0 Umang Patel83 over 10 years ago in reply to Sunil Oak

Prodigy 200 points

Those functions are included in the tms570_ecap.c file that I have attached in the posts above

0 Sunil Oak over 10 years ago in reply to Umang Patel83

TI__Mastermind 49120 points

Thanks. Sorry missed it in your earlier post.

0 Umang Patel83 over 10 years ago in reply to Sunil Oak

Prodigy 200 points

Hi Sunil,

Are you still working on the issue? Let me know if you need anything to replicate the setup on your end

0 Sunil Oak over 10 years ago in reply to Umang Patel83

TI__Mastermind 49120 points

Hi Umang,

Yes, I am still working on it. I had to take an unplanned day off yesterday and could not work on this, sorry about that.

I am creating a new HALCoGen project that outputs a 10KHz PWM on ePWM1A and then captures it on eCAP2,3,4,5,6. You are right in that eCAP1 input is not available on the Launchpad. I will send you the example code later today.

Regards, Sunil

0 Umang Patel83 over 10 years ago in reply to Sunil Oak

Prodigy 200 points

Great ! Let me know if you get the eCAP 4,5 and 6 working correctly along with eCAP 2 and 3. I was able to get all eCAP module counters to run and overflow synchronously but wasn't able to capture any signal

0 Charles Tsai over 10 years ago in reply to Umang Patel83

TI__Guru**** 191886 points

I think your pinmux is the problem.

You have:

pinMuxReg->PINMUX[81] = 0U;

This means that you are selecting the ECAP[4,5,6] bond pads that are not present in the ZWT package. Please change to:

pinMuxReg->PINMUX[81] = 0x02020202U;

You have the same problem for PINMUX[82]. You should change to pinMuxReg->PINMUX[82] = 0x02020202U also if you want to use eQEP modules in the future.

There are two bond pads associated with each eCAP module. One is present in the ZWT package and the other one is not. When you use eCAP as PWM, the signal goes to both pad cocurrently. So you will see PWM signal properly. When you use eCAP for input capture there is a mux that will select either inputs (one that is present in ZWT and the other not present in ZWT). You happen to select the one that is not present in the ZWT package.

0 Umang Patel83 over 10 years ago in reply to Charles Tsai

Prodigy 200 points

Thanks a lot for your help. I just made the changes and it works perfectly. It wasn't very apparent from the datasheet or the manual that additional changes are required to the PINMUX logic, atleast from a first glance.

Arm-based microcontrollers

Arm-based microcontrollers forum

TMS570LC4357 eCAP module is not working correctly in capture mode