Hub75 interface indoor dot matrix screen development board based on ESP32 module

At present, a large number of LED dot matrix screens use the Hub75 interface as shown in the figure below. If you want to drive it, you need to occupy 13 IO pins. Some LED screens with a larger dot matrix need to use 14 pins, that is, the GND of the fourth pin in the right row is changed to signal channel E, as shown in Figure 2. When doing various experiments related to LED dot matrix screens, if you use Dupont wires to connect these pins, it will probably make you dazzled. If you connect them incorrectly or not securely, it will cause even more headaches.

Therefore, I have previously made a small adapter board for Espressif's official ESP32 development board, see the ESP32 Hub75 Adapter project. But it still feels inconvenient. Firstly, the volume of the ESP32 development board will become very large after being plugged into the adapter board. Secondly, the whole thing is not beautiful. So I simply re-referenced the schematic diagram of Espressif's official ESP32 DevKitC V4 development board and tried to make this ESP32 Hub75 DevKit development board that integrates the Jane Niu socket pads and TF card slot for Hub75/Hub75E.

Features

This development board has the following features:

• The device refers to the official ESP32 DevKitC V4 as much as possible to ensure its compatibility.
• Integrated standard 2.54 2*8 pads, used for Hub75 interface simple cow socket or straight female socket (so that different installation methods can be used according to actual needs).
• Integrated TF card slot.
• Use a jumper to switch whether to support Hub75E. If your dot matrix screen has a 16-brush Hub75 interface, you can save the IO12 interface for other purposes.
• Comes with 4 M3 positioning holes for easy fixing needs.
• Compared with the previous ESP32 Hub75 Adapter, the power binding post has been removed to avoid misconnection and interference.
• Compatible with ESP32's DMA-based dot matrix screen driver library , it has high refresh efficiency and supports multi-screen linking to form a large screen ( see example ).

For more introduction and sample code, please refer to my library on Github .

See attachment for demonstration video.