3 ms·
> It can dump the firmware but it can still execute something else than this (or in addition to) this firmware, can't it? Well, of course, in theory. In practi
by unwind 12y ago
> It can dump the firmware but it can still execute something else than this (or in addition to) this firmware, can't it?
Well, of course, in theory. In practice the total amount of firmware space is limited. It's rather large, as these things go, at 256 or 512 KB depending on the exact model.
If it dumps a firmware close to that size, which passes scrutiny by several people, I would say that the risk that the chip still manages to contain a firmware which creates bad random data and a fake firmware is rather slim.
Of course it's not impossible, and if you made it a contest (which, perhaps it is to some people) I'm sure it could be done.
It's hard to trust digital systems of this complexity; what if you decide you don't trust TI (the makers of the microcontroller) in the first place, for instance? Building your own processor at this performance and size level isn't trivial.
- Taniwha 12y agothe actual firmware is far smaller than that (see my explanation about how we pad it out above) - essentially the way you verify it is by compiling the (open) source and getting the same binary image (and then of course one verifies the source by inspection)