Google’s chromebooks and routers use off the shelf Microcontrollers (MCU) todo power sequencing, fan control, PWM and other hardware control tasks onetypically encounters in embedded systems. Interestingly enough the firmware isavailable under (3 clause) BSD license and thus open for hacking, abusing andmodifying to your needs. We’ll look at a bunch of MCU options and eval boards to get started with,their availability and pricing in low quantities as well as ways to hook themup to your embedded platform. Moreover we’ll look at hardware levelrequirements your SoC / board will have to provide in order to make it allwork. We’ll cover existing driver / software support in upstream Linux and U-Boot,as well as parts that are or were missing. Typical tasks of an embedded controller for a chromebook or random otherdevices like mine - which is everything but a laptop - will be discussed.Topics covered will include boot selection, firmware upgrades, watchdog timersand others. Finally I’ll share my experiences building a real world Zynq based systemusing chromium-ec on an STM32 MCU and my experiences adapting the software tomy needs and interacting with the community. Examples include replacing thecoreboot bootflow with U-Boot, creating device drivers for things like buttonsand issues encountered in making things work.