CC2530: Using an ADC conversion sequence with Zstack

Hi Ryan,

yes i am using adc channels 0 and 1 for a conversion sequence triggered periodically by Timer1 using dma to transfer the data to memory. The point that i am trying to understand is if the extra sequence made by zstack (function HalAdcCheckVddRaw as you wrote) can be safely executed while my periodic conversion is running. I ask you this because I randomly noticed incorrect values when i get the result values of the adc sequence; they seem exactly equal to the value that the conversion made by HalAdcCheckVddRaw should return (3.3v). I think that there may be a data race when accessing the adc registers ADCH and ADCL that causes this behavior. Does anyone know if these two kind of adc uses can coexist at the same time (both extra conversion and conversion sequence)?

Hi Ryan,

how would you proceed about stopping the adc? I already tried modifying the function like this:

bool HalAdcCheckVdd(uint8 vdd)
{
bool res = FALSE;

halIntState_t his;
HAL_ENTER_CRITICAL_SECTION(his);

// Disable trigger on timer
ADCCON1 = 0x33;

// Wait until no conv is in progress
while (ADCCON1 & HAL_ADC_START);
ADCH; // Make sure eoc returned low
while (ADCCON1 & HAL_ADC_EOC);

ADCCON3 = 0x0F;
while (!(ADCCON1 & 0x80));
res = (ADCH > vdd);

HAL_EXIT_CRITICAL_SECTION(his);

// Enable trigger on timer
ADCCON1 = 0x23;

return res;
}

but i still randomly receive incorrect values, does it seem correct to you?

I am not sure about disabling OSAL_NV_CHECK_BUS_VOLTAGE, isn't it a bit risky?

Regards,

Daniele