> I guess this kind of protection is quite useless, perhaphs this is > why Philips doen't disclosure the JTAG direct access to Flash > read/write routines, but it's pretty simple to disassemble IAP > bootloader (I've read somewhere on Russian ARM forum that there are > few peoples who are doing this) and to have direct access to Flash > through JTAG instead through IAP > I even read on the same Russian forum that one guy sucessfully > overwrote (by mistake) bootloader Flash when tried to write huge file > through the Philips ISP, thus made the chip absolutely useless > without the bootloader code inside. I had tried to overwrite the bootloader by programming a big file. Nothing happened. All I got was a warning from the Philips ISP tool about file being bigger than the Flash. I had experimented with the different file sizes but the bootloader was never overwritten. Can you please dig some more information from the Russian forum. I won't discount the code read protection feature just because of some rumors. I would like to get my hands dirty with a chip and do more expriments to assess how difficult/expensive it is to break the protection. Regards Tom
Message
Re: Code Protection
2004-02-23 by lpc2100
Attachments
- No local attachments were found for this message.