I will develop bare metal c firmware for stm32 esp32 or avr with fpga
About this Gig
Embedded work here is Arduino sketches stacked on libraries. That works for a prototype not for a product that must survive in the field. I write firmware using register access, no HAL unless you want it. Every timer value comes from the datasheet. Every failure mode is covered.
What I actually do:
Register-level driver development. SPI, I2C, UART, ADC timers are written from scratch not borrowed. If a sensor has timing needs I read the datasheet and meet those needs.
Fault-tolerant design. Watchdogs that really reset. ADC recovery with logic. State machines that never get stuck. Systems that recover from sensor failure without the user noticing.
Firmware integration. Verilog for the FPGA, C for the MCU clean interface, between them. High-speed preprocessing, timing-critical logic, whatever the architecture requires.
Low-level debugging. An oscilloscope, simulations, ST link, keil and assembly verification.
What I will not do: paste code from a tutorial. Call it custom. Use a library when writing the driver myself would take an hour and save you a week later. Ship something I would not want to maintain.

