A great and short read
Who knows, we may be running into this more literally in our lifetime.
You can find the paper (Formally Proved Security of Assembly Code Against Power Analysis) and presentation slides on my web page: https://pablo.rauzy.name/research.html#rauzy2014formaldpl
This is all about reducing power consumption down in the nA range when the CPU is turned off but the RTC keeps ticking over.
Multiple clock domains definitely tricky though!
http://www.sunburst-design.com/papers/CummingsSNUG2008Boston...
What sort of glitches? Which effects could they produce on outputs?
I wish there was a concrete example.
"For example, there's a glitch in the external address bus logic that causes internal bus addresses like 0xFF20 to appear on the external bus even though the logic should prevent that. Due to gate delays, not all of the inputs to gate LOXO (page 8 in Furrtek's schematics) arrive at the same time. This causes LOXO to produce a glitch pulse that in turn causes latch ALOR to make a copy of one bit of the internal bus address. ALOR then drives that bit onto the external bus (through a few more gates) where it can be seen with an oscilloscope or logic analyzer."
> Actually no, for complicated reasons. The Game Boy chip has a handful of logic gates that operate independently of the master clock and whose exact behavior depends on things like gate delay. These gates create glitches that depend heavily on the physical placement of the gates, the silicon process used to make them, and other weird things like temperature and voltage.
This is fascinating, I previously would have assumed that a gate-level simulation would necessarily be perfect by definition.