However, the fun part about this particular attack is that it does not require quite the same level of precision. The voltage is dropped incrementally until the CPU starts to make faulty calculations. It just so happens that AES is one of the most complex operations, and thus, the first to start faulting.
I presume the CPU here was VERY cost conscious and so trade-offs were made.
I have no background in gaming but have worked with flawed "security" solutions. Often the business does not care that the engineers explain how flawed some security thing is before release, if there's more money to be made by not fixing it then it won't get fixed. Often doing all of the right things is MUCH too expensive, either in dollars, size, or power.
It was also more intended as a media chipset and they managed to flog it to Nintendo, and was an early effort by the team involved.
How do you know if external voltage is low if you check it against... a voltage derived from it?
In re "properly secured system": it's a cost-sensitive games console for children, while there's a big incentive against piracy ultimately there's a limit to how much you can defend. And this is the second line of defense, the bootloader having been breached earlier.
> What is body bias?
> Body bias is used to dynamically adjust the threshold voltage (Vt) of a CMOS transistor. While CMOS transistors are usually thought of as having three terminal devices, with terminals for the source, gate, and drain, it’s increasingly common to have a fourth terminal connected to the body (substrate). Because the voltage difference between the source voltage (Vs) and body voltage (Vb) affects the Vt, the body can be thought of as a second gate that helps determine how a transistor turns on and off.
https://semiengineering.com/body-bias-what-it-is-and-why-you...
https://research.nccgroup.com/2020/10/15/theres-a-hole-in-yo...
That was 8 years ago
Or perhaps the ECC simply works well enough that there's no perceptible data loss for audio?
that said, one of the first copy protection schemes involved writing specific sectors to a magnetic disk with an invalid checksum. when the program would start, it would verify that reading those sectors would return an error, but if you used a regular disk copy program it would not copy the invalid sectors- either resulting in an aborted copy or a copy that would zero out the bad sectors on the target which would not produce the expected read errors on startup telling the program it had been copied.
https://scarybeastsecurity.blogspot.com/2020/06/weak-bits-fl...
http://dmweb.free.fr/?q=node/210
http://dmweb.free.fr/?q=node/1429
https://scarybeastsecurity.blogspot.com/2020/07/turning-400-...
This one describes very similar floppy protection - encoding physical disk parameters in the executable per every individual disk. https://scarybeastsecurity.blogspot.com/2020/12/the-cleveres...
As an aside, I hate all of this. If someone made an open console, I'd buy it in a second. I realise that's probably my computer running linux next to me, but still...
Steam Deck?
The general field is called PUF (physically uncloneable functions)
https://en.m.wikipedia.org/wiki/Physical_unclonable_function
https://chipwhisperer.readthedocs.io/en/latest/tutorials/cou...
https://chipwhisperer.readthedocs.io
https://www.newae.com/chipwhisperer
https://embedded.fm/episodes/286 (podcast interview)