A software architect always pays his technical debts.
Notes from the field on NXP i.MX RT firmware engineering — board bring-up, secure boot, RTOS architecture, and taking products to series production. Short, hands-on, reproducible.
A software architect always pays his technical debts.
Notes from the field on NXP i.MX RT firmware engineering — board bring-up, secure boot, RTOS architecture, and taking products to series production. Short, hands-on, reproducible.
A TFT backlight can be dimmed by an MCU timer or by the display controller’s own PWM, set with the MIPI DCS brightness commands. What each option costs, what it frees up, and the traps when you move from one to the other.
How FlexSPI talks to a QSPI NOR on the i.MX RT1062: the two access paths, the LUT, the sampling clock that caps your frequency, and how to prove you run at full speed. Read speed is checked against the bus, write speed against the flash datasheet.
Five lessons from taking an i.MX RT control unit from first boot toward production: the bootloader that hides your SDRAM setup, the flash size nobody measured, writing the flash you execute from, firmware updates as a protocol, and surviving the power cut.
Secure boot on the i.MX RT10xx is a sequence of one-way steps. A production checklist in the order that avoids bricking boards: trust boundary, keys, signing, testing on an open part, fusing the SRK hash, encrypted XIP, closing the part, and locking debug.
How I run AI agents on real embedded work without losing control: one context file per repo, small task specs, separate implement and review agents, a human who merges every change, and a knowledge base that turns every proven fix into a reusable lesson.
What each IOMUXC pad-control field on the i.MX RT10xx actually does, how to derive its value from the schematic and the protocol spec instead of trusting generated defaults, and a microSD interface as a worked example.
GPIO, ADC and FlexPWM interrupts follow one NVIC pattern but differ in where the trigger lives and how the flag clears. Plus the audit that matters with FreeRTOS: which ISRs sit above the syscall barrier, and therefore must never touch a FreeRTOS API.
A free, open-source toolchain for arc42 architecture documents: AsciiDoc source next to the code, PlantUML diagrams as text, HTML and PDF from one source, and reviews that show exactly what changed.