Differences

This shows you the differences between two versions of the page.

--- projects:q3kled [2015/12/23 17:01] – q3k
+++ projects:q3kled [2023/11/06 21:12] (current) – informatic
@@ Line 1: / Line 1: @@
+{{template>:template:project
+ | name=chubbyled/colorlight-blaster
+ | status=active
+ | founder=[[user>informatic]]
+ | repo=[[code>informatic/colorlight-blaster]]
+}}
+====== Chubbyled ======
+Reincarnation of q3kled project (archived below). Same 128x128 (4x4x[64x64]) RGB LED panel, but based on Colorlight 5A-75B.
+While said board [[github>q3k/chubby75|has been reverse-engineered]] and can be used as a target for custom FPGA bitstream, no such bitstream has been prepared. However - using [[code>informatic/colorlight-blaster|some disgusting python code]] (involving raw ethernet frames broadcasting) original bitstream can be controlled.
+LED panel is now mounted next to a rollup projection screen in main room. Connect blue ethernet cable marked as "No uplink/No internet/LED Panel" directly to your machine and use [[code>informatic/colorlight-blaster]].
+**DO NOT TRY TO CONNECT IT TO HACKERSPACE LAN ETHERNET NETWORK!** Due to broadcast nature of these ethernet video packets this **will** take down most of wifi devices.
+----
+{{template>:template:project
+ | name=q3kled
+ | status=abandoned
+ | founder=[[user>q3k]]
+ | repo=[[github>q3k/ledvideo]]
+}}
 ====== Chinese 'HUB75' RGB LED Driver ======
 [[people:q3k:start|q3k]]'s project to create a Zynq-based RGB LED Matrix driver.
+[[https://youtu.be/gnT0wj1DyD0|Video of a 128x128 panel it action at 32c3]].
+===== Overview =====
+This project targets the [[projects:zturn-hackers|MYiR ZTurn board]] with a custom buffer interface board (to be released). The programmable logic exposes a 65-kbyte block RAM to Linux running on the PS via a full-speed AXI slave. The logic also loads data from the BRAM, gamma corrects it and outputs it to the RGB panel interface.
 ===== Current Status =====
-It works!
+It works! But really needs to be re-written. Keep poking q3k on IRC until he does so.
+Issues:
+  * <del>Vertical glitches</del> Fixed by switching buffers to 5V
+  * <del>Low framerate</del> Fixed by switching buffers to 5V and increasing pixel clock
+  * Horizontal ghosting
+  * No double buffering in hardware
+  * No vsync / interrupts
+  * No runtime configuration
+  * Kernel framebuffer access from userspace (FBDev/DirectFB) locks up whole system
+  * Gamma correction is poor, needs and actual ICC color profile correction
+  * Hardcoded parameters in kernel/mpv driver
+Note: photo of display was taken before dank memes started becoming appropriated by hate groups.
 {{https://owncloud.hackerspace.pl/index.php/apps/files_sharing/ajax/publicpreview.php?x=1278&y=1358&a=true&file=IMG_20151222_185742.jpg&t=vcbwcUxqmTVcCfh&scalingup=0&.png?600}}
 {{https://owncloud.hackerspace.pl/index.php/apps/files_sharing/ajax/publicpreview.php?x=1278&y=1358&a=true&file=IMG_20151222_212052.jpg&t=naEYL6o4nBA6RJR&scalingup=0&.png?600}}
-After 32c3 dies down, I should go ahead and refactor most of the code and make sure it's tunable (right now the display format is hardcoded, and so are a few software components)...
 ===== Components =====