• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 83 subscribers
  • Views 214 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.

TMS320F28379D: using ADCSOCOUTSELECT

Mojo
Expert 1570 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: SYSCONFIG

Hi,

I have 2 SOCs working in the uC.

I would like to see them on 2 GPIOs.

can you please explain how this is possible:

1. how to use ADCSOCOUTSELECT - do I need to enable the two SOCs that I'm interested to see?

2. how to connect to the GPIOs ?

a code snippet would be much appreciated!

thanks!

  • 0
    TI__Genius 10845 points

    Hi,

    Can you elaborate more on what do you mean by SOCs working in the uC. Are these SOC trigger signals or the ADC SOCs?

    Thanks
    Vasudha

  • 0 in reply to Vasudha Bhadoria
    Expert 1570 points

    Hi,

    ADC SOCs.

    I have PWM1 trigger SOCA on CTR=PRD, and SOCB on CTR=ZRO

    I would like to see these SOC on a scope.

    Target here is actually to debug 2 DMA channels - one is triggered by SOCA, and one by SOCB. I suspect there's some issue with these DMA.

    If there's another method to see DMA triggering then I'm open to suggestions.

    thank you!

  • 0 in reply to Mojo
    TI__Genius 10845 points

    Hi

    I don't think it is possible to see the SOC signals on scope.

    Thanks
    Vasudha

  • 0 in reply to Vasudha Bhadoria
    Expert 1570 points

    In the TRM, figure 13-3 (ePWM submodules) it shows that you can generate a pulse for external ADC. So I believe this has to come out from some GPIO.

    The TRM doesn't explain anything about ADCSOCOUTSELECT but I think this is the starting point to generate SOC pulse on a GPIO.

    Can you please re-check your answer.

    thanks a lot!

  • 0 in reply to Mojo
    Expert 1570 points

    Hi TI team,

    any update on the above question?

    thank you.

  • +1 in reply to Mojo
    TI__Guru* 82230 points

    Mojo,

    You are correct on the definition of this signal, it essentially brings out the local ePWM generated SOCA/SOCB that would normally be routed to the internal ADC to trigger a conversion, and brings it to a pin.  Note that this will only show the signal at that level(and I believe will stretch it by 32 sysclk cycles); and not the actual SOCx that is generated inside the ADC which is where the confusion likely happened earlier in the thread.  We don't have a mechanism to bring the physical ADC local SOC signal out to a pin.

    On this device(and other gen3 devices), this signal is routed to the OutputX-bar, which can then be routed to a GPIO.

    The TRM gives more info on this, please check out page 1194 https://www.ti.com/lit/spruhm8

    For instance ADCSOCA can be routed via MUX13 position 1.

    You can also use Sysconfig to auto generate the C code to set all this up https://dev.ti.com/sysconfig You'll want to add a Output X-bar, and then select the correct mux that you'll find from the TRM above.

    Let me know if you have more questions.

    Best,

    Matthew

  • 0 in reply to MatthewPate
    Expert 1570 points

    Thank you!

    it works.