-
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2 from ironsheep/newColorDepth
Release New color depth Support
- Loading branch information
Showing
33 changed files
with
771 additions
and
306 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,6 +4,9 @@ | |
| # macOS files | ||
| .DS_Store | ||
|
|
||
| # vscode files | ||
| .history | ||
|
|
||
| # my scripts | ||
| checkDropbox | ||
|
|
||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
8 changes: 8 additions & 0 deletions
8
Docs/Altronics-AU/Z6517 LED Dot Matrix RGB 32 X 32 - Altronics.webloc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| <?xml version="1.0" encoding="UTF-8"?> | ||
| <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> | ||
| <plist version="1.0"> | ||
| <dict> | ||
| <key>URL</key> | ||
| <string>https://www.altronics.com.au/p/z6517-led-dot-matrix-rgb-32-x-32/</string> | ||
| </dict> | ||
| </plist> |
Binary file not shown.
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,194 @@ | ||
| # HUB75 Driver - configuring for a chip we haven't seen yet | ||
|
|
||
| ![Project Maintenance][maintenance-shield] | ||
|
|
||
| NOTE: this is NEW information as of v1.x! An older version is here: [Sofware Ver0.x Timings](HUB75-Driver-SWver0.md) | ||
|
|
||
| ## Intent | ||
|
|
||
| The P2 HUB75 backend-end driver has configuration values we place in the file: **isp_hub75_hwGeometry.spin2**. This page presents more detail of what's happening behind the scenes for some of these configurable values. | ||
|
|
||
| ## Driver Adjustable Settings for given Panel | ||
|
|
||
| The driver currently offers the following adjustments: | ||
|
|
||
| | Purpose | Value Choices | Description | ||
| |-----------------|-------------|-----| | ||
| | LATCH_STYLE | OFFSET, ENCLOSED | Adjust the waveform of Latch & OE! | | ||
| | LATCH_POSITION | OVERLAPPED with the Last Bits of the row AFTER the last bits of the row | When should the latch occur relative to the bits for each row? | | ||
| | INIT_PANEL | True, [False] | The Driver chips on this panel require/support a configuration stream prior to normal operation (e.g., FM6126A, FM6126Q, FM6127, and MBI5124) | ||
| | WIDER_CLOCK | True, [False] | Inject a wait during the high portion of the data clock (ICN2037 Has 20MHz limit) | ||
| | RED\_BLUE_SWAP | True, [False] | It seems that our 64x64 panel requires the red and blue lines to be swapped | ||
| | SCAN\_4 | True, [False] | By default [False] the driver sends half the panel pixels over the each of the two sets of RGB lines (RGB1,RGB2), A 1/8th scan panel however [True] sends two diff regions of 1/4 of the panel which is a different pixel ordering. | ||
| | ADAPTER\_BASE_PIN | 0-15, 16-31, 32-47, 48-63 [*no default*] | compile driver to use specific header pair to which the HUB75 Adapater card is attached | ||
|
|
||
| ### PURPOSE: LATCH_STYLE | ||
|
|
||
| The driver has two built-in LATCH, OE! styles supporting the hardware we've seen to date. | ||
|
|
||
|  | ||
|
|
||
| **FIGURE 1: LATCH_STYLE: OFFSET (left), ENCLOSED (right)** | ||
|
|
||
| #### LEGEND | ||
|
|
||
| | Signal | Color | | ||
| |-----|-----| | ||
| | LATCH | Green | | ||
| | OE! | White | | ||
| | ADDR | Yellow | | ||
|
|
||
|
|
||
| In the OFFSET case: we see OE! going high, we see the row address changing and then we see LATCH going high which latches the serial data into the chip. Then we see the OE! going low, followed by the LATCH going low. However, in the ENCLOSED case the LATCH signal goes low before the OE! goes low. | ||
|
|
||
| ### PURPOSE: LATCH_POSITION | ||
|
|
||
| The driver supoorts two forms of latch position: | ||
|
|
||
|  | ||
|
|
||
| **FIGURE 1: LATCH_POSITION: OVERLAPPED (left), AFTER (right)** | ||
|
|
||
| #### LEGEND | ||
|
|
||
| | Signal | Color | | ||
| |-----|-----| | ||
| | CLK | Red | | ||
| | LATCH | Green | | ||
| | OE! | White | | ||
| | ADDR | Yellow | | ||
|
|
||
|
|
||
| In the OVERLAPPED case: we see LATCH going high before the start of the three last serial bits of the row and ending after the last serial data bit. However, in the AFTER case we see the LATCH signal going high after the final serial bit of the row is sent. | ||
|
|
||
| ## Driver configuration by chip type - S/W Ver 1.x Timings | ||
|
|
||
| In this section we are recording the configuration we've shown that works for each of the following driver chips we've seen used in the panels. As you identify more, please file an issue telling us the settings you found that work with your panels' driver chip. And we'll add the new details to this document for us all to see. | ||
|
|
||
| ### Driver Chip: FM6126A | ||
|
|
||
| This is the most complicated of the driver chips to date. These chips don't turn on reliably until they've been configured which is a process nearly the same as writing a single row of data but with special meaning to the bit stream and special latch timing. This Chip supports faster data CLK (Max 30MHz) | ||
|
|
||
| - LATCH_STYLE: OFFSET | ||
| - LATCH_POSITION: OVERLAPPED | ||
| - CONFIGURE_PANEL: True | ||
| - WIDER_CLOCK: False | ||
| - RED\_BLUE_SWAP: False | ||
| - SCAN_4: False | ||
|
|
||
| Signal Timings - 64x32 panel - for driver v1.x: | ||
|
|
||
|  | ||
|
|
||
| **NOTE** *the orange indicates a frame-rate less than 60Hz so you may see some flicker.* | ||
|
|
||
| --- | ||
|
|
||
| ### Driver Chip: FM6124 (UNKNOWN) | ||
|
|
||
| This is the most simple chip form. This chip also supports faster data CLK (Max 30MHz) although the driver doesn't, yet. | ||
|
|
||
| - LATCH_STYLE: ENCLOSED | ||
| - LATCH_POSITION: AFTER | ||
| - CONFIGURE_PANEL: False | ||
| - WIDER_CLOCK: False | ||
| - RED\_BLUE_SWAP: False | ||
| - SCAN_4: False | ||
|
|
||
| Signal Timings - 64x32 panel - for driver v1.x: | ||
|
|
||
|  | ||
|
|
||
| **NOTE** *the green indicates a frame-rate greater than 60Hz for all color depths* | ||
|
|
||
| --- | ||
|
|
||
| ### Driver Chip: ICN2037 (UNKNOWN) | ||
|
|
||
| This is nearly the same as the FM6124 but needs a slower data CLK (Max 20MHz) (wider pulse width) and our 64x64 panels appear to need Red/Blue swapped!?. | ||
|
|
||
| - LATCH_STYLE: ENCLOSED | ||
| - LATCH_POSITION: AFTER | ||
| - CONFIGURE_PANEL: False | ||
| - WIDER_CLOCK: True | ||
| - RED\_BLUE_SWAP: True | ||
| - SCAN_4: False | ||
|
|
||
| Signal Timings - 64x64 panel - for driver v1.x: | ||
|
|
||
|
|
||
|  | ||
|
|
||
| **NOTE** *the orange indicates a frame-rate less than 60Hz so you may see some flicker.* | ||
|
|
||
| --- | ||
|
|
||
| ### Driver Chip: MBI5124_8S (MBI5124 but panel is 1/8 scan) | ||
|
|
||
| This is nearly the same as the FM6124 but but halves the number of address lines which is normally panel rows / 2, but in this case is panel rows / 4. It also clocks out 2x the number of pixels per row. | ||
|
|
||
| *NOTE: The MBI5124 does support configuration but it appears that it is already configured at power-up so this driver does not attempt to configure the panel currently. The setting CONFIGURE_PANEL is marked as true so if we add configuration later the driver will use it.* | ||
|
|
||
| - LATCH_STYLE: ENCLOSED | ||
| - LATCH_POSITION: AFTER | ||
| - CONFIGURE_PANEL: True | ||
| - WIDER_CLOCK: False | ||
| - RED\_BLUE_SWAP: False | ||
| - SCAN_4: True | ||
|
|
||
| Signal Timings - 64x32 panel - for driver v1.x: | ||
|
|
||
|  | ||
|
|
||
| **NOTE** *the green indicates a frame-rate greater than 60Hz for all color depths* | ||
|
|
||
| ---- | ||
|
|
||
| ### Driver Chip: ICN2037 (UNKNOWN) for P2 P2 Cube | ||
|
|
||
| This is nearly the same as the FM6124 but needs a slower data CLK (Max 20MHz) (wider pulse width) and our 64x64 panels need Red/Blue swapped. | ||
| **NOTE** However, I'm successfully clocking the panels at 28.6 MHz (which is faster than the panel 20 MHz max.) while clocking the P2 at 335 MHz. | ||
|
|
||
|
|
||
|
|
||
| - LATCH_STYLE: ENCLOSED | ||
| - LATCH_POSITION: AFTER | ||
| - CONFIGURE_PANEL: False | ||
| - WIDER_CLOCK: True | ||
| - RED\_BLUE_SWAP: True | ||
| - SCAN_4: False | ||
|
|
||
| Signal Timings - 64x32 panel x 6! - for driver v1.x. | ||
|
|
||
|  | ||
|
|
||
| **NOTE** *the ORANGE indicates a frame-rate less than 60Hz so you may see some flicker while the RED indicates the flicker is really drammatic!* | ||
|
|
||
| A single PWM Frame consists of writing 32 - 384 pixel lines (which paint to the top 32 and bottom 32 rows at the same time.) | ||
|
|
||
| When this driver is configured for the P2 P2 Cube (1 chain of 6 64x64 pixel panels) the driver copies two lines of PWM data from Hub RAM to COG RAM, clocks out the two rows then fetches the next 2 rows. Within the driver code these two-row groups are called subFrames. For the 6x64x64 panel-set there are 16 of these subFrames for each PWM Frame. There are N PWM Frames creating what we know as a single video frame. Where the N is is 2^{color-depth} number of frames and {color-depth} set by your COLOR_DEPTH compile time value. | ||
|
|
||
| ---- | ||
|
|
||
| > If you find this kind of written explanation useful, helpful I would be honored by your helping me out for a couple of :coffee:'s or :pizza: slices -or- you can support my efforts by contributing at my Patreon site! | ||
| > | ||
| > [](https://www.buymeacoffee.com/ironsheep) -OR- [](https://www.patreon.com/IronSheep?fan_landing=true)[Patreon.com/IronSheep](https://www.patreon.com/IronSheep?fan_landing=true) | ||
| ---- | ||
|
|
||
| ## License | ||
|
|
||
| Copyright © 2020 Iron Sheep Productions, LLC. All rights reserved.<br /> | ||
| Licensed under the MIT License. <br> | ||
| <br> | ||
| Follow these links for more information: | ||
|
|
||
| ### [Copyright](copyright) | [License](LICENSE) | ||
|
|
||
| [maintenance-shield]: https://img.shields.io/badge/maintainer-stephen%40ironsheep.biz-blue.svg?style=for-the-badge | ||
|
|
||
| [license-shield]: https://camo.githubusercontent.com/bc04f96d911ea5f6e3b00e44fc0731ea74c8e1e9/68747470733a2f2f696d672e736869656c64732e696f2f6769746875622f6c6963656e73652f69616e74726963682f746578742d646976696465722d726f772e7376673f7374796c653d666f722d7468652d6261646765 | ||
|
|
||
| [releases-shield]: https://img.shields.io/github/release/ironsheep/p2-LED-Matrix-Driver.svg?style=for-the-badge | ||
|
|
||
| [releases]: https://github.com/ironsheep/p2-LED-Matrix-Driver/releases |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.