AM2434: Optimize ADC Data Update Function Execution Time

Hello Kevin,

Please try my suggestions below and confirm how much time is reduced.

Method 1 : 

In current customer implementation, we can't change time from ADC start to till ADC extraction.

Now, to reduce overhead, try the steps below.

After ADC extracts data, we called ADC stop. So, instead of calling the ADC stop API,

Just stop the ADC and wait for the ADC to idle.

code : 

/* Stop ADC */
ADCStart(baseAddr, FALSE);

/* Wait for FSM to go IDLE */
ADCGetSequencerStatus(baseAddr, &status);
while ((ADC_ADCSTAT_FSM_BUSY_IDLE != status.fsmBusy) &&
ADC_ADCSTAT_STEP_ID_IDLE != status.stepId)
{
ADCGetSequencerStatus(baseAddr, &status);
}

Next, instead of calling ADCconfig API, just enable steps.

code : 

    /* Step enable */
    for(chCnt = 0U; chCnt < APP_ADC_NUM_CH; chCnt++)
    {
        adcStep = ADC_STEP_1 + chCnt;   /* Step -> Channel one to one mapped */
        ADCStepEnable(baseAddr, adcStep, TRUE);
    }

Later, start the ADC.

Method 2 : 

Entire ADC functionality will be divided into 3 parts. ADC start, ADC stop and ADC processing.

Now, you can implement 3 ADC states. ADC_START, ADC_PROCESSING and ADC_STOP.

case ADC_START : Start ADC 

case ADC_PROCESSING : 

Here, you need to poll  if ADC conversion is completed or not.

If ADC conversion is completed, then extracting the ADC data and then move to the next state ADC stop.

case ADC_STOP : Stop the ADC, enable Steps and then move to ADC start state.

Method3 : 

Combine Method 1 and Method 2.

If user still wants to reduce the overhead further then they should go with the ISR method .

Method 4 : 

ISR Method : 

In the task, they need to start the ADC.

In the ISR routine , users need to extract the ADC data. Again, users need to start the ADC based on the previous conversion completion status in the task.

And other than these  methods, there are no methods to reduce further overhead.

Regards,

Anil.