In the version 1.x driver your panel settings were all in one file isp_hub75_hwGeometry.spin2. You chose a configuration that specified all compile-time constants. This file was adjacent to the other driver code files and compiled into it.
In the new v2.x and later driver you have the same isp_hub75_hwGeometry.spin2 file but it now has fewer settings in it, which you still have to configure. But there is now a new 2nd file isp_hub75_hwBuffers.spin2 which the other settings moved to. This 2nd file is named hwBuffers because this driver now support multiple HUB75 cards so buffer space (which must be compile-time allocated) has to be set up for each of the HUB75 cards you wish to support. Your work in this file has you selecting constant values once again but you also potentially have to uncomment some of the table entry and buffer allocations as well.
Let's look at making these changes and also the new form of startup the v2.x driver uses (it's much more like starting normal device object now, as you'll see.
The file isp_hub75_hwGeometry.spin2 needs to be adjusted to support your panel hardware.
Example v1.x form:
ADAPTER_BASE_PIN = PINS_P16_P31
' (1) determine what form of signalling the driver should use
PANEL_DRIVER_CHIP = CHIP_FM6126A
' (2) describe the panel electrical layout
MAX_PANEL_COLUMNS = 64
MAX_PANEL_ROWS = 32
PANEL_ADDR_LINES = ADDR_ABCD
' (3) describe the organization of panel(s)
' panels organization: visual layout
' [1][2]
' (4) describe the organization in numbers of panels
MAX_PANELS_PER_ROW = 2
MAX_PANELS_PER_COLUMN = 1
' (5) describe the color depth you want to support [3-8] bits per LED
' NOTE full 24bit color is DEPTH_8BIT
COLOR_DEPTH = DEPTH_8BITExample v2.x form (single HUB75 adapter):
ADAPTER_BASE_PIN = hwEnum.PINs_P16_P31
' (1) determine what form of signalling the driver should use
PANEL_DRIVER_CHIP = hwEnum.CHIP_FM6126A
PANEL_ADDR_LINES = hwEnum.ADDR_ABCD
' The visual organization of panel(s)
' [1][2] ' one row of 2 panelsNOTE in order to reduce compile-time complexity the named constants you select from to assign are all moved into isp_hub75_hwEnums.spin2 The two files you are editing already have this Enums file specified as an object named hwEnum which is why you see these value names prefixed with hwEnum.
The file isp_hub75_hwBuffers.spin2 needs to be adjusted to support each of your HUB75 cards with a chain of 1 or more panels attached to each card.
NOTE: All panels in a chain (all connected to same HUB75 card) must have the SAME hardware driver chips.
Since this file didn't exist in v1.x we are only showing an example for v2.x:
' /-------------------------------------------
' | User configure
' (1) describe the panel electrical layout
DISP0_MAX_PANEL_COLUMNS = 64
DISP0_MAX_PANEL_ROWS = 64
' (2) describe the organization of panel(s)
' panels organization: visual layout
' [1][2] 1 row of 2 panels
'
DISP0_MAX_PANELS_PER_ROW = 2
DISP0_MAX_PANELS_PER_COLUMN = 1
' (3) describe the color depth you want to support [3-8] bits per LED
' NOTE full 24bit color is DEPTH_8BIT
DISP0_COLOR_DEPTH = hwEnum.DEPTH_6BIT
' | End User configure
' \-------------------------------------------NOTE Notice the use of value names prefixed with hwEnum. in this file too.
Example v1.x start up:
OBJ
display : "isp_hub75_display"
PUB ...()
ok := cog := display.start() ' awaken the LED matrix driverExample v2.x start up (single hub75 card):
OBJ
display : "isp_hub75_display"
hub75Bffrs : "isp_hub75_hwBuffers" ' run-time hardware config
user : "isp_hub75_hwGeometry" ' compile-time hardware config
PUB ...()
hub75Bffrs.configure(hub75Bffrs.HUB75_ADAPTER_1, user.ADAPTER_BASE_PIN, user.PANEL_DRIVER_CHIP, user.PANEL_ADDR_LINES)
chainIndex := hub75Bffrs.indexForHub75ChainId(hub75Bffrs.HUB75_ADAPTER_1)
' startup our backend COG(s)
ok := cog := display.start(chainIndex) ' send buffer to driverExample v2.x start up (two hub75 cards):
In isp_hub75_hwGeometry.spin2::
' Constants for Panels connection to 1st HUB75 card (nickname FRONT_)
FRONT_ADAPTER_BASE_PIN = hwEnum.PINs_P16_P31
' (1) determine what form of signalling the driver should use
FRONT_PANEL_DRIVER_CHIP = hwEnum.CHIP_FM6126A
FRONT_PANEL_ADDR_LINES = hwEnum.ADDR_ABCD
' The visual organization of panel(s)
' [1][2] ' one row of 2 panels (our cube is electrically 1 row)
' Constants for Panels connection to 2nd HUB75 card (nickname BACK_) BACK_ADAPTER_BASE_PIN = hwEnum.PINs_P0_P15
' (1) determine what form of signalling the driver should use
BACK_PANEL_DRIVER_CHIP = hwEnum.CHIP_ICN2037_B
BACK_PANEL_ADDR_LINES = hwEnum.ADDR_ABCDE
' The visual organization of panel(s)
' [1][1] ' one row of 1 panel (our cube is electrically 1 row)In top-level-file:
OBJ
display[2] : "isp_hub75_display"
hub75Bffrs : "isp_hub75_hwBuffers" ' run-time hardware config
user : "isp_hub75_hwGeometry" ' compile-time hardware config
CON
' which chain is connected to which pin-group
HUB75_FRONT_PANEL = hub75Bffrs.HUB75_ADAPTER_1
HUB75_BACK_PANEL = hub75Bffrs.HUB75_ADAPTER_2
' which display instance do we want to call FRONT and BACK
FRONT_PANEL = 0
BACK_PANEL = 1
PUB ...() | frontPanelIdx, backPanelIdx
hub75Bffrs.configure(HUB75_FRONT_PANEL, user.FRONT_ADAPTER_BASE_PIN, user.FRONT_PANEL_DRIVER_CHIP, user.FRONT_PANEL_ADDR_LINES)
hub75Bffrs.configure(HUB75_BACK_PANEL, user.BACK_ADAPTER_BASE_PIN, user.BACK_PANEL_DRIVER_CHIP, user.BACK_PANEL_ADDR_LINES)
frontPanelIdx := hub75Bffrs.indexForHub75ChainId(HUB75_FRONT_PANEL)
backPanelIdx := hub75Bffrs.indexForHub75ChainId(HUB75_BACK_PANEL)
' startup our backend COG(s)
ok := cog := display.start(0, frontPanelIdx) ' send buffer to driver
ok := cog := display.start(1, backPanelIdx) ' send buffer to driver
' NOTE with multiple hub75 cards all your display.method() calls must
' now be display[FRONT_PANEL].method() or display[BACK_PANEL].method() calls.Now that your driver is configured and you've started the driver (or drivers) the rest of the single HUB75 card display code is pretty much the same. Your existing code shouldn't change.
Of course, if when you decide to activate two or three HUB75 cards then you'll be selecting from 2-3 display object instances as shown in the "two hub75 cards" example above.
That's it. If you've followed along and updated the two files with specifics that describe your panels and you've adjusted your top-level file to start the driver in the new way then you are good to go!
I hope you continue to enjoy using this driver. As always please feel free to report issues or discuss how you are using the driver in our Matrix driver thread P2 Driver for HUB75 LED Matrix Panels. You can also file BUG reports or feature requests at the driver repository Issues Page.
See you in the Parallax Forums and on our P2 Live Forums!
-Stephen
If you find this kind of written explanation useful, helpful I would be honored by your helping me out for a couple of ☕'s or 🍕 slices -or- you can support my efforts by contributing at my Patreon site!
Licensed under the MIT License.
Follow these links for more information: