CCS/CC1352P: ADC share with System CPU and Sensor Controller on CC1352

But I get an exception in TI !! how I can use them on both sides?
I have 5 ADC channel with different pins, I want to measure one pin with SC and all the rest with TI CPU.
stop the SC while Other ADC measure and start it again after not successful as well and got an exception...!

I have to check this in more detail, but why do you want to use the ADC both from the CM3 and the SC side? Why not do everything from one domain?

I have one IR ADC channel measurement every 50ms that implemented in the SC in order to reduce power consumption.
and more 4 ADC channels that measuring very occasionally(hours/days) with CM3 and all their modules files are already implemented and common for other projects that doesnt have SC. so i must use both.

note: all the ADC hannels with differnt PINS. (Not need sc_Reint () )

thanks

Hi Moshe,

Could you be more specific on what exception you are getting? As for SC and peripheral sharing, there is example code available for the ADC case:

// Acquire the ADC
fwAcquirePeripheral(PERIPHERAL_ADC);

// Select ADC input
adcSelectGpioInput(AUXIO_A_SENSOR_OUTPUT);

// Enable the ADC (fixed reference, 2.7 us sample time, manual trigger)
adcEnableSync(ADC_REF_FIXED, ADC_SAMPLE_TIME_2P7_US, ADC_TRIGGER_MANUAL);

// Sample the sensor and store the ADC value
adcGenManualTrigger();
adcReadFifo(output.adcValue);

// Disable the ADC
adcDisable();

// Release the ADC
fwReleasePeripheral(PERIPHERAL_ADC);

Hi M-W

as I mentioned before I already use this example for SC side ADC implement with peripheral sharing.
in addition I Acquire the ADC hardware semaphore for the AUX ADC (AUX_SMPH_2 in AUX_SMPH) in CM3 side.
I got exception at ADCBuf_open() in MCU side after enable the SC . (while opening it jump to callback function(why ??) and then got exception in ADCBuf_adjustRawValues() )
the exception occurs also after SC disable. if i not enabling the SC the ADC measurement for 4 channels is great!

Hi Moshe,

I might have a clue to what could be going on. Could you break point on the ADCBuf_open() call and check if "AUX_ADC_IRQ" is set in the AUX_EVCTL->EVSTAT3 register?

Hi,
the AUX_ADC_IRQ is '0' in the AUX_EVCTL->EVSTAT3 register after try to measure another ADC PIN after enabling the SC.
but I notice that after calling: || HwiP_construct(&(object->hwi), INT_AUX_ADC_IRQ, ADCBufCC26X2_hwiFxn, &paramsUnion.hwiParams) ||
in ADCBufCC26X2_open the MCU jumps to ADC callback function (??!!) and then got exception.(in ADCBuf_adjustRawValues() )

the AUX_ADC_IRQ in AUX_EVCTL->EVTOMCUFLAGS is High!! but the AUX_ADC_IRQ in EVTOMCUCUPOL(select the event source level reg) is still in high level.

I did a test without sensor controller :
I Break before ADCBuf_open and change the EVTOMCUCUPOL->AUX_ADC_IRQ to Low level and I switch again to High level as before.
the EVTOMCUFLAGS ->AUX_ADC_IRQ is set high because the change, then i clear it.
this scenario effect the same result that i see with SC Enable.

Hi Moshe,

Can you try to add the following before the open call and see if it solves your issue?

HWREG(AUX_EVCTL_BASE + AUX_EVCTL_O_EVTOMCUFLAGSCLR) = ADC_IRQ; (HWREG(0x400C5038) = 1 << 10;)

Hi M-W ,

it didn't solve this issue.

Hi,

it seems that change the EVTOMCUCUPOL->AUX_ADC_IRQ cause the exception even if the flag is cleared.

Hi Moshe,

Do you have a example project your testing this with that you can share with me?

HI Moshe,

I saw you rejected the solution, I found it to be working on my example, have you have time to try it out?

Hi H-W ,

Yes, I have time and willingness to try it

Great!

I would recommend you add the ADCBufCC26X2.c file to your project and add the changes straight into the ADCBufCC26X2_open() function.