We use some essential cookies to make our website work.

We use optional cookies, as detailed in our cookie policy, to remember your settings and understand how you use our website.

3 posts • Page 1 of 1
rst
Posts: 606
Joined: Sat Apr 20, 2013 6:42 pm

May DSI display stop working on high bus load on RPi 4?

Mon May 05, 2025 6:20 am

In a bare metal application running on the Raspberry Pi 4 a connected firmware-driven DSI display occasionally stops working and goes black. The application heavily uses the memory bus by parallel DMA transfers and updates the contents of two un-cached frame buffers at a frame rate of at least 30 Fps using multiple CPU cores.

Is is possible that the update process of the DSI display stops, because the bus bandwidth is exhausted? Or if not, are there any data structures in main memory space, which is used by the GPU/VPU, which would trigger such a display update stop, when they would be destroyed due to application failure?

aBUGSworstnightmare
Posts: 13432
Joined: Tue Jun 30, 2015 1:35 pm

Re: May DSI display stop working on high bus load on RPi 4?

Mon May 05, 2025 7:20 am

which driver are you using and which display do we speak of?

rst
Posts: 606
Joined: Sat Apr 20, 2013 6:42 pm

Re: May DSI display stop working on high bus load on RPi 4?

Mon May 05, 2025 10:45 am

aBUGSworstnightmare wrote:
Mon May 05, 2025 7:20 am
which driver are you using and which display do we speak of?
A 7" Official Raspberry Pi Touchscreen (v1), which is fully driven by the firmware. It is setup by a bare metal application using property mailbox calls. After init only the frame buffer memory is written.

3 posts • Page 1 of 1

Return to "Bare metal, Assembly language"

AltStyle によって変換されたページ (->オリジナル) /