Dio, Port & IoHwAb Configuration - MCAL & Driver Development

DIO API Reference

Function	Parameters	Returns	Description
Dio_ReadChannel	ChannelId	Dio_LevelType (HIGH/LOW)	Read single pin
Dio_WriteChannel	ChannelId, Level	void	Write single pin
Dio_FlipChannel	ChannelId	Dio_LevelType (new level)	Toggle pin, return new level
Dio_ReadPort	PortId	Dio_PortLevelType (16-bit)	Read all pins on one port
Dio_WritePort	PortId, Level (16-bit)	void	Write all pins on one port
Dio_ReadChannelGroup	ChannelGroupIdPtr	Dio_PortLevelType (masked)	Read a group of pins (bitmask + offset)
Dio_WriteChannelGroup	ChannelGroupIdPtr, Level	void	Write a group of pins
Dio_GetVersionInfo	VersioninfoPtr	void	Module version info

IoHwAb Integration: Digital Output Pattern

Ciohwab_digital.c

/* IoHwAb digital output: relay control */
#include "IoHwAb_Dio.h"
#include "Dio.h"
#include "SchM_IoHwAb.h"

/* Symbolic channel mapping (project-specific) */
#define IOHWAB_CH_RELAY_FUEL_PUMP    DIO_CH_P10_0
#define IOHWAB_CH_RELAY_COOLING_FAN  DIO_CH_P10_1
#define IOHWAB_CH_RELAY_STARTER      DIO_CH_P10_2

/* State mirror: avoids reading back from hardware */
static Dio_LevelType g_relay_state[3] = {STD_LOW, STD_LOW, STD_LOW};

void IoHwAb_SetRelay(IoHwAb_RelayIdType relay_id, boolean active)
{
    Dio_ChannelType ch;
    Dio_LevelType   level = active ? STD_HIGH : STD_LOW;

    switch (relay_id) {
        case RELAY_FUEL_PUMP:   ch = IOHWAB_CH_RELAY_FUEL_PUMP;   break;
        case RELAY_COOLING_FAN: ch = IOHWAB_CH_RELAY_COOLING_FAN; break;
        case RELAY_STARTER:     ch = IOHWAB_CH_RELAY_STARTER;     break;
        default: return;
    }

    SchM_Enter_IoHwAb_RELAY();   /* critical section: prevent ISR race */
    Dio_WriteChannel(ch, level);
    g_relay_state[relay_id] = level;
    SchM_Exit_IoHwAb_RELAY();
}

boolean IoHwAb_GetRelay(IoHwAb_RelayIdType relay_id)
{
    if (relay_id >= RELAY_COUNT) return FALSE;
    return (g_relay_state[relay_id] == STD_HIGH) ? TRUE : FALSE;
}

Runtime Pin Direction Change

Port_SetPinDirection

Port_SetPinDirection() allows changing pin direction at runtime - but only for pins configured with PortPinDirectionChangeable = TRUE in the Port ARXML configuration.

Use case: bidirectional half-duplex communication pins (LIN, K-line), or power save (pull to known state when unused).

/* Switch from output to input at runtime */
Port_SetPinDirection(PORT_PIN_KLINE, PORT_PIN_IN);

/* Switch back to output */
Port_SetPinDirection(PORT_PIN_KLINE, PORT_PIN_OUT);

/* Refresh all pin directions after wakeup (power-glitch recovery) */
Port_RefreshPortDirection();

Summary

The DIO module is deceptively simple: two functions (ReadChannel, WriteChannel) cover 90% of GPIO use cases. The complexity is in the IoHwAb layer above it, which must translate between logical signal names (RELAY_FUEL_PUMP) and physical MCAL channel IDs, handle active-high vs active-low polarity, apply debouncing for inputs, and manage state mirrors for outputs. The critical section around Dio_WriteChannel (shown above with SchM_Enter/Exit) is essential for outputs that are also read by other tasks: without it, an ISR can read a partially-updated relay state and make a wrong decision.

🔬 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.