|
Post by jethronull on Apr 29, 2014 14:57:02 GMT -8
Almost certainly my code, since you are the guru here. After the last couple of things you helped me out with everything has been going smoothly. However today I was trying to hammer the UI (pushing lots of buttons repeatedly just to see what would happen). It's not predictable but some buttons do cause it to hang after being pressed multiple times. On every change I made to the code the button/count permutation would change. That suggests to me a runaway variable somewhere. But here's the thing, what goes wrong is always the display, it hangs, or crashes or shows garbage, which leads me to suspect the offending code is in GD2/FT800, although it's probably something stupid that I'm asking it to do that triggers it. My code hangs too but that's probably because I am polling GD.get_inputs() and I am guessing that if the FT800 hangs that never returns.
I'm using Visual Micro/Atmel Studio so have the use of a debugger but (afaik) it doesn't show where abouts in the code it stopped, just breakpoints. I've tried scattering bp's all over the place but havn't been able to narrow it down.
I also tried setting the SPI speed lower but I suspect GD2 overwrites that back to it's norm.
Any ideas of tracking this down would be most appreciated.
|
|
|
Post by jethronull on Apr 30, 2014 14:59:59 GMT -8
OK, many hours later herding cats... found it: the notorious String/maloc.c curse. I so want to be able to use String, darn.
|
|