This is mostly a question for Martin
I'm doing a PCB layout for my PixelSplitter and want to include support so I can drive the splitter with an ESPixelStick with V4 firmware on it.
I have a very recent release from your github running on a Wemos D1 Mini 32, using the d1 mini firmware that's compiled by CI/CD. I previously had some much older version of V4 beta firmware from the original Forkineye tree running on it, that was also the d1 mini 32 image, but didn't change anything with the hardware between that and flashing this more current version from your fork.
I'm very confused about the output channel mapping and pin definitions. Looking through the platform files in the repo, it looks like the pin definitions for the d1 mini 32 are in this file:
It looks to me like Output 1 should be coming out GPIO_2, Output 2 should be coming out GPIO_4, Output 3 should be coming out GPIO_12, Output 4 should be coming out GPIO_14, Output 5 should be coming out GPIO_16, and output 6 and 7 should only support SPI and I2C. And the various pins are configured for the SD Card, and indeed my sdcard works - I can put files on it through the web interface / ftp.
In the web interface, output 6 and 7 do indeed only show support for only a few supported types on SPI and I2C which all makes sense, and I only have Output 1 configured for WS2811, but it's coming out GPIO_16??? I seem to recall having an issue with this when I very first flashed the V4 firmware, but don't remember the details now as that was more than a year ago.
Why is Output 1 in the web interface coming out the output pin defined as OM_PortId_t(4) in the config?
What I actually want is 8 channels of WS2811 output, and no channels of I2C or SPI, and I see there's a config that matches that already in GPIO_Defs_ESP32_KA.hpp that also has the same sd card pin mappings (but it also has the DS18B20 temperature sensor defined, which I don't have). Because I'm doing my own board layout, I can use any IO pins I want from the d1 mini, but I need to actually understand the mapping to make sure I connect the right things together!
How many pixels per port can the ESPS V4 firmware handle when there are 8 output ports enabled? Is it the full ~800 pixels per port even if all 8 ports are enabled?
Hmm, I disabled all of the outputs in the web ui, and then re-enabled them, and now the mapping seems to be correct - I get pixel data on GPIO_16 only when I have Output 5 enabled in the web ui. I've actually never had output 5 enabled before, and was getting pixel data out GPIO_16 for a long time now (like over a year of it being used intermittently on my desk for testing only)
I wonder if there was some old config data left from the old firmware version that didn't get cleared out until I disabled all the outputs and then re-enabled them.
It does seem to be doing exactly what I would expect now.
Did you have a different version of V4 on this device?
Did you flash the device using the web flash tool or did you flash it using vs code / platformio?
If vs code, did you also build and upload the FS image?
As an experiment, do a factory reset on the ESP. The only time I have seen this issue is when I initialized the FileSystem (FS) on one version and then switched to a different version and forgot to reset the FS. The GPIOs in the file are the default values. They get stored into a config file if the config file is missing. Doing a reset to factory defaults removes the config file and sets the new default values.
Yes, it was some previous version of V4, but I don't know exactly what version it was.
Originally I used the java flash tool to build a .efu and flashed it through the web interface, but that didn't seem to update the version number showing in Admin (or maybe I wasn't patient enough), so instead I flashed it over USB using the java flash tool, with both the firmware and the flash tool coming from the CI/CD artifact I got from your github off whatever was the most recent checked in code a few days ago.
Was there a way in the webUI to change the IO pin mapping of the outputs before? When I enable "Advanced mode" under admin, I can set the IO pins of the SD card, but it doesn't look like I can set the IO pins of the outputs. Was that an option previously?
That was previously an option. It stopped working when I refactored the html files to make the transfer to the browser faster. I have yet to figure out a way to correct that. Been working on ESP32 S3 support.



