How do you approach reading a datasheet for a new sensor or microcontroller?
What the interviewer wants to hear
- Start with overview, block diagram and pinout
- Check electrical characteristics and absolute maximum ratings
- Study the interface: protocol, timing diagrams, register map
- Look for power-up sequence, reset and initialisation steps
- Read errata and application notes
Model answer
I start with the overview and block diagram to understand what the part does, then the pinout and package. Next I check the electrical characteristics: supply range, current in each mode, logic levels, and the absolute maximum ratings so the design stays safe. For the interface I read the protocol section closely, such as I2C address, SPI mode or maximum clock, along with the timing diagrams and the register map with reset values. I look for the power-up and initialisation sequence, for example a startup delay or a required configuration write before measuring. I always read the errata sheet, because silicon bugs can waste days, and the application notes for recommended circuits and example code. While reading, I note key numbers and open questions for the hardware engineer, and later compare the logic analyser trace with the timing diagrams.
Can you answer it under time pressure?
Take a timed easy round and get scored on every answer.
More easy Embedded Systems Engineer questions
- What is the difference between a microcontroller and a microprocessor?
- What is an interrupt, and how is it different from polling?
- Compare UART, SPI and I2C. When would you use each?
- Explain volatile and const in embedded C. Can a variable be both?
- When would you use bare-metal firmware versus an RTOS?
- What GPIO modes does a typical microcontroller pin support, and when would you use each?
- What is PWM, how is it generated on a microcontroller, and what is it used for?
- What is a bootloader in an embedded device, and why would a product need one?
- What is endianness, and how do you deal with it when exchanging data between devices?