“I changed the [continuous integration] build toolchain between fw157 and fw158, and the new compiler used a little more stack,” Abrasive said on his Discord server. “It triggers rarely because a particular interrupt has to arrive while another particular piece of code is running, together their stack usage is too much.”
-Abrasive
Abrasive said he had moved a stack into DRAM that “really needed to stay in SRAM.”
“Uncached DRAM is pretty slow,” he said, “especially if you’re accessing multiple pages randomly.”
This is the second update to the Satiator’s firmware since Abrasive returned from a nine-month hiatus in early February.
That update, FW158, issued a fix for some units hanging on bootup.
Abrasive has said that he’s focusing more time on fixing issues customers have encountered, something he’s able to do since taking a step back from his job in the medical technology industry.
For more general information regarding the Satiator ODE, currently in stock at satiator.net check out the following SHIRO! Review:
is there a current invite to abrasive’s discord?
Here you go: https://discord.gg/9NCtYBQw