• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 81 subscribers
  • Views 936 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: Reg: DAC in F28379D

Prakash S20
Intellectual 395 points
Part Number: TMS320F28379D


Dear All,

I have downloaded the "buffdac_enable_cpu01" from resource explorer. The downloaded program is for to generate the 1.5 V DC output from the ADCINA0.

But I couldn't see the signal from that particular pin. Please suggest to me where I could have stuck.

Thank you,

Prakash S

 

  • 0
    TI__Mastermind 29451 points

    Hi Prakash,

    Can you provide more observations or details from your debug of  the issue?

    What hardware or eval board are you using? Did the code compile and load correctly?

    There is a note on the example:

    //! This example generates a voltage on the buffered DAC output,
    //! DACOUTA/ADCINA0 (HSEC Pin 9) and uses the default DAC reference setting
    //! of VDAC.
    //!
    //! When the DAC reference is set to VDAC, an external reference voltage
    //! must be applied to the VDAC pin. This can accomplished by connecting a
    //! jumper wire from 3.3V to ADCINB0 (HSEC pin 12).

    This example was created specifically for the F28379D control card. Did you apply a 3.3V voltage to the VDAC pin?

  • 0 in reply to Gus Martinez
    Intellectual 395 points

    Dear Gus Martinez,

    I am using an evaluation module, "LAUNCHXL_F28379D".  As far as my knowledge on this module, no such pin "VDAC" is available to connect the external 3.3V as a DAC reference. I am using internal reference only for DAC operations. 

    I deleted the previous project and import from resource explorer newly. Now it is working fine. I also did the same in earlier cases, but I don't know how it gets solved now.

    Thank you,

    Prakash S.