<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Lvgl on alelec blog</title>
    <link>https://notes.alelec.net/tags/lvgl/</link>
    <description>Recent content in Lvgl on alelec blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 13 Apr 2026 10:00:00 +1000</lastBuildDate>
    <atom:link href="https://notes.alelec.net/tags/lvgl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Five Hours, Five Root Causes, Crisis Averted: A Case Study in Agentic Embedded Debugging</title>
      <link>https://notes.alelec.net/posts/five-hours-five-root-causes-crisis-averted/</link>
      <pubDate>Mon, 13 Apr 2026 10:00:00 +1000</pubDate>
      <guid>https://notes.alelec.net/posts/five-hours-five-root-causes-crisis-averted/</guid>
      <description>&lt;p&gt;&lt;img alt=&#34;MCU development board with portrait LVGL keyboard display&#34; loading=&#34;lazy&#34; src=&#34;https://notes.alelec.net/assets/lvgl_perf/Microcontroller_board_with_202604112331.jpeg&#34;&gt;&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m developing a MicroPython-based product running on an NXP i.MX RT1176 (Cortex-M7 @ 1 GHz) with a 720x1280 MIPI DSI touchscreen driven by LVGL v9. It&amp;rsquo;s an embedded system, not a phone or PC. The on-screen keyboard was unusable. Each keypress took nearly 200ms to render, dropping to 1-2 FPS while typing, missing many keypresses entirely. This same LVGL keyboard widget is routinely used on much slower microcontrollers. Something was fundamentally wrong with how our system was configured, but the rendering stack is deep and the root cause wasn&amp;rsquo;t obvious.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
