ESPixelStick Questi...
 
Notifications
Clear all

ESPixelStick Question for Martin

15 Posts
4 Users
0 Reactions
682 Views
Posts: 79
Topic starter
(@bobsmith)
Trusted Member
Joined: 11 years ago

maybe that's how I set it to a weird setting in the past, and like you said it's stored in a config file in the filesystem, and it was still there from before until I disabled all the outputs and re-enabled them


Reply
Posts: 79
Topic starter
(@bobsmith)
Trusted Member
Joined: 11 years ago

I wanted to try flashing the ESP32_KA version, as it has 8 outputs already defined, and from what I can tell is just a generic ESP32, but I want to try it out and see if output 3 that's assigned to GPIO_0 which has a pullup resistor and capacitor on it, which seems to be for flashing / resetting during flashing) would work normally.

I tried flashing my board using the ESPS java flash tool with ESP32 KA, but it fails.
Looking at the log, esptool (called by the python script called by the java utility) wasn't happy and complaining about missing arguments.

I dug a little further and noticed in firmware/firmware.json, ESP32 KA had no "options" set for esptool compared to "D1 Mini32". Copying the options line from "D1 Mini32" firmware definition to the "ESP32 KA" firmware definition fixed the issue with the missing arguments to esptool, and now it flashed to my board just fine using the java flasher.

"esptool": {
"baudrate": "460800",
"options": "--before default_reset --after hard_reset", <<== this was just an empty " " on ESP32 KA
"flashcmd": "write_flash -z"
},

I'm not sure what generates that firmware.json file in the build, but that should probably be fixed.

Also what actual board is a ESP32_KA? Googling, I can't seem to find what original hardware that's actually targeting.
It runs just fine on a stock D1 mini32 though, and has all 8 outputs defined, which is nice.
I've only tested Output 4 (which is assigned to GPIO_16) so far and it works fine.

I'll need to solder a couple more wires to some of the other outputs on my test board to verify that they're all working (especially the one on GPIO_0). I really want to make sure this works properly before connecting the pins on my custom PCB - trying to get this to work properly on the first spin of the board 🙂


Reply
Posts: 79
Topic starter
(@bobsmith)
Trusted Member
Joined: 11 years ago

Another question, I see if I configure more than ~3000 pixels on various outputs, I start to see "[OutputMgr] ERROR: Too many output channels have been Requested" errors on the console. Looking through the code, this seems to be related to the available ram size.

Does the firmware make use of the psram on the ESP-32 WROVER modules? Do they allow more output pixels to be configured?


Reply
MartinMueller2003
Posts: 7613
(@martinmueller2003)
Illustrious Member
Joined: 14 years ago

All of the types listed in the platform list represent a custom base card created by a user. People are adding new platforms on there own. Some people ask me to do it.

V4 cannot use PSRAM. It takes to long to flush the data cash and switch to external ram. Doing so caused the WSP to crash with a memory access exception (worst case) or not output data quick enough causing corrupted data to be sent to the pixels.

V4 supports an aggregate of 3000 pixels spread across all ports.


Reply
Posts: 133
(@mel4853)
Estimable Member
Joined: 19 years ago

The ESP32_KA is a custom board I made to use in my show. (It's actually 2 boards to keep the footprints small) I'm not a programmer, Martin got the definitions, etc.... all setup with the information I gave him and helped me over a couple hurdles. I do use 3 sets of these boards in my show and they all ran flawless last year. They use a esp32 d1 mini. I gave up on the ESPS java flash tool, it always failed for me. I use the ESPixelStick Software Web Flasher and have not had problems.


Reply
Page 2 / 3
Share: