What configuration for RUC7258 chip?

[Kalrkloss]

The RUC7258 is in the list of supported chips, but nowhere in the sourcecode.
What driver option do I actually have to choose for a RUC7258 based 1/16 panel (64x32)?

[board707]

The ruc7258 is not a driver, it is just a multiplexor. To make conclusion, is your panel compatible with the library or not, we need to know the type of the another chip on the panel.

Addition: 7258 multiplexor doesn't require any special configuration

[Kalrkloss]

The thing is, I can almost drive this panel with a Color light 5a-75b board and Ledvision.
"Almost" meaning that only the upper half of the display works and is somewhat garbled.

[daveythacher]

I looked into this and it works for the most part. However the Ethernet packets are supposed to be very consistent in timing. The display glitches when this is not true. I found that using a PIC32MZ with a dedicated 1G switch fixed the issue.

What I did was carefully write firmware in the PIC32MZ to move data from USB HS (single bulk endpoint) to 100Mb Ethernet. The switch then proxies this to 1Gb Ethernet for the receiver card. I was able to get the transfers very consistent with this. The cost is somewhat high and my USB logic was a total hack. (I eventually stopped work on it due to legal concerns.)

Raspberry Pi was capable of driving a decent amount of pixels directly for non GCLK (hardware PWM) panels. This is Pi first gen, but second gen was significantly faster.

[daveythacher]

Which 5A-7B firmware did you use? (PWM or the standard one)

[Kalrkloss]

I didn't even know that there are different ones. I used the one it came with.

[daveythacher]

If that worked then you are not likely using a hardware PWM panel. (That means support would be easier to add to this project. Assuming it can be done legally.)

You may need to adjust your settings. You need to define both the cabinet and the panel size. It assumes all panels are the same within the cabinet. The eight connectors are stacked by row. (You may be able to change it, but I just did this in software on PC/Pi application.) You need to know the scan, columns and pixel locations. There is a walk thru which helps you out. The netcard function is a setup tool which can be abused. I forget if it gives you snow or just repeats the image. There is a number of knobs and switches, but most are for random cases. (From my tinkering at least, my guess is they help with compatibility electrically.)

Note for high refresh you need to use something with PWM rather than BCM. I do not recall which ones they use, but I believe it is BCM. PWM uses more memory and computational power. I think they use a 32 or 64 bit SDRAM/DDR interface. They can do PWM but they would have to scale it down. For the most part standard firmware likely is limited on refresh, however an alternative which reduces color depth may be able to fix this.

[daveythacher]

It is supported by the code base. It is an optimized high side driver. (It handles the rows.) It likely has some kind of push/pull driver for managing upper ghosting, which is pretty much required for high refresh rates. This is passive to the code base. (Any optimizations that this brings passively are not fully used by this code base.) This code base does not support super high refreshes like most BCM code bases.

Just enjoy the improved performance.

[board707]

@daveythacher
Is this an output from Chatgpt?
A lot of empty phrases that have nothing to do with the topic.

[daveythacher]

I actually did play with hardware. (Connect the dots.) I actually did a little more than play...

[board707]

I hope we see something concrete other than words