Hardware speaks in bits, and C is how you answer. Nearly every peripheral bring-up is the same loop: read the register map row, build the mask, write it, read it back to verify. Engineers who are fluent in that loop bring up drivers in an afternoon; everyone else spends a week toggling the wrong bit.
The core skills
Bit manipulation as a first language. Setting, clearing, toggling and testing individual bits with shifts and masks ā REG |= (1 << EN), REG &= ~(3 << MODE), if (REG & READY) ā is the vocabulary of every driver you'll ever write. Practice until masks feel like plain reading.
ā Bit manipulation and register programming
ā Hands-on bit manipulation exercises
Structs as register maps and sensor data. A well-laid-out struct overlays a peripheral's registers or packs a sensor reading (SensorReading_t with temperature, humidity, timestamp) into something every layer of firmware can share. Unions pull double duty for protocol payloads where the same bytes mean different things by message type.
ā Functions, structs, unions and macros
Functions, macros and the HAL habit. Raw register writes scattered through application code rot fast. A thin hardware-abstraction layer ā sensor_init(), sensor_read(), one place per peripheral ā means a pin change or a sensor swap touches one file, not forty. Know when a macro beats a function (and when it hides a double-evaluation bug).
Headers and sources that scale. One giant main.c dies at a few hundred lines. Split by peripheral and by concern, guard every header, keep ISRs thin and fast, and let the build tell you about mistakes with warnings-as-errors before the hardware does.
Start at the Embedded C deep track for the full six-part treatment. Share a driver snippet, a mask trick, or a HAL layout that survived contact with real hardware. Tag with c-lang.