-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panic when driving larger matrixes (one long strip) on 32MB 8MB ESP32-S3-DevKitC1 #580
Comments
@GameTec-live The hastebin link at the end of your description leads to an empty page with a blinking cursor in my browser. |
oh, weird... ill reupload later... (when I'm home) |
crashlog.log |
Please build debug, as instructed, and be sure you're running the trace
decode filter. I think most o the flags are already present because I get
them by default.
https://docs.platformio.org/en/latest/core/userguide/device/cmd_monitor.html#filters
platformio/platform-espressif32#105 (comment)
I suspect you're just building opt and not debug.
…On Thu, Jan 4, 2024 at 1:39 PM GameTec-live ***@***.***> wrote:
crashlog.log
<https://github.com/PlummersSoftwareLLC/NightDriverStrip/files/13834734/crashlog.log>
Sorry for the late reply, but here you go...
—
Reply to this email directly, view it on GitHub
<#580 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD36TAZ5QBUHW5EBIVTTYM4APBAVCNFSM6AAAAABBFMSILWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZXGY3DAMJRGI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
changed heres the new log: |
That's indicating a problem in a library we use, somewher around:
https://github.com/FastLED/FastLED/blob/09c5fb8f74c43191974c09e1f31edda8281eab7e/src/platforms/esp/32/clockless_rmt_esp32.cpp#L503
You're going to have to get a debugger (or other stone-banging techniques)
in there to see if mCur is walking past the end of mPixelData[]
(questioning mSize corruption?) or some other zany behaviour.
I don't recognize it and don't see smoking guns on this topic in the
fastled buganizer.
https://github.com/FastLED/FastLED/issues?q=+ESP32RMTController%3A%3AfillNext+
…On Thu, Jan 4, 2024 at 5:00 PM GameTec-live ***@***.***> wrote:
changed build_type under base from release to debug and set monitor_filters
= esp32_exception_decoder under [env:demo]
heres the new
debug-log.log
<https://github.com/PlummersSoftwareLLC/NightDriverStrip/files/13836222/debug-log.log>
log:
—
Reply to this email directly, view it on GitHub
<#580 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD3YYAWV3WFOXS2FPSF3YM4YAPAVCNFSM6AAAAABBFMSILWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZXHA3TQMRXGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
probably the stupidiest thing youve heard in a while, but.... i do have a pico debug probe (SWD) and cant figure out where im supposed to hook it up... |
Dude, you can't imagine the stupid stuff I hear. That's not even on the
list. :-)
There is an embarrassment of debugging options on S3. Picking one may
actually be the hardest part. Espressif has this locked down. Even if you
don't follow all the steps, reading this chapter is worthwhile:
https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-guides/jtag-debugging/#
You could hook up wires for TDO, TDI, TMS, and TCK like a caveman and be
proud of your pico purchase. If you work with lots of micros and have a
good workflow around that, go for it.
https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-guides/jtag-debugging/configure-other-jtag.html
If you don't,
*don't do that.*
"The quickest and most convenient way to start with JTAG debugging is
through a USB cable connected to the D+/D- USB pins of ESP32-S3. No need
for an external JTAG adapter and extra wiring/cable to connect JTAG to
ESP32-S3."
So configure it for the built-in JTAG interface. This may require some
driver fiddling depending on yoru OS. The one downfall of this approach
over a "real" JTAG pod, IMO, is that it resets the connection when the
ESP32 resets, such as when you load new code. This has been fixed in newer
ESP parts like the H2 and C6.
Now here's where I'll get hand-wavy because you surely don't want to do it
the way I do it. (See also: working with dozens of micros.)
I try to use as little of platformio and visual studio as I can because I
want to use the SAME debuggers on as many of those micros as I can. I
understand, however, that Platformio has some pointy-clicky stuff that
automates some of the above like building the openocd config. (So why did I
tell you to read that? Because IMO, a developer should know these things
about our tools.)
This is very Windows-centric, but it gives you the needed debug_FOO and
build_type stuff and a nickel tour of GDB.
https://community.platformio.org/t/how-to-use-jtag-built-in-debugger-of-the-esp32-s3-in-platformio/36042/3
This talks about the platformio doc being wrong/misleading.
https://community.platformio.org/t/esp32-s3-jtag-debugging-over-usb/28182
Looks like the official doc is fixed:
https://docs.platformio.org/en/latest/boards/espressif32/esp32-s3-devkitc-1.html#debugging
The concepts you have to embrace are that OpenOCD is the middle-man. It
uses libusb (or Windows driver stuff) to actually open the debug interface
on the board. It creates a couple of network sockets. IIRC, port 3333 is
the one that GDB does the 'target extended remote:localhost:3333" to
connect to (look all this up...I may be typing crazy talk, but I have the
big picture right) and there's an additional port that you can telnet to
that is, I think, 4444. This lets you talk to the board directly, but you
can also confuse GDB if you, say, change a memory location that happens to
hold a variable and you change it without GDB knowing about it. Be careful.
Once you "get it", I think you really will find that the hardest part is
wading through the redundant documentation of expanations fo
rmanually setting up openocd (for both the SoC and the board) which may be
different for CLI use and Platformio use and the differences in the 'real'
jtag interface and the chip-resident jtag interface and all that. This is
why it's worth reading the whole thing - jumping around and copy-pasting
bits will surely get you in trouble.
There are a lot of moving parts, but the ability to single step, display
variables and stack traces, and set breakpoints is worth its weight in gold
and worth the finicky setup.
Good night, good luck and...
May the source be with you.
RJL
…On Fri, Jan 5, 2024 at 2:20 AM GameTec-live ***@***.***> wrote:
probably the stupidiest thing youve heard in a while, but.... i do have a
pico debug probe (SWD) and cant figure out where im supposed to hook it
up...
—
Reply to this email directly, view it on GitHub
<#580 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD35GVN36RNONZI6BR4LYM6ZWRAVCNFSM6AAAAABBFMSILWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZYGI4TCMZZG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Okay, thanks for the help, i managed to get a debugger running (it was a driver issue...)... I don't know what the value of mCur is supposed to be, etc... I'll poke around a bit more and report back... |
cant really see anything unusal? (i mean; i also dont know what those values are supposed to be lol) |
@GameTec-live Glad to see you got the debugger working, and I appreciate the earlier upload of the debug log. As @robertlipe already indicated, it does show that the actual problem (which is a form of illegal memory access) takes place several levels below "our" code. In fact, the backtrace doesn't even include references to any code that's part of NightDriverStrip. Concerning your last comment, we're obviously not looking over your shoulder, so we can't see what you are looking at. Also, even if we could then figuring out what the cause of the invalid behavior is would effectively require us to debug the dependency libraries involved. Which isn't entirely impossible, but very difficult if we can't ourselves debug trace through the code just before the problem occurs. Without having the hardware and software setup that triggers these crashes available, I therefore think we won't be able to solve this. You could (still) consider raising a bug report in the dependent libraries (Espressif ESP-IDF and/or FastLED) and see if they are able to provide pointers to what's actually behind this. I'll leave this issue open in case someone else runs into the same problem, and may be able to provide additional information that can help get to the root of this. |
Yeah, kinda hard to replicate a issue without hardware... Ill open a issue over at FastLED... Thanks for the help though... |
hey GameTec-live 20240108_191857.mp4 |
thx for the info, ig ill try that... My matrix is just one long strip though... |
altough using the spectrum-elecrow project seems to work, it doesnt help me much as spectrum drives hub whatever its called matrixes and i just have one long strip snaking back and forth... |
All of the spectrum builds use a series of strips that zig-zag back and forth as you describe. They can be identified as there is only 1 pin used for output led_pino. The hub75 is currently only used for the Mesmerizer builds that require around 14 output pins depending on what you are doing. Dave does a great job of describing all of this here: https://www.youtube.com/watch?v=COJnlehBcKw&t=224s The video I posted is using a standard zig-zag strip as you describe at 16 pixels high by 48 pixels wide on spectrum build, using the chip you specified. |
ah, ok... so ig I will fumble a bit more with spectrum elecrow and try to use that... thanks... |
nvm, setting the matrix to the required size crashes elecrow too... |
Perhaps if you could articulate exactly what you are trying to accomplish, we might be able to help. As far as I am seeing, this chip is working without any crashes for the spectrum build. While there aren't a lot of spectrum effects here, intend to test it more thoroughly. |
drive my 50x30 matrix (being one long strip) with the new, more powerful ESP32-S3... It works fine with my current, not as powerful ESP32 (afaik its even singlecore?), had to disable nice to haves like the webserver though for it to run a stream from the computer at a decent framerate which im hoping to fix with this a lot more powerful variant... |
Stupid question, but can some of the devs or someone more competent than me try and compile demo with a 50x30 matrix? |
C3 is DOA for us. Not because it's RISC-V but because it's single core. S2
is LX7 like S3, but it's single core, so that's similarly dead to us.
I think there are configurations that probably could be made to work with
some engineering investment (like cleaning up the multiple threads that are
spin looping) but right now, unless you're willing to drive that effort, we
require the two core models. So no c2, c3,. C6, , h6, or such. P4 is a
contender, but they're not sampling yet and honestly, even when they do, I
expect work in esp-idf and probably all that Arduino code that was dragged
off an 8-bit CPU is going to burst into flames when faced with a 64-bit
system. My anxiousness to tackle that may be proportional to the dev board
price when they're announced.
You want to stay in the LX6 dual core parts like esp32 nothing (Those with
no suffix) but that appears in a ton of packages and modules or the dual
core LX6 like ESP32-S3 in about any id it's forms, but I'd lean to the
n8r16 though the n2r2 and other combinations of flash and ram are fine.
Actually,. You just inspired my local copy to make dual cores a hard
requirement at runtime and probably at compile time.
…On Sun, Feb 11, 2024, 11:52 PM GameTec-live ***@***.***> wrote:
Stupid question, but can some of the devs or someone more competent than
me try and compile demo with a 50x30 matrix?
I tried to compile elecrow, 50x30, similar error. Tried to compile demo
for a seeed studio esp32 c3 (ik, not officially supported) and it's still
the same error (from what it looks like)
Havnt tried a nodemcu (clone) yet as thats currently driving the matrix
and id rather not break it until my replacement mcu works... :/
—
Reply to this email directly, view it on GitHub
<#580 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD35CLTAYKBL3S6RFOILYTGU3NAVCNFSM6AAAAABBFMSILWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZYGA4TQMBVGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Ok, that makes sense then, was just the one I had laying around... Id still be interested if someone else can replicate this issue or if its just me or maybe even a defect MCU... And having a reproducable thing / minimum reproducable example might help speed things up here (or over at fastLED) |
Hello [GameTec-live], have looked at your situation a good bit over the last couple of weeks, and do get similar results. While I can approach your matrix size, cannot quite get there. Have a similar problem when trying to use this chip with 4 channel strip effects. Have tried different board define files as well as different memory tables, but still have not solved this problem. While an alternate led program makes both of our build problems work, I would like to get it working here. What I have learned is programs can make use of 16 mb, and the 32mb that these chips support is only useful for storage. Have tried both of our builds with unexpected maker s3 pro, wemos s3, and generic and official builds of esp32-s3 in various memories. Have a wemos d32 pro, and m5stack I'll try our build on next. M5 stack used to work on my build, but suspect that no longer works. Will let you know what I find. |
Ah, so it isn't just me XD |
@robertlipe while ordering other stuff, i threw in a N16R8, so the 16MB version you apperently use... I still get the same panic... |
Seems we're getting no traction with FastLED looking into this.
I'm about to be on the road through the end of the month, so I can't commit
to looking into this in the short term, though I know this has been
simmering a long time. Looks like I may have to debug FastLED. 😐
Is there a repro case for this here? Does it take a while to bonk or is it
close to immediate?
…On Wed, May 15, 2024, 2:20 PM GameTec-live ***@***.***> wrote:
@robertlipe <https://github.com/robertlipe> while ordering other stuff, i
threw in a N16R8, so the 16MB version you apperently use... I still get the
same panic...
—
Reply to this email directly, view it on GitHub
<#580 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD33WTSEGOIIFGP4PVHLZCOYRFAVCNFSM6AAAAABBFMSILWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJTGI4TQMBWGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
The S3 LEDSTRIP project with the onboard LED will fault out reliably. Only problem is the S3 reboots without showing a call stack or exception chain!
- Dave
… On May 15, 2024, at 12:43 PM, Robert Lipe ***@***.***> wrote:
Seems we're getting no traction with FastLED looking into this.
I'm about to be on the road through the end of the month, so I can't commit
to looking into this in the short term, though I know this has been
simmering a long time. Looks like I may have to debug FastLED. 😐
Is there a repro case for this here? Does it take a while to bonk or is it
close to immediate?
On Wed, May 15, 2024, 2:20 PM GameTec-live ***@***.***> wrote:
> @robertlipe <https://github.com/robertlipe> while ordering other stuff, i
> threw in a N16R8, so the 16MB version you apperently use... I still get the
> same panic...
>
> —
> Reply to this email directly, view it on GitHub
> <#580 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ACCSD33WTSEGOIIFGP4PVHLZCOYRFAVCNFSM6AAAAABBFMSILWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJTGI4TQMBWGY>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub <#580 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4HCF4KWJ3YWMMBXNBPUQLZCO3FRAVCNFSM6AAAAABBFMSILWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJTGMZTCMZYGQ>.
You are receiving this because you are subscribed to this thread.
|
While you have that can open, Zack, please add another W to that request.
Another project just went to the effort to add RGBW, then their top request
became RGBWW when the additional work from there is mostly mechanical. It's
a bummer that atruct Pixel no longer fits in a word which can be a drag on
low memory configurations.
This problem, though, is likely something that's just not pinned in IRAM.
Someone with a debugger just needs to repro it. I've tried to repro it
(when filed) and can't. Perhaps with a better repro case, Zach and/or I can
repro it in NightdriverLED context.
I do agree that there are a ton of packages out there that just haven't
kept up in the later silicon, but as existence proof, I have WLED running
on S3, son Makuna code must work there, though I have only run it to a few
hundred pixels.
Oh, one of the things that NightdriverLED had to work around is the
antiquated use of 'register'..I haven't looked lately but has that been
fixed in FastLED? It's a problem in the post c++2017 world.
P. S. Are you Zack or Zach? Over the lunch table I never noticed.
On Fri, Sep 6, 2024, 11:04 AM Zachary Vorhies ***@***.***>
wrote:
… You can reopen the issue. Zack's trying to burn down the list of ancient
bugreports that have been open for up to 8 years and apparently just cut
too deeply. Be prepared to build up a test case that repros this in "raw"
FastLED, though. It's increasingly time to replace FastLED with with Makuna
NeoPixel or maybe I2SClocklessLedDriver. Maybe. I'm leaning toward the
former. But given the requirement of building and running every
combination, I cannot undertake that here. I'll probably eventually do it
in a fork and get "advanced" features like RGBWW, changing pin numbers and
strip types without recompiling, etc.
… <#m_4762911349048884551_>
On Thu, Sep 5, 2024 at 5:49 AM GameTec-live *@*.*> wrote: 😂 yep, sadly
lol — Reply to this email directly, view it on GitHub <#580 (comment)
<#580 (comment)>>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACCSD3ZQNEEVRXOA6LPEMBDZVAZKJAVCNFSM6AAAAABBFMSILWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZRGIYDQMJWGY
<https://github.com/notifications/unsubscribe-auth/ACCSD3ZQNEEVRXOA6LPEMBDZVAZKJAVCNFSM6AAAAABBFMSILWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZRGIYDQMJWGY>
. You are receiving this because you were mentioned.Message ID: @.*>
I already tried to import the I2SClocklessDriver.
Here's the bad news: Doesn't work in C3,S3,C6, only works on Esp32dev.
The developer said he has a working version for s3 but I didn't see it,
maybe I didn't look good enough.
Additionally the readme states that the library works on
Arduino/PlatformIO as a drop in for FastLED.
Problem is: The developer forgot to put in a header include for the
library.json file. I fixed the issue and issued a pull request. But it's
been three days and the developer hasn't merged it in.
I looked at the neopixel bus to see what they did and - yup, same problem,
only works on ESP32DEV and all other platforms are compiled out.
Major bummer. Though I like the thought of running 24 channels of I2S
WS2812 data, the driver is about only 33% done, realistically for someone
that is new and wants to come in and fix it. For the original developer,
this is probably 90% done. I've reached out to the developers of this to
help them get it in for the library but haven't heard back.
Bummer, because this is a fantastic feature. But the ESP32DEV user base is
just too small to justify me wrapping my head on all the crazy espressif
headers to get this done. Our user base wants WS2812 RGBW and that's my top
priority for the next release.
—
Reply to this email directly, view it on GitHub
<#580 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD37UG2REUDFRXBQY2KDZVHHBPAVCNFSM6AAAAABBFMSILWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZUGM3TMMZWGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Ill try and poke a bit more at nightdriver and fastled... for reference ill also drop the links to the exact 2 boards i have (incase someone is crazy enough and wants to try on the exact boards): |
I really don't understand why everyone wants to make the RGBW implementation so freaking difficult. This is my opinion, but Adafruit did it the completely wrong way. They said: there are 4 pixels being outputted so let's give the user 4 pixels to manipulate. Everyone that I've talked to about the RGBW issue seems to have the same opinion. I come from the games industry. We use RGB8 everywhere until HD became a thing, and that was only what, RGB10? Going beyond RGB8 on the client side seems like absolute madness. Are we going to partition our entire blending / fx code too? Are we going to do it again with RGBWW? Shoot me. RGB8 It's good enough for games, it's good enough for our users. So what's my approach?Convert RGB -> RGBW at the fastled driver level. Boom. Done, easy peezy. All the sketches that work today for the RGB pixel type now magically work on the RGBW output pixel type. Blending code stays the same. If RGBWW becomes the rage, then that's supported too very easily (well for non AVR chipsets unless someone wants to change all that asm code). RGB8 is fine, the problem is that the RGB8 on the pixel chipsets don't gamma correct. But future ones do or will give you 16 bit per channel brightness or maybe they'll get smart and realize we only need 5+ bits of global brightness per pixel. I've already done this for APA102HD mode. No gamma correction necessary by the user, it's automatic. Client still uses RGB8, it just looks fantastic. RGB8 is good enough for artists IF the pixels themselves are gamma corrected. This is what games do already and it works great. Will some insist on a W component? Maybe, but they are in the minority. Most users just want to plug in a strip and have it work well. What makes this even easier right now is that it appears that the WS2812 makers have so far standardized W as the last component. So 3-component ordering may stay the same. Though I suspect that the entire industry may just assume standardized ordering going forward since it's a major headache for them to support anything but the standard GRB ordering, which becomes the default for WS2812 on the next release, as god intended it. What's great about the RGBW types is that it seems to reduce power usage. Full blast white for RGB for 30 pixels is 3.8 watts. Full blast white for RGBW (using the white color stealing algorithm) reduces that to 2.6 watts. So it cuts the power down by a 1/3rd. Experimental support for RGBW will be released on Monday. Fun times. (btw it's Zach but you can use either spelling - i don't care) |
Use our clone-and=compile mode for best results. Just clone our repo, open it up in VSCode and hit compile. It's that easy. Your changes go in dev/dev.ino. It's already preset to the esp32-s3 using the open source platformio codebase and uses the new arduion 3+ framework which includes idf 5.1. Once you've repro'd the case, push it to your fork and send me a link and I can see if I can repro it with my XIAO esp32 s3. |
@zackees heres the fun part, I cant rly reproduce it with a simple fastled sketch alone, tried for ~1h now, so ig its the combination of smthng Nightdriver is doing and Fastled thats the problem? |
Can you package it all up into one repo? |
That's like this repo or what do you mean? All you need to do is change the config as ive shown already.I can generate a new patchfile for the current repo versions as the older ones dont apply anymore and youd have to modify the files by hand... I'll send them in a bit... |
I really don't understand why everyone wants to make the RGBW
implementation so freaking difficult.
Because not everyone has the same goal.
Category 1:
Some people want the W bulb as a way to "take the load off" the RGB bulbs
for power delivery.
W=std::mind(r, g, b)
r -= w
g -= w
b -= w
done[1].
The power is saved by using the white bulb (as malformed of color as it may
be because some people like "sickly orange" white light (~3K) and some
people like "cubicle nightmare soft blue" white light (~5K) to be "white".
Neither group calls them that. In fact, they tend to call the OTHER group
that. :-)
These users never want to see the fourth or fifth pixel. They're perfectly
happy to barf up RGB8 and take the savings on their power supplies. They
don't want to change their software At All.
Honestly, this group could have been well served by totally putting the
whole shebang inside the bulb, keeping 24-bits on the wire, changing NO
software, calling this a "power saving WS2812 mutant" and moving the hell
on. But that's not the hand we were dealt.
The other group actually wants to manage them like additional spots of
light in their effects and are prepared to manage them a tiny little spots
of light of ~3K or ~5K "pixel" of its own. They want another 16 bits of
color spectrum out there - admittedly all clumped together - and they're
willing to address and provide another eight (one W) or even sixteen (two
W's) bits to provide it at a per-pixel level in the scene. These people
want struct CRGBWW.
This is my opinion, but Adafruit did it the completely wrong way. They
said: there are 4 pixels being outputted so let's give the user 4 pixels to
manipulate.
Half the users agree with you. (Well, other than the ones in that half that
recognize there are two whites, not one and want to bias the whites
to match.)
Between all three of these halves and the others, their preferred "correct"
answer is 3, 4, or 5 pixels because that's the number of bulbs offering 8
bits of intensity.
I come from the games industry. We use RGB8 everywhere until HD became a
thing, and that was only what, RGB10?
RGB565 fought hard and has a place. But there ARE people designing effects
that use both whites independently in effects.
Going beyond RGB8 on the client side seems like absolute madness. Are we
going to partition our entire blending / fx code too? Are we going to do it
again with RGBWW? Shoot me.
That was exactly my request, yes. RGBWW is here and it's not UNcommon.
Convert RGB -> RGBW at the fastled driver level. Boom. Done, easy peezy.
All the sketches that work today for the RGB pixel type now magically work
on the RGBW output pixel type. Blending code stays the same.
That makes group one above happy enough. It doesn't help group 2a or 2b who
want to treat white as individually addressable pixels happy at all. Those
bits are still occupying space in the transmitted frame and chomping down
the total frame rate. Might as well expose them to animators trying to
highlight or emphasize something, for example.
If RGBWW becomes the rage, then that's supported too very easily (well for
non AVR chipsets unless someone wants to change all that asm code).
My evaluation of 8-bit processors like AVR here in 2010 is pretty clear,
but we disagree on that and that's OK. :-)
What makes this even easier right now is that it appears that the WS2812
makers have so far standardized W as the last component. So 3-component
ordering may stay the same. Though I suspect that the entire industry may
just assume standardized ordering going forward since it's a major headache
for them to support anything but the standard GRB ordering, which becomes
the default on the next release.
That's just not true. I have strips in my collection that use different
ordering for the white channels. At least one of them swaps a white with
Green. One of them swaps a white with Blue. I can't remember any putting
a/either white FIRST, but at least one of the whites always seems to be
last.
So we have the full RGB/BGR/RBG/ {I'm not typing all of those combinations
at this hour and then repeating it with W1 and W2 sprinkled throughout)
matrix to deal with. Lucky us.
From a users's view, I don't dig the way WLED handled it where they let you
pick GRB order and then let you pick which of the pixels to "swap". It
looks very afterthought-ish. Nobody wants to hand a, what, 32-option enum
of alphabet soup to the user. This is one of the few things I've seen I've
seen the "Balance X" (nee Banlan X) get really right. Try a Speril SP530E
or older 630 controller (or just look at the data sheet of the alphabet
soup they support) for motivation.
What's great about the RGBW types is that it seems to reduce power usage.
Full blast white for RGB for 30 pixels is 3.8 watts. Full blast white for
RGBW (using the white color stealing algorithm) reduces that to 2.6 watts.
So it cuts the power down by a 1/3rd.
That's exactly the hook for crowd 1 above, yes.
Experimental support for RGBW will be released on Monday. Fun times.
Groovy.
For all our sanity (including yours and mine since we talk to each other in
like eight different places) let's move the RGBWW discussion out of
Gametec's crash inside FastLED when he has LOL - lots of LEDs. I probably
shouldn't have mentioned it here. Sorry.
(btw it's Zach but you can use either spelling - i don't care)
Thanx. I try to respect a person's preference and I couldn't remember yours.
RJL
[1] Of course, it's not REALLY done. Depending upon the color temperature
of that W (which we rarely know), you want to bias it slightly more red or
blue depending upon the temperature of that W.
… Message ID: <PlummersSoftwareLLC/NightDriverStrip/issues/580/2334756266@
github.com>
|
Man. I've tried two different S3 boards (a YULC and the more traditional
YD-ESP32-S3, which is a DevKitC clone, but with "fixed" USB-C connectors,
like God Herself intended.
I get rainbows out of the port and it keeps on chugging. The frame rate
falls to about 20fps since we have 1500 pixels on this "strip" that's
running off into space.
But I can't get it to crash.
Ugh.
…On Sat, Sep 7, 2024 at 1:22 AM GameTec-live ***@***.***> wrote:
N32R8V-diff.patch
<https://github.com/user-attachments/files/16915104/N32R8V-diff.patch>
—
Reply to this email directly, view it on GitHub
<#580 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD3YUAK4YKWGPEKW37FLZVKLUDAVCNFSM6AAAAABBFMSILWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZVGA4DQNBWGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@robertlipe appreciate the effort, but then smthng must be different? Ive tried 2 different boards, from different sellers, so I doubt that both just happened to randomly be broken in the same way? |
Okay. This is exactly the real world information that i was looking for but couldn't find. Thank you. Looks like I have to define a total ordering for RGBW then. Luckily there is enough room in the EOrdering enum for one additional component. Cheers as always. |
Still looking for a repro case. If there isn't an environment to reproduce this issue then I can't begin the fix it process |
@zackees Idk what more you want / I can provide... It's this repo, I published multiple diffs that set up either a working or broken config (also detailed how to do it yourself, diffs just for convenience) and sent links to the exact boards I own (a ESP32-S3-DevKitC1 32MB 8MB (the main subject) and a smaller S3 board too, id be happy if any of those 2 worked...) Idk what else I can provide? I don't even have to have the matrix connected for the crash to occur, so that isn't a factor... My wifi SSID contains a _, but the crash also happens when putting in my phone hotspot or disabling wifi entirely, so that isn't a factor either... |
I just spent an hour trying to build your project. There are a lot of errors being emitted from the compiler. It could be that you don't have one of your libraries pinned and you are now in a broken state, or something else I can't figure out. What I need from you is the following:
Once you have the branch, reply with this link so that I can By the way, you mentioned that one large alloc of memory works, but that it's not optimal because you can only allocate it to one pin. However, are you aware that FastLED does support segmenting one large LED block into multiple blocks by using offsets? This might solve your problem or at least kick the can down the road. |
Here are some of the errors emitted: ✓ built in 407ms
✨ [vite-plugin-compression]:algorithm=gzip - compressed file successfully:
dist/C:/Users/niteris/dev/NightDriverStrip/site/dist/index.html.gz 1.28kb / gzip: 0.49kb
dist/C:/Users/niteris/dev/NightDriverStrip/site/dist/favicon.ico.gz 15.04kb / gzip: 6.32kb
dist/C:/Users/niteris/dev/NightDriverStrip/site/dist/index.js.gz 50.21kb / gzip: 14.96kb
Build completed, html: 501 B, jsx: 15320 B, ico: 6471 B, total: 21 KB
CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/esp32-s3-devkitc-1.html
PLATFORM: Espressif 32 (6.8.1) > Espressif ESP32-S3-DevKitC-1-N8 (8 MB QD, No PSRAM)
HARDWARE: ESP32S3 240MHz, 320KB RAM, 8MB Flash
DEBUG: Current (esp-builtin) On-board (esp-builtin) External (cmsis-dap, esp-bridge, esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h,
olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES:
- framework-arduinoespressif32 @ 3.20017.0 (2.0.17)
- tool-esptoolpy @ 1.40501.0 (4.5.1)
- toolchain-riscv32-esp @ 8.4.0+2021r2-patch5
- toolchain-xtensa-esp32s3 @ 8.4.0+2021r2-patch5
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 47 compatible libraries
Scanning dependencies...
Dependency Graph
|-- IRremoteESP8266 @ 2.8.6
|-- FastLED @ 3.7.6
|-- Adafruit BusIO @ 1.16.1
|-- Adafruit GFX Library @ 1.11.10
|-- U8g2 @ 2.35.27
|-- arduinoFFT @ 1.6.2
|-- AsyncTCP @ 1.1.1
|-- ESP Async WebServer @ 1.2.3+sha.a6cd518
|-- ArduinoJson @ 6.21.5
|-- Bounce2 @ 2.72.0
|-- RemoteDebug @ 3.0.5+sha.706f093
|-- QRCode @ 0.0.1
|-- TJpg_Decoder @ 1.1.0
|-- UrlEncode @ 1.0.1
|-- HTTPClient @ 2.0.0
|-- ArduinoOTA @ 2.0.0
|-- FS @ 2.0.0
|-- SPIFFS @ 2.0.0
|-- ESPmDNS @ 2.0.0
|-- WiFiClientSecure @ 2.0.0
|-- SPI @ 2.0.0
|-- SD @ 2.0.0
|-- WiFi @ 2.0.0
Building in release mode
Compiling .pio\build\demo\src\deviceconfig.cpp.o
Compiling .pio\build\demo\src\drawing.cpp.o
Compiling .pio\build\demo\src\effectmanager.cpp.o
Compiling .pio\build\demo\src\effects.cpp.o
Compiling .pio\build\demo\src\gfxbase.cpp.o
Compiling .pio\build\demo\src\jsonserializer.cpp.o
Compiling .pio\build\demo\src\ledstripgfx.cpp.o
Compiling .pio\build\demo\src\main.cpp.o
Compiling .pio\build\demo\src\network.cpp.o
Compiling .pio\build\demo\src\ntptimeclient.cpp.o
Compiling .pio\build\demo\src\screen.cpp.o
Compiling .pio\build\demo\src\socketserver.cpp.o
Compiling .pio\build\demo\src\webserver.cpp.o
Compiling .pio\build\demo\libdeb\IRremoteESP8266\ir_Carrier.cpp.o
Compiling .pio\build\demo\libdeb\IRremoteESP8266\ir_ClimaButler.cpp.o
Compiling .pio\build\demo\libdeb\IRremoteESP8266\ir_Coolix.cpp.o
In file included from include/systemcontainer.h:37,
from include/effects/matrix/spectrumeffects.h:38,
from src/drawing.cpp:35:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from include/systemcontainer.h:37,
from src/ntptimeclient.cpp:2:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from include/systemcontainer.h:37,
from src/socketserver.cpp:2:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from src/main.cpp:162:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from include/systemcontainer.h:37,
from src/effectmanager.cpp:34:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
Compiling .pio\build\demo\libdeb\IRremoteESP8266\ir_Corona.cpp.o
In file included from include/systemcontainer.h:37,
from src/network.cpp:41:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from include/systemcontainer.h:37,
from src/deviceconfig.cpp:34:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from include/systemcontainer.h:37,
from include/effects/strip/fireeffect.h:37,
from src/effects.cpp:35:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from include/systemcontainer.h:37,
from src/gfxbase.cpp:34:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from include/systemcontainer.h:37,
from src/ledstripgfx.cpp:33:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from .pio/libdeps/demo/FastLED/src/FastLED.h:63,
from include/globals.h:109,
from src/drawing.cpp:34:
.pio/libdeps/demo/FastLED/src/fastpin.h:13:32: warning: unknown option after '#pragma GCC diagnostic' kind [-Wpragmas]
#pragma GCC diagnostic ignored "-Wvolatile"
^~~~~~~~~~~~
In file included from .pio/libdeps/demo/FastLED/src/platforms/esp/32/fastled_esp32.h:3,
from .pio/libdeps/demo/FastLED/src/platforms.h:42,
from .pio/libdeps/demo/FastLED/src/FastLED.h:67,
from include/globals.h:109,
from src/drawing.cpp:34:
.pio/libdeps/demo/FastLED/src/platforms/esp/32/fastpin_esp32.h:7:32: warning: unknown option after '#pragma GCC diagnostic' kind [-Wpragmas]
#pragma GCC diagnostic ignored "-Wvolatile"
^~~~~~~~~~~~
Compiling .pio\build\demo\libdeb\IRremoteESP8266\ir_Daikin.cpp.o
In file included from include/systemcontainer.h:37,
from src/jsonserializer.cpp:34:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~ |
See the first step in "getting started"
https://github.com/PlummersSoftwareLLC/NightDriverStrip?tab=readme-ov-file#getting-started-with-the-source-code
…On Fri, Sep 13, 2024 at 3:26 AM Zachary Vorhies ***@***.***> wrote:
Here are some of the errors emitted:
✓ built in 407ms
✨ [vite-plugin-compression]:algorithm=gzip - compressed file successfully:
dist/C:/Users/niteris/dev/NightDriverStrip/site/dist/index.html.gz 1.28kb / gzip: 0.49kb
dist/C:/Users/niteris/dev/NightDriverStrip/site/dist/favicon.ico.gz 15.04kb / gzip: 6.32kb
dist/C:/Users/niteris/dev/NightDriverStrip/site/dist/index.js.gz 50.21kb / gzip: 14.96kb
Build completed, html: 501 B, jsx: 15320 B, ico: 6471 B, total: 21 KB
CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/esp32-s3-devkitc-1.html
PLATFORM: Espressif 32 (6.8.1) > Espressif ESP32-S3-DevKitC-1-N8 (8 MB QD, No PSRAM)
HARDWARE: ESP32S3 240MHz, 320KB RAM, 8MB Flash
DEBUG: Current (esp-builtin) On-board (esp-builtin) External (cmsis-dap, esp-bridge, esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h,
olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES:
- framework-arduinoespressif32 @ 3.20017.0 (2.0.17)
- tool-esptoolpy @ 1.40501.0 (4.5.1)
- toolchain-riscv32-esp @ 8.4.0+2021r2-patch5
- toolchain-xtensa-esp32s3 @ 8.4.0+2021r2-patch5
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 47 compatible libraries
Scanning dependencies...
Dependency Graph|-- IRremoteESP8266 @ 2.8.6|-- FastLED @ 3.7.6|-- Adafruit BusIO @ 1.16.1|-- Adafruit GFX Library @ 1.11.10|-- U8g2 @ 2.35.27|-- arduinoFFT @ 1.6.2|-- AsyncTCP @ 1.1.1|-- ESP Async WebServer @ 1.2.3+sha.a6cd518|-- ArduinoJson @ 6.21.5|-- Bounce2 @ 2.72.0|-- RemoteDebug @ 3.0.5+sha.706f093|-- QRCode @ 0.0.1|-- TJpg_Decoder @ 1.1.0|-- UrlEncode @ 1.0.1|-- HTTPClient @ 2.0.0|-- ArduinoOTA @ 2.0.0|-- FS @ 2.0.0|-- SPIFFS @ 2.0.0|-- ESPmDNS @ 2.0.0|-- WiFiClientSecure @ 2.0.0|-- SPI @ 2.0.0|-- SD @ 2.0.0|-- WiFi @ 2.0.0
Building in release mode
Compiling .pio\build\demo\src\deviceconfig.cpp.o
Compiling .pio\build\demo\src\drawing.cpp.o
Compiling .pio\build\demo\src\effectmanager.cpp.o
Compiling .pio\build\demo\src\effects.cpp.o
Compiling .pio\build\demo\src\gfxbase.cpp.o
Compiling .pio\build\demo\src\jsonserializer.cpp.o
Compiling .pio\build\demo\src\ledstripgfx.cpp.o
Compiling .pio\build\demo\src\main.cpp.o
Compiling .pio\build\demo\src\network.cpp.o
Compiling .pio\build\demo\src\ntptimeclient.cpp.o
Compiling .pio\build\demo\src\screen.cpp.o
Compiling .pio\build\demo\src\socketserver.cpp.o
Compiling .pio\build\demo\src\webserver.cpp.o
Compiling .pio\build\demo\libdeb\IRremoteESP8266\ir_Carrier.cpp.o
Compiling .pio\build\demo\libdeb\IRremoteESP8266\ir_ClimaButler.cpp.o
Compiling .pio\build\demo\libdeb\IRremoteESP8266\ir_Coolix.cpp.o
In file included from include/systemcontainer.h:37,
from include/effects/matrix/spectrumeffects.h:38,
from src/drawing.cpp:35:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from include/systemcontainer.h:37,
from src/ntptimeclient.cpp:2:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from include/systemcontainer.h:37,
from src/socketserver.cpp:2:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from src/main.cpp:162:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from include/systemcontainer.h:37,
from src/effectmanager.cpp:34:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
Compiling .pio\build\demo\libdeb\IRremoteESP8266\ir_Corona.cpp.o
In file included from include/systemcontainer.h:37,
from src/network.cpp:41:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from include/systemcontainer.h:37,
from src/deviceconfig.cpp:34:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from include/systemcontainer.h:37,
from include/effects/strip/fireeffect.h:37,
from src/effects.cpp:35:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from include/systemcontainer.h:37,
from src/gfxbase.cpp:34:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from include/systemcontainer.h:37,
from src/ledstripgfx.cpp:33:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
include/deviceconfig.h:77:2: error: #error A definition for cszTimeZone is missing from secrets.h
#error A definition for cszTimeZone is missing from secrets.h
^~~~~
In file included from .pio/libdeps/demo/FastLED/src/FastLED.h:63,
from include/globals.h:109,
from src/drawing.cpp:34:
.pio/libdeps/demo/FastLED/src/fastpin.h:13:32: warning: unknown option after '#pragma GCC diagnostic' kind [-Wpragmas]
#pragma GCC diagnostic ignored "-Wvolatile"
^~~~~~~~~~~~
In file included from .pio/libdeps/demo/FastLED/src/platforms/esp/32/fastled_esp32.h:3,
from .pio/libdeps/demo/FastLED/src/platforms.h:42,
from .pio/libdeps/demo/FastLED/src/FastLED.h:67,
from include/globals.h:109,
from src/drawing.cpp:34:
.pio/libdeps/demo/FastLED/src/platforms/esp/32/fastpin_esp32.h:7:32: warning: unknown option after '#pragma GCC diagnostic' kind [-Wpragmas]
#pragma GCC diagnostic ignored "-Wvolatile"
^~~~~~~~~~~~
Compiling .pio\build\demo\libdeb\IRremoteESP8266\ir_Daikin.cpp.o
In file included from include/systemcontainer.h:37,
from src/jsonserializer.cpp:34:
include/deviceconfig.h:43:2: error: #error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
^~~~~
include/deviceconfig.h:53:2: error: #error A definition for cszPassword is missing from secrets.h
#error A definition for cszPassword is missing from secrets.h
^~~~~
include/deviceconfig.h:57:2: error: #error A definition for cszHostname is missing from secrets.h
#error A definition for cszHostname is missing from secrets.h
^~~~~
include/deviceconfig.h:61:2: error: #error A definition for cszOpenWeatherAPIKey is missing from secrets.h
#error A definition for cszOpenWeatherAPIKey is missing from secrets.h
^~~~~
include/deviceconfig.h:65:2: error: #error A definition for cszLocation is missing from secrets.h
#error A definition for cszLocation is missing from secrets.h
^~~~~
include/deviceconfig.h:69:2: error: #error A definition for bLocationIsZip is missing from secrets.h
#error A definition for bLocationIsZip is missing from secrets.h
^~~~~
include/deviceconfig.h:73:2: error: #error A definition for cszCountryCode is missing from secrets.h
#error A definition for cszCountryCode is missing from secrets.h
^~~~~
—
Reply to this email directly, view it on GitHub
<#580 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD35GJWXKAFY56AMT3BDZWKORXAVCNFSM6AAAAABBFMSILWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBYGM2DCNZWGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yeah that didn't work. Lots of other compilation issues. I'm halting my work on this bug until a repo branch can be made for testing this bug that I can just clone and compile. Compilation errors: src/main.cpp:221:5: note: in expansion of macro 'debugI'
debugI("Version %u: Wifi SSID: \"%s\" - ESP32 Free Memory: %u, PSRAM:%u, PSRAM Free: %u",
^~~~~~
In file included from include/webserver.h:52,
from src/webserver.cpp:32:
include/deviceconfig.h:114:24: error: 'cszHostname' was not declared in this scope
String hostname = cszHostname;
^~~~~~~~~~~
include/deviceconfig.h:114:24: note: suggested alternative: 'GetHostname'
String hostname = cszHostname;
^~~~~~~~~~~
GetHostname
include/deviceconfig.h:115:24: error: 'cszLocation' was not declared in this scope
String location = cszLocation;
^~~~~~~~~~~
include/deviceconfig.h:115:24: note: suggested alternative: 'GetLocation'
String location = cszLocation;
^~~~~~~~~~~
GetLocation
include/deviceconfig.h:116:29: error: 'bLocationIsZip' was not declared in this scope
bool locationIsZip = bLocationIsZip;
^~~~~~~~~~~~~~
include/deviceconfig.h:116:29: note: suggested alternative: 'locationIsZip'
bool locationIsZip = bLocationIsZip;
^~~~~~~~~~~~~~
locationIsZip
include/deviceconfig.h:117:27: error: 'cszCountryCode' was not declared in this scope
String countryCode = cszCountryCode;
^~~~~~~~~~~~~~
include/deviceconfig.h:117:27: note: suggested alternative: 'countryCode'
String countryCode = cszCountryCode;
^~~~~~~~~~~~~~
countryCode
include/deviceconfig.h:118:24: error: 'cszTimeZone' was not declared in this scope
String timeZone = cszTimeZone;
^~~~~~~~~~~
include/deviceconfig.h:118:24: note: suggested alternative: 'GetTimeZone'
String timeZone = cszTimeZone;
^~~~~~~~~~~
GetTimeZone
include/deviceconfig.h:119:33: error: 'cszOpenWeatherAPIKey' was not declared in this scope
String openWeatherApiKey = cszOpenWeatherAPIKey;
^~~~~~~~~~~~~~~~~~~~
include/deviceconfig.h:119:33: note: suggested alternative: 'GetOpenWeatherAPIKey'
String openWeatherApiKey = cszOpenWeatherAPIKey;
^~~~~~~~~~~~~~~~~~~~ |
This is the same problem..Edits secrets.h like it says and provide values
for those fields.
…On Fri, Sep 13, 2024, 1:44 PM Zachary Vorhies ***@***.***> wrote:
Yeah that didn't work. Lots of other compilation issues.
I'm halting my work on this bug until a repo branch can be made for
testing this bug that I can just clone and compile.
Compilation errors:
src/main.cpp:221:5: note: in expansion of macro 'debugI'
debugI("Version %u: Wifi SSID: \"%s\" - ESP32 Free Memory: %u, PSRAM:%u, PSRAM Free: %u",
^~~~~~
In file included from include/webserver.h:52,
from src/webserver.cpp:32:
include/deviceconfig.h:114:24: error: 'cszHostname' was not declared in this scope
String hostname = cszHostname;
^~~~~~~~~~~
include/deviceconfig.h:114:24: note: suggested alternative: 'GetHostname'
String hostname = cszHostname;
^~~~~~~~~~~
GetHostname
include/deviceconfig.h:115:24: error: 'cszLocation' was not declared in this scope
String location = cszLocation;
^~~~~~~~~~~
include/deviceconfig.h:115:24: note: suggested alternative: 'GetLocation'
String location = cszLocation;
^~~~~~~~~~~
GetLocation
include/deviceconfig.h:116:29: error: 'bLocationIsZip' was not declared in this scope
bool locationIsZip = bLocationIsZip;
^~~~~~~~~~~~~~
include/deviceconfig.h:116:29: note: suggested alternative: 'locationIsZip'
bool locationIsZip = bLocationIsZip;
^~~~~~~~~~~~~~
locationIsZip
include/deviceconfig.h:117:27: error: 'cszCountryCode' was not declared in this scope
String countryCode = cszCountryCode;
^~~~~~~~~~~~~~
include/deviceconfig.h:117:27: note: suggested alternative: 'countryCode'
String countryCode = cszCountryCode;
^~~~~~~~~~~~~~
countryCode
include/deviceconfig.h:118:24: error: 'cszTimeZone' was not declared in this scope
String timeZone = cszTimeZone;
^~~~~~~~~~~
include/deviceconfig.h:118:24: note: suggested alternative: 'GetTimeZone'
String timeZone = cszTimeZone;
^~~~~~~~~~~
GetTimeZone
include/deviceconfig.h:119:33: error: 'cszOpenWeatherAPIKey' was not declared in this scope
String openWeatherApiKey = cszOpenWeatherAPIKey;
^~~~~~~~~~~~~~~~~~~~
include/deviceconfig.h:119:33: note: suggested alternative: 'GetOpenWeatherAPIKey'
String openWeatherApiKey = cszOpenWeatherAPIKey;
^~~~~~~~~~~~~~~~~~~~
—
Reply to this email directly, view it on GitHub
<#580 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD3236JGTUKU3LY46OHTZWMXBJAVCNFSM6AAAAABBFMSILWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBZHA3DKMZTHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
No. The developer can do this and push a branch. Someone else with an NRF52 board issue just gave me a repro case and I fixed the bug in one hour. The dev here can meet me halfway on this. |
I was 90% sure that I'd already made this almost impossible to mess up. I
did. On 9 a.m. of Christmas Eve in
#574 Rutger
merged it later that day.
Now that I'm reading Zach's message from a computer and not my phone in the
middle of the night, the solution is the very first error issued. Because
Platformio/scons doesn't have a [ censored ] brain, it proceeds to compile
eleventy hundred files that bury that #error. I just confirmed in a local
tree that this actually works and it's in the first error that Zach
reported:
In file included from include/systemcontainer.h:37,
from include/effects/matrix/spectrumeffects.h:38,
from src/drawing.cpp:35:
include/deviceconfig.h:43:2: error: #error Copy
include/secrets.example.h to include/secrets.h, edit to taste, and
retry. Please see README.md.
#error Copy include/secrets.example.h to include/secrets.h, edit to
taste, and retry. Please see README.md.
^~~~~
include/deviceconfig.h:49:2: error: #error A definition for cszSSID is
missing from secrets.h
#error A definition for cszSSID is missing from secrets.h
So the build instructions give the solution, the code gave the
solution, and I have the solution twice.
I'm somewhat guilt-obligated to observe that we COULD further
special-case the build to not NEED time zones, WiFi IDs, Weather
providers, etc.
#if !defined ENABLE_WIFI && !defined INCOMING_WIFI_ENABLED /
ENABLE_OTA / any other other traces of using WiFi on this chip whose
whole purpose is to expose WiFi, but I'm not sure how many levels of
recursion into protecting a builder from not reading/following
instructions
we really should go as I think we've provided plenty.
The point that it's using fastled 3.4.0 is similarly invalid.
platformio.ini requests
fastled/FastLED @ ^3.4.0
which is any version greater than 3.4.0 that's API compatible
<https://docs.platformio.org/en/latest/core/userguide/lib/cmd_update.html>.
If you grovel around in platformio's dumpster
pio/libdeps/demo/FastLED//release_notes.md, you will likely see the
file starts off with a version that's > 3.4.0. I was pretty sure this
was the case because recent changes in FastLED's "hey, we have to
touch hardware now!!!!!" banners have been showing up
<FastLED/FastLED#1169> in everyone's builds
as they've been changed.
Compiling .pio/build/spectrum/src/ntptimeclient.cpp.o
Compiling .pio/build/spectrum/src/remotecontrol.cpp.o
In file included from
.pio/libdeps/spectrum/FastLED/src/platforms/esp/32/fastled_esp32.h:6,
from .pio/libdeps/spectrum/FastLED/src/platforms.h:42,
from .pio/libdeps/spectrum/FastLED/src/FastLED.h:66,
from include/globals.h:109,
from src/main.cpp:161:
.pio/libdeps/spectrum/FastLED/src/platforms/esp/32/fastspi_esp32.h:2:17:
note: #pragma message: ESP32 Hardware SPI support added
#pragma message "ESP32 Hardware SPI support added"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Compiling .pio/build/spectrum/src/screen.cpp.o
So I'm quite sure that nobody is on 3.4.0. But don't dwell on those
annoying messages; they're just an indicator that our users are
tracking at least moderately recent values of FastLED.
In addition to GameTec's steps, you may find it useful that
pio run -e demo
should be enough to repro this; you don't need to wait 90+ minutes to
download the same stinking packages 39 times to build all 39 of this
project's environments (See also: platformio stupidity
<https://community.platformio.org/t/distributed-build-with-distcc/11518/4>.)
I know it's the weekend and we'd all rather be playing outside than
staring at debugger crashes on a JTAG pod, but a full
git fetch, cp inc*/secre*.h inc*/secrets.h ; vim inc*/sec*.h ; pio run -e demo
should take ~4-5 minutes, which is a tiny fraction of what any one of
us active in this conversation has spent. I know I've spent
waaaaaay more than that, and I just can't repro it and I have no idea
why...and I know the S3 more than reasonably well. I tried to
grok FastLEDs #ifdef tangles, but fled since I couldn't see the
affected case or even get a JTAG lead on the crash anyway.
If I were to guess, something in the interrupt path is taking long
enough it's being deferred to a thread OR SOMETHING or
possibly there's contention on the bus about holding a bus lock too
long and one of the cores is trying to access something
in interrupt context that's not locked into IRAM. But that's totally a
guess. However, it's an experienced guess because I spent
many hours chasing a problem report
<#195>on
"large" (multi-strip) fastled configurations to produce this fix
<#515>(which
doesn't fix
GameTec's issue as it's now been inthe tree almost a year) that's deep
inside the FastLED clockless_rmt_esp32.cpp code where
one core was handling an RMT interrupt that wasn't locked into flash
while the other was handling SPI in the foregroiund (or
something like that - again, it's late and I'm not digging up all that
history that may ore may not be pertinent, just to establish
that I have been more than a casual visitor inside the ESP32 code.
Other people still had issues with FastLED crashing and
reported them in 1220 <FastLED/FastLED#1220>
with no resolution in sight, so I didn't have a lot of faith in that
being a well exercised combination.
I remain hopeful that you - or anyone on the FastLED team - can find
and fix this issue.
Thanx!
RJL
…On Fri, Sep 13, 2024 at 3:25 PM Zachary Vorhies ***@***.***> wrote:
No. The developer can do this and push a branch.
Someone else with an NRF52 board issue just gave me a repro case and I
fixed the bug in one hour. The dev here can meet me halfway on this.
—
Reply to this email directly, view it on GitHub
<#580 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD35FPFAGX5PHRMZI7RLZWNC2LAVCNFSM6AAAAABBFMSILWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJQGA4TSNRVHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
In NPM, ^ will increment the third version number which is assumed to be bug fixes. I believe the second number means minor API breakages. So I think that ^ will bind to 3.4.0, 3.4.1... but not 3.5.XX ... But I could be wrong. |
You are. NPM is irrelevant. This is python-semver rule knife-fight.
<https://docs.platformio.org/en/latest/core/userguide/pkg/cmd_install.html#cmd-pkg-install-requirements>
API changes are first digit, <https://devhints.io/semver>not second.
^1.2.3 is >=1.2.3 <2.0.0
$ head .pio/libdeps/*/FastLED/release_notes.md
to convince yourself of that.
…On Mon, Sep 16, 2024 at 12:40 AM Zachary Vorhies ***@***.***> wrote:
The point that it's using fastled 3.4.0 is similarly invalid.
platformio.ini requests
fastled/FastLED @ ^3.4.0
which is any version greater than 3.4.0 that's API compatible
In NPM, ^ will increment the third version number which is assumed to be
bug fixes. I believe the second number means minor API breakages. So I
think that ^ will bind to 3.4.0, 3.4.1... but not 3.5.XX ...
But I could be wrong.
—
Reply to this email directly, view it on GitHub
<#580 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCSD32YV5CVI4PIOPI5WY3ZWZVMTAVCNFSM6AAAAABBFMSILWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJSGA2TEOJRGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks! TIL! |
Btw robert, what's your relation to this project? |
@zackees Although the question was not directed at me, I'll be so bold as to answer your question from a maintainer's perspective. In my view, Robert has been very helpful to this project in multiple ways:
I find it difficult to capture it in one term, but I think "Most Valued Contributor" goes in the right direction - in the broadest sense of the term. I hope this helps? |
I’m happy to second that - Robert has been knee deep into some gnarly issues, especially ESP32 minutiae, and getting things to work. He probably knows the code as well as anyone at this point! If anything he’s too prolific at times and we likely frustrate his efforts, but they’re always appreciated! :-)
- Dave
… On Sep 16, 2024, at 5:37 PM, Rutger van Bergen ***@***.***> wrote:
@zackees <https://github.com/zackees> Although the question was not directed at me, I'll be so bold as to answer your question from a maintainer's perspective.
In my view, Robert has been very helpful to this project in multiple ways:
He has contributed the largest number of new effects to the project - in fact I believe he is the only contributor who has added any effect, aside from the project's initiator.
He has been very helpful with on-boarding people newly engaging with the project.
He has contributed to the analysis and resolution of many problems that project users have run into.
He has made numerous suggestions for improvements to the project's codebase, architecture and documentation - both in terms of code (reviews) and ideas -, many of which were non-trivial to put it mildly.
I find it difficult to capture it in one term, but I think "Most Valued Contributor" goes in the right direction - in the broadest sense of the term.
I hope this helps?
—
Reply to this email directly, view it on GitHub <#580 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4HCF4HV3TUHB2DTB7LGH3ZW52UFAVCNFSM6AAAAABBFMSILWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJUGI3TAMJZHA>.
You are receiving this because you commented.
|
Cool stuff. Same offer still holds. Please make a branch that I can download and get up running quickly and I'll tackle this issue. |
I just pumped 24k RGBW pixels through an s3 - no crash. Try changing your platform to the open source version of platformio with the latest ardunio:
See my platformio.ini below. dev.ino #include <FastLED.h>
// How many leds in your strip?
#define NUM_LEDS 24000
// For led chips like WS2812, which have a data line, ground, and power, you just
// need to define DATA_PIN. For led chipsets that are SPI based (four wires - data, clock,
// ground, and power), like the LPD8806 define both DATA_PIN and CLOCK_PIN
// Clock pin only needed for SPI based chipsets when not using hardware SPI
#define DATA_PIN 9
// Define the array of leds
CRGB leds[NUM_LEDS];
// Time scaling factors for each component
#define TIME_FACTOR_HUE 60
#define TIME_FACTOR_SAT 100
#define TIME_FACTOR_VAL 100
void setup() {
Serial.begin(115200);
FastLED.addLeds<WS2812, DATA_PIN, GRB>(leds, NUM_LEDS).setRgbw(RgbwDefault());
FastLED.setBrightness(128); // Set global brightness to 50%
delay(2000); // If something ever goes wrong this delay will allow upload.
}
void loop() {
uint32_t ms = millis();
for(int i = 0; i < NUM_LEDS; i++) {
// Use different noise functions for each LED and each color component
uint8_t hue = inoise16(ms * TIME_FACTOR_HUE, i * 1000, 0) >> 8;
uint8_t sat = inoise16(ms * TIME_FACTOR_SAT, i * 2000, 1000) >> 8;
uint8_t val = inoise16(ms * TIME_FACTOR_VAL, i * 3000, 2000) >> 8;
// Map the noise to full range for saturation and value
sat = map(sat, 0, 255, 30, 255);
val = map(val, 0, 255, 100, 255);
leds[i] = CHSV(hue, sat, val);
}
FastLED.show();
} platformio.ini
|
Bug report
32MB FLASH 8MB PRAM ESP32-S3-DevKitC1(ESP32-S3-DevKitC-1-N32R8V)
Problem
Steps
Example
Notes
In this case a "Matrix" is just a bunch of daisychained LED strips going back and forth.
My globals.h
globals.h.txt
Same exact config file works fine on a generic, less powerful, esp32.
And reportedly running 1500 leds on one controller isnt optimal, but it works fine and i get a decent frame rate on my underpowered esp32. It shouldnt crash anyways ;)
Monitor Log:
https://hastebin.skyra.pw/wikevijele.yaml
The text was updated successfully, but these errors were encountered: