- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Translated Content
- :
- Multi Source Translation Content
- :
- 1973466_en-US
1973466_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
1973466_en-US
1973466_en-US
we are working with customized board based on iMX8MQ and trying to make HDMI work in U-Boot on it. We are talking about HDMI from SOC, without MIPI-DSI to HDMI bridge.
We are using the following U-Boot version from NXP (customers request): lf_v2022.04, tag: lf-6.1.1-1.0.0.
Now we just guess that HMDI implementation may be very similar on iMX8MP and iMX8MQ, so we shouldn't spend time attempting to make HDMI work in U-Boot.
If possible, could you please clarify whether the HDMI video output is supported on reference EVK design with reference software from NXP?
Best regards,
Mikhail Vanyulin.
Hello @Bio_TICFSL,
thanks for your feedback!
The instructions under your link are for adjustment of video modes for the Linux kernel via U-Boot cmdline. We were not aware that it's possible to adjust corresponding nodes in device tree on the fly - thanks for sharing this knowledge.
But our problem was different - the HDMI video output did not work in U-boot on our iMX8MQ board out of box itself. Nevertheless we found the root cause - the HDMI video output started to work on our side when we loaded U-Boot binary from eMMC storage (instead of using serial download). At the moment we can't explain why there is such different in the behavior of the same U-Boot binary when it's loaded via serial. We are investigating this now. But we guess that there's some problem with memory mapping in our U-Boot, as other functionality (access to FPGA via I2C) also stops working when the U-Boot binary is loaded over serial.
Once again, thanks a lot for your help. Feel free to close this issue now.
Best regards,
Mikhail Vanyulin.
Hello,
Please check it this thread it may be helpful:
regards