AWR1642BOOST: Triggering more than one general purpose ADC (GPADC) measurement

Erik Larsen

Part Number: AWR1642BOOST

Hello;

I'm working on collecting measurements from the GPADCs. I can successfully initialize the GPADCs with:

rlSetGpAdcConfig(RL_DEVICE_MAP_INTERNAL_BSS, (rlGpAdcCfg_t*)&gpAdcCfg);

This will cause one asynchronous event to take place within the "MmwDemo_mssMmwaveEventCallbackFxn" (there is also an event on the DSS which is ignored), at which point the ADC is stored. The ADC measurements are correct when I report them, but I do not know how to trigger additional ADC measurements without calling this each and every time:

rlSetGpAdcConfig(RL_DEVICE_MAP_INTERNAL_BSS, (rlGpAdcCfg_t*)&gpAdcCfg);

Each call to rlSetGpAdcConfig takes many hundreds of milliseconds to complete and isn't a sustainable way to obtain a single set of ADC measurements.

Is there an easier way to repeatedly measure the GPADCs?

Thanks,
Erik

over 7 years ago

0 Raghunandan Kamath over 7 years ago

TI__Mastermind 22155 points

Erik,

Did you perform profiling on this API to check the execution time?

-Raghu

0 Erik Larsen over 7 years ago in reply to Raghunandan Kamath

Expert 1095 points

Raghu,

It turns out verifying a valid rl driver handle takes a lot of time (rlDriverGetHandle()).

After that was removed, the rlSetGpAdcConfig() takes a negligible amount of time in comparison.

Thanks,
Erik

0 Kaushal Kukkar over 7 years ago in reply to Erik Larsen

TI__Expert 7215 points

Hi Erik,

Good that you are able to use rlSetGpAdcConfig()..

We will check the modification you had to do to make it work faster, though the function is just returning a pointer and not doing any operations.

Regards,

Kaushal

0 Erik Larsen over 7 years ago in reply to Kaushal Kukkar

Expert 1095 points

Kaushal,

As a note, all of these trials have been running through the debugger. In some other profiling I've done with other API functions, I've noticed orders of magnitude of timing differences when running in deployment mode versus debugging mode.

Typically, slow API calls in debugging mode are not slow when in deployment mode. This is not surprising to me. I have not ran this specific GPADC profiling in deployment mode.

Thanks,
Erik

0 Kaushal Kukkar over 7 years ago in reply to Erik Larsen

TI__Expert 7215 points

Erik,

In debugging mode, when you put breakpoints or console prints, debugger halts different clocks which would impact all the API calls.

Did you halt or enabled any debug prints during profiling?

Kaushal

Sensors

Sensors forum

AWR1642BOOST: Triggering more than one general purpose ADC (GPADC) measurement