Table of Contents
Keep your hands of our code
If you have the same interests as me, then you can probably relate the way these programming sessions go; one succes after another, you keep coding and trying hours after hours and once you stumble accross a setback, you can’t get your head around how this could have gone wrong? How can this result not be what I expected it to be? Taking a step back, literally, often shines a new light on your problem.
So I made myself a cup of tea and then I suddenly realised I have seen this behaviour before. Code protection. It is a thing. Often these microchips have some bits you can set after testing so no one is able to steal your code of the chip. So I retreived the code protection bits and I confirmed my worst nightmare at that moment: this chip was code protected. No easy way to get code from this chip. If you want to reset these bits, you have to erase the whole chip, but that would defeat the purpose of what I was trying to achieve: getting the firmware in the first place before writing to the chip.