2290707_en-US

[#1]

imx6 vxworks7.0 drawing

Using imx6q's gpu to draw two screen outputs, extremely occasional program error triggering data abort exception, operating system is using vxworks 7.0, what could it be related to? What are the known bugs?

Graphics & Displayi.MX6QuadRe: imx6 vxworks7.0绘图Thank you. We have encountered similar issues several times since 2022: the program crashes, leading to a failure of watchdog feeding and a hardware watchdog reset. Have other users reported similar problems? What are the known defects of the GPU driver for i.MX6Q under the VxWorks 7.0 operating system? Is it safe to enable two tasks for dual-screen rendering? If not, how can dual-screen display be implemented for i.MX6Q under the VxWorks 7.0 operating system?Re: imx6 vxworks7.0绘图

Hello,

When using VxWorks 7.0 for dual-screen GPU rendering on the i.MX6Q platform, extremely rare Data Abort exceptions occur, typically related to memory inconsistency, resource contention, or timing vulnerabilities in the Vivante GPU driver in multi-display controller (IPU) environments. The following are common causes and troubleshooting directions for this type of problem:

Memory Inconsistency and Cache Coherency This is the most common cause of Data Aborts in real-time operating systems such as VxWorks: 

GPU and CPU cache misalignment: The i.MX6Q's GPU is not within the ARM's Snoop Control Unit. If the application layer updates the video memory data but does not manually execute cacheFlush(), or if the CPU immediately accesses the region after the GPU finishes drawing and does not execute cacheInvalidate(), it may result in illegal address offsets or data corruption, triggering an abort

Regards

Re: imx6 vxworks7.0绘图

Hi,

You better enter a support request to VXworks.

Regards

Re: imx6 vxworks7.0绘图We tried to reproduce it, but we couldn't reproduce it. Is there any way to increase the probability of reproduction.