• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 81 subscribers
  • Views 394 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.

CCS/F28M35H52C: How to call AdcOffsetSelfCal() function

Yong Zhou1
Intellectual 310 points

Part Number: F28M35H52C
Other Parts Discussed in Thread: CONTROLSUITE

Tool/software: Code Composer Studio

Hello,

  I am using TI F28M35H52H DSP that contains a M3 core and a C28 core.  I am trying to use ADC zero offset calibration function described on page 907 of TI document spruh22g_Concerto by calling AdcOffsetSelfCal() function.  My questions are,

1.  Where I can find the source code of function?

2.  Since I have two cores, how should I call it (or call from which core or both cores)?

3.  Any other tip that I should know?

  Thanks,

  Yong

  • 0
    TI__Guru 62975 points

    Yong Zhou1 said:
    1.  Where I can find the source code of function?

    The controlSUITE example source is located here: C:\ti\controlSUITE\device_support\f28m35x\v220\F28M35x_common\source\F28M35x_Adc.c

    Yong Zhou1 said:
    2.  Since I have two cores, how should I call it (or call from which core or both cores)?

    The ADC configuration registers can only be accessed by the C28 core so the offset calibration cannot be performed by the M3.

    Yong Zhou1 said:
    3.  Any other tip that I should know?

    The offset calibration implementation in the AdcNOffsetSelfCal() functions can be modified to better fit the custom software.

    For example, the AdcNConversion() function uses ADCINTSOCSELn for ADC self-triggering. These settings also have the effect of conflicting with normal ADCSOC triggers. The developer is free to collect ADC samples using other triggering schemes in order to avoid resource conflicts.

    See the Errata for known device issues.