• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 82 subscribers
  • Views 129 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.

TMS320F280049C: with DRV8353

Chad Coons
Prodigy 60 points
Part Number: TMS320F280049C


Hello,

We are moving from the 100 pin TMS320F280049C to the 64 pin package. The ADC inputs have all been routed to different pins. I have tried to adjust the HAL files to match the new inputs but I am not getting expected results. Debugging with live updates enabled, the adc readings for the current sense, voltage sense, and VDC bus are all floating around as if tied to nothing. 

I believe their is a configuration that I don't have set correctly but I cannot figure out what I'm missing. Below are my hal.c and hal.h files.

Any guidance would be much appreciated!

Thanks,

Chad

6242.hal.c5417.hal.h

  • 0
    TI__Guru 60865 points

    Hi Chad,

    Ultimately the calls to "ADC_setupSOC" will determine which ADC input pins are mapped to which SOCs. After these configurations run, I think you might want to use the expressions window to directly check that the values in the ADC HW registers are as expected.  Generally, everything you'd want to know would be in the AdcxRegs.ADCSOCyCTL register (so, for example, ADCA SOC0 info would be in the AdcaRegs.ADCSOC0CTL register, and you'd be primarily interested in the CHSEL and TRIGSEL fields). 

    If you aren't already, you can also directly look at the result registers to see if the issue is reading the results vs. configuring the SOCs.  For instance, the raw results for ADC A SOC0 would go to AdcaResultRegs.ADCRESULT0.