https://github.com/librerpi/rpi-tools/b ... pp#L24-L55
the DPI hardware block on the rpi, was meant for driving video
you give it an array of 24bit color data
and on each pixel clock, it will present a different pixel from that array on up to 24 gpio pins
after doing $hactive pixels, it will disable the output for $hblank pixels (hfb + hbp + hsync, minimum of 1 total)
and then it will repeat for $vactive scanlines, and then disable for $vblank lines (minimum 1)
nothing stops you from loading non-video data into the framebuffer, and then just sitting back and letting the hardware clock it out 24 gpio pins at once
the link i provided, is an example of doing that t generate 8 uart streams at once
the DPI hardware block on the rpi, was meant for driving video
you give it an array of 24bit color data
and on each pixel clock, it will present a different pixel from that array on up to 24 gpio pins
after doing $hactive pixels, it will disable the output for $hblank pixels (hfb + hbp + hsync, minimum of 1 total)
and then it will repeat for $vactive scanlines, and then disable for $vblank lines (minimum 1)
nothing stops you from loading non-video data into the framebuffer, and then just sitting back and letting the hardware clock it out 24 gpio pins at once
the link i provided, is an example of doing that t generate 8 uart streams at once
Statistics: Posted by cleverca22 — Thu Feb 01, 2024 9:42 am