For some reason the M16 core turns write protect on after erasing some sectors. Guess: Perhaps some sectors do not exist on some device and in error case it protects itself?
View differences: inline side by side
Also available in: Unified diff
For some reason the M16 core turns write protect on after erasing some sectors. Guess: Perhaps some sectors do not exist on some device and in error case it protects itself?