Abstract

Abstract: Chrome OS has a six-week release cycle. In the wild, there are devices from a dozen manufacturers and hundreds of different models and configurations. This presents an interesting testing problem (once you “brick” your first school district with an update you never want to do it again). The Chromebook hardware thus extends the hooks used for bring-up and debugging to enable automation in the test lab, and more recently we adapted this to RMA and in-store returns. I will discuss the evolution of the debug system over the last 9 years.

Bio: Mark Hayter is currently a visitor from industry with the Computer Architecture team in the Computer Lab. He is Sr Engineering Director in the Chrome OS Hardware team at Google. The team is responsible for reference implementations and developing new technologies for Chromebooks. Prior to that he was involved in systems architecture at several semiconductor companies, being VP of Systems Engineering at P.A. Semi, Inc. (acquired by Apple Inc.), Senior Manager of Hardware Systems Engineering at Broadcom Corporation and System Architect at SiByte, Inc. Earlier, he was at the Digital Equipment Corporation Systems Research Center. He holds a PhD from the University of Cambridge Computer Laboratory.