The code
Embedded C for Cortex-M. It compiles. There are 3 real bugs in it: the kind that pass a bench test and fail in the field.
void my_flush_cb(lv_display_t *disp, const lv_area_t *area,
uint8_t *px)
{
int32_t w = area->x2 - area->x1;
int32_t h = area->y2 - area->y1;
dma2d_copy(px, fb, area->x1, area->y1, w, h);
}What an interviewer expects
- Point to each line you'd stop in a code review.
- Say what actually breaks: the failure mode, not just the rule it violates.
- Fix it, then defend the fix when asked the follow-up.
The bugs, reference fixes and the follow-up question are in the practice app, after you've tried it.
Companies that test this
Matched on the skills each company's embedded roles emphasise.
MediaTekChipmaker · India hiring: MediumMeta Reality LabsConsumer devices · India hiring: LowNVIDIAChipmaker · India hiring: MediumSamsungConsumer devices · India hiring: HighThundersoftEngineering services · India hiring: MediumValeoAutomotive supplier · India hiring: HighAcsia TechnologiesEngineering services · India hiring: MediumAMD IndiaChipmaker · India hiring: Medium
Related challenges
ADC with circular DMADMA & graphics · Hard · 3 bugs · ~7 minLogging over UART with DMADMA & graphics · Medium · 3 bugs · ~5 minLTDC double bufferingDMA & graphics · Hard · 3 bugs · ~7 minTouch controller interruptDMA & graphics · Medium · 4 bugs · ~6 minSPI DMA on a cached coreDMA & graphics · Hard · 3 bugs · ~7 min
Flag the lines, say what breaks, then fix it and build it with clang in your browser.
Find the bugs