-
Notifications
You must be signed in to change notification settings - Fork 49
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
[SparkleMotionMini] Having too many classes of things enabled as board comes online causes reboot #687
Comments
Been seeing a lot of publish failed messages recently so added logging on all of them, along with migrating to use the wipper publish function, and printing stack/heap info. On this branch: https://github.com/tyeth/Adafruit_Wippersnapper_Arduino/tree/publish-returns-bool Suddenly drops off in stack size towards the end: Log With Stack/Heap info:
ets Jul 29 2019 12:21:46 rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
|
@brentru not much further, the stack does get exhausted, but doesn't get consumed with regularity (or as I'd expect). |
Seems like there is some conflict, but think it worked as a NeoPixel while board was already online. Needs retestingTesting:
Not found to affect a second board with no external components plugged in, but external neopixel pins active and onboard neopixel active, and rebooted.
Second device has 256 pixels on D32, the onboard pixel set to white (and other onboard components added), plus a SEN66 I2C sensor which has a lot of subcomponents (9).
Summary
It looks like there is too deeper stack or too many unfinished MQTT transactions, via the exception decoder (using the release elf file which is included for littleFS builds):
https://gist.github.com/tyeth/cb44cd253df74d6beb92def689cb58e2
Just looking at the publish and decodes, we're clearly still waiting for the publish acknowldegement from the initial pinSetupComplete, but instead of waiting for that we have processed subscriptions for the next stages (component init/add)
Details
Output:
The text was updated successfully, but these errors were encountered: