3 ms·
My favourite case of this was simply "touchscreen sometimes doesn't work". That took over a year before it even made it to us developers, being reported intermi
by pjc50 2y ago
My favourite case of this was simply "touchscreen sometimes doesn't work". That took over a year before it even made it to us developers, being reported intermittently across a large number of point of sale systems. Sensibly, people were reluctant to pass on something that they couldn't reproduce, and it was often blamed on hardware issues or user error, such as damage from people operating the (resistive) touchscreen with a bunch of keys or the smooth metal Dallas key fob that was also used for log in.
We eventually got a robot to reproduce some other issues with PIN pads (which for obvious reasons do not support any kind of software injection of input!), and got some time using the robot to press the touchscreen over and over. That way we were able to confirm it happening, and start the debug process.
(anticlimactically, I can't quite remember what the resolution was, something to do with debounce logic and interrupt events)
- vardump 2y ago> something to do with debounce logic and interrupt events Oh, the classic, an unfiltered hardware button connected to a GPIO that generates an IRQ? What could go wrong... :-D For the uninitiated: https://en.wikipedia.org/wiki/Switch#Contact_bounce https://en.wikipedia.org/wiki/Switch#Contact_bounce