If you can read the bytes you could put them through a disassembler...
But only if you know where the instruction boundary is. One trick I used to use for protecting EPROM code before protection resistors came in, was to put in a rouge byte or two in between subroutines so a disassembler would be thrown off and read back rubbish.
It is depending upon the manufacturer and also programmer. Some programmer protecting the code from code infringement. which means you can use that chip but you can't read the source code from program memory.
Some fuses and registers are set by programmer or developers.
Grumpy_Mike:
But only if you know where the instruction boundary is. One trick I used to use for protecting EPROM code before protection resistors came in, was to put in a rouge byte or two in between subroutines so a disassembler would be thrown off and read back rubbish.
One trick I used to use for protecting EPROM code before protection resistors came in, was to put in a rouge byte or two in between subroutines so a disassembler would be thrown off and read back rubbish
You could follow the call , jump, and return instructions.....
I had plenty more I used to sprinkle around to fool disassemblers. A lot depended on the instruction set, and some included jumping into what would be the second or third byte of a multi byte instruction so the disassembler could not get it right.
One of the points was so that if someone stole the code wholesale it would contain all this rubbish that would mark it out, in a court of law as being exactly copied.