• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 82 subscribers
  • Views 277 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F28386D: ECAP GPIO problem.

Ramon Martins
Prodigy 216 points

Part Number: TMS320F28386D
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi there,

I'm having an issue involving the eCAP peripheral. I'm using eCAP3 to capture the signal frequency from GPIO23, but the CTR register is overflowing and never transferring the value to the CAP1 register.

I’ve already checked the INPUTSEL setting — it’s set to 118 (I'm using SysConfig), and the module is in continuous mode.

I also tried changing the INPUTSEL to route a signal from the XBAR, and with that change, the peripheral works fine.

I also checked GpioDataRegs.GPADAT.GPIO23, and the register toggles normally between 0 and 1 as expected, but CAP1 still doesn’t update.

To reserve GPIO23, I configured it as a synchronous floating input.

Am I missing something? Are there any specific configurations I need to apply to GPIO23 before using it with eCAP?


Thank you for your guidance!

  • 0
    TI__Mastermind 27736 points

    Hi Ramon,

    Can you screenshot me the exact set up you're using in SysConfig?

    Input should be from GPIO23, or if you're routing through inputxbar then you'll just need to make sure the eCAP's input is coming from INPUTXBAR of your choice.

    Other than that I would scope your GPIO signal just to make sure there is output, then double check your eCAP settings for the rising/falling edge logic, and read any of the capture flags to see if tthey get triggered.

    Best regards,

    Ryan Ma

  • 0 in reply to Ryan Ma
    Prodigy 216 points

    Hi Ryan,

    I already "solved" the problem changing the ecap instance from "ECAP3" to "ECAP1", for some reason the "ECAP3" doesn't capture the "GPIO23", i haven't tested for other GPIOs. Could this be a problem in the my MCU? Currently i don't have another MCU available to test, as soon as i get another, i return with a response.

    Either way, i will let attached a print of the ecap configuration.

    Thank you.

    Ramon. 

  • 0 in reply to Ramon Martins
    TI__Mastermind 27736 points

    Hi Ramon,

    I have not had time to test this. But will be trying to get to this tomorrow. Apologize for the delay in response.

    Best regards,

    Ryan Ma

  • +1 in reply to Ryan Ma
    TI__Mastermind 27736 points

    Hi Ramon,

    I was able to sync up with the internal team on this to figure out why ECAP3 does not capture GPIO23. There is a documentation bug and we will file a ticket to get this updated in our documentation. ECAP2 and onwards does not have GPIO23 as an input and is tied to 0. We will get this fixed in our next release.

    Thank you for bringing this to our attention.

    Best regards,

    Ryan Ma