ADC Driver - Channels, Groups, Triggers - MCAL & Driver Development

ADC MCAL Concepts

Concept	Description	Example
ADC Channel	One analog input pin; maps to one ADC converter input	ADC_CH_TPS = AN3, ADC_CH_MAP = AN4
ADC Group	A set of channels converted together; trigger and result buffer shared	GROUP_ENGINE_SENSORS = {TPS, MAP, COOLANT, O2}
Trigger source	What starts the group conversion: SW trigger, HW (GPT, PWM), continuous	Continuous: convert all group channels in loop; SW: start on demand
Conversion mode	One-shot (convert once, stop) or continuous (loop until stopped)	Sensor monitoring: continuous; on-demand calibration: one-shot
Result buffer	RAM array where MCAL writes ADC results; application reads from here	Adc_ValueGroupType g_sensor_buf[4]
Streaming access	Circular buffer: MCAL keeps last N conversions per channel	Adc_GetStreamLastPointer() for last result

ADC Group Configuration

Cadc_cfg.c

/* ADC configuration: engine sensor group */
#include "Adc.h"

/* Channel IDs (generated by configurator) */
#define ADC_CH_TPS      ((Adc_ChannelType)3u)  /* AN3: throttle */
#define ADC_CH_MAP      ((Adc_ChannelType)4u)  /* AN4: manifold pressure */
#define ADC_CH_COOLANT  ((Adc_ChannelType)5u)  /* AN5: coolant temp */
#define ADC_CH_O2_PRE   ((Adc_ChannelType)8u)  /* AN8: lambda pre-cat */

const Adc_ChannelType Adc_EngineSensorChannels[] = {
    ADC_CH_TPS, ADC_CH_MAP, ADC_CH_COOLANT, ADC_CH_O2_PRE
};

const Adc_GroupConfigType Adc_GroupConfig[] = {
    {
        .AdcGroupId              = ADC_GROUP_ENGINE_SENSORS,
        .AdcGroupAccessMode      = ADC_ACCESS_MODE_SINGLE,
        .AdcGroupConversionMode  = ADC_CONV_MODE_CONTINUOUS,
        .AdcGroupTriggerSource   = ADC_TRIGG_SRC_SW,  /* SW triggered */
        .AdcGroupSamplingTime    = ADC_SAMPLING_TIME_16CYCLES,
        .AdcGroupChannelList     = Adc_EngineSensorChannels,
        .AdcGroupChannelCount    = 4u,
        .AdcStreamNumSamples     = 1u,          /* single sample */
        .AdcNotification         = Adc_EngineSensors_Notification,
    },
};

/* Setup: call once before first conversion */
static Adc_ValueGroupType g_engine_buf[4];

void Adc_EngineSensors_Init(void)
{
    Adc_Init(&AdcConfig);
    Adc_SetupResultBuffer(ADC_GROUP_ENGINE_SENSORS, g_engine_buf);
    Adc_StartGroupConversion(ADC_GROUP_ENGINE_SENSORS);
}

Reading ADC Results in IoHwAb

Cadc_read_iohwab.c

/* IoHwAb: read ADC group results and convert to physical values */
#include "Adc.h"
#include "IoHwAb_Adc.h"

static Adc_ValueGroupType g_engine_buf[4];  /* TPS, MAP, COOLANT, O2 */

/* Called from notification (ADC group complete) or polled 10ms task */
void Adc_EngineSensors_Notification(void)
{
    /* Read results atomically */
    (void)Adc_ReadGroup(ADC_GROUP_ENGINE_SENSORS, g_engine_buf);
    /* Signal application layer: new data available */
    IoHwAb_SetAdcGroupReady(IOHWAB_GROUP_ENGINE_SENSORS);
}

/* Physical conversion: 12-bit ADC, 0-5V reference */
#define ADC_TO_MV(raw)   (((uint32)(raw) * 5000u) / 4095u)

float32 IoHwAb_GetTPS_Degrees(void)
{
    uint32 mv = ADC_TO_MV(g_engine_buf[0]);  /* TPS is index 0 */
    /* 0.5V - 4.5V = 0 - 90 degrees */
    if (mv < 500u)  mv = 500u;
    if (mv > 4500u) mv = 4500u;
    return 90.0f * (float32)(mv - 500u) / 4000.0f;
}

float32 IoHwAb_GetCoolantTemp_DegC(void)
{
    /* NTC lookup: ADC raw to temperature (linearised) */
    uint16 raw = g_engine_buf[2];  /* COOLANT is index 2 */
    /* Steinhart-Hart coefficients for NTC 10k beta=3950 */
    /* Simplified linear fit for -40 to +150 degC range */
    return 150.0f - ((float32)raw / 4095.0f) * 190.0f;
}

Summary

The most common ADC MCAL mistake is calling Adc_ReadGroup() before Adc_SetupResultBuffer() - the MCAL writes results to an uninitialised pointer, causing a data bus fault or silent memory corruption. A close second: starting an ADC group conversion in continuous mode, then calling Adc_StopGroupConversion() from a lower-priority task while a higher-priority task is reading g_engine_buf - producing a torn read of partially-updated ADC results. The Adc_ReadGroup() function copies results from the MCAL internal buffer atomically, so calling it from the notification callback (which runs in ADC ISR context) is safe. Reading directly from g_engine_buf without Adc_ReadGroup() is not guaranteed to be atomic.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.