We've got a bunch of DeskHogs now in the wind, and there's a problem with 0.1.5: you can OTA-update into it, but can't OTA back out. Which is a shame because the power management adjustments it delivered didn't seem to make a big difference.
Basically: all downside.
There's actually a range of versions flashed to the various rounds of DeskHog kits, so rather than trap more folks on 0.1.5, I've removed the release. You can still access the tag, for posterity:
https://github.com/PostHog/DeskHog/releases/tag/0.1.5
What we know so far
We're allocating PSRAM to parse the JSON , and there's plenty of it to spare. We only need 3K of JSON to satisfy an OTA update run.
Logs suggest some sort of memory corruption at this point, but this is beyond the ability of cowboy logging and hoping the LLM gets lucky. I think this gets solved with proper step debugging.
But how does that work with ESP32-S3 and PlatformIO? Can't put off figuring it out any further. I hope it doesn't require some arcane probe.
So if you, or anyone you know, can enable interactive GUI debugging
PR's welcome!
(The PR could be extremely brief documentation. You'd earn a Picard Facepalm gif in my sheepishness if it turns out this was much simpler than I thought.)
We've got a bunch of DeskHogs now in the wind, and there's a problem with 0.1.5: you can OTA-update into it, but can't OTA back out. Which is a shame because the power management adjustments it delivered didn't seem to make a big difference.
Basically: all downside.
There's actually a range of versions flashed to the various rounds of DeskHog kits, so rather than trap more folks on 0.1.5, I've removed the release. You can still access the tag, for posterity:
https://github.com/PostHog/DeskHog/releases/tag/0.1.5
What we know so far
We're allocating PSRAM to parse the JSON , and there's plenty of it to spare. We only need 3K of JSON to satisfy an OTA update run.
Logs suggest some sort of memory corruption at this point, but this is beyond the ability of cowboy logging and hoping the LLM gets lucky. I think this gets solved with proper step debugging.
But how does that work with ESP32-S3 and PlatformIO? Can't put off figuring it out any further. I hope it doesn't require some arcane probe.
So if you, or anyone you know, can enable interactive GUI debugging
PR's welcome!
(The PR could be extremely brief documentation. You'd earn a Picard Facepalm gif in my sheepishness if it turns out this was much simpler than I thought.)