Hi, I’m the Toradex AI Assistant.
I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.
Did you like my answer?

Hello! Thank you for your questions about display capabilities, frame buffers, and UI development options on Verdin modules.
1. Modules Supporting Multiple Frame Buffers (/dev/fb0, /dev/fb1):
Both the Verdin iMX8M Plus and Verdin AM62 modules support up to two independent display pipelines, and thus commonly expose multiple frame buffer devices (such as /dev/fb0 and /dev/fb1) depending on the specific Linux BSP, display interface usage, and kernel configuration. This multi-pipeline setup allows for independent content rendering on two separate displays.
More information on these modules can be found here:
Regarding Overlay/Video Playback with Crank Storyboard:
Crank Storyboard is a high-performance GUI tool, but out-of-the-box, hardware-accelerated blending of video (such as MP4 playback using the GPU) atop GUI elements often requires careful integration. The Verdin SoMs’ hardware display controllers can support multi-layer composition in hardware, but this must be supported by both the application stack and the chosen GUI toolkit. In practice, many GUI frameworks including Crank may not fully expose the ability to composite a hardware-decoded video stream above or below UI layers—sometimes only pure software decoding or limited icon/graphic overlay is possible.
The usage of multiple frame buffers (e.g., rendering video to /dev/fb1 and GUI to /dev/fb0) depends on both software support and hardware pipeline routing. On modern embedded Linux systems, especially with Wayland/Weston and GStreamer pipelines, the frame buffer interfaces may be abstracted behind DRM/KMS APIs, which are more suitable for advanced composition and video overlay use-cases in a hardware-accelerated manner.
2. Alternative UI Development Frameworks (Other than Qt and Crank Storyboard):
Besides Qt and Crank Storyboard, other alternatives supported on Toradex modules include:
-
TotalCross – An open-source SDK that enables you to develop cross-platform GUIs using Java or Kotlin, suitable for embedded Linux devices.
See here for more details
-
GTK+ / GNOME – A widely used C-based toolkit for Linux GUIs. Well supported in embedded scenarios, though not as feature-rich for HMI as Qt or Crank.
-
LVGL (Light and Versatile Graphics Library) – For lightweight 2D GUIs on resource-constrained hardware, sometimes used in conjunction with TorizonCore.
(LVGL project site)
-
Electron – For web-based UIs using JavaScript/HTML5, though more resource-demanding.
For more about GPU, display backends, and frameworks:
2D/3D Graphics Acceleration & GPU on embedded Linux
Summary:
- Both Verdin iMX8M Plus and Verdin AM62 support multiple frame buffers and dual display pipelines, provided the software stack (BSP and middleware) enables them as needed.
- Crank Storyboard may have some limitations rendering hardware-accelerated video overlays directly; more advanced video integration may require other toolkits or direct GStreamer/Wayland use.
- UI alternatives to consider: TotalCross, GTK+, LVGL, or Electron.
If you’d like guidance on setting up multiple displays or specific integration with video playback and frame buffers on your module, just let me know!
Best regards,
Toradex AI Assistant.