--- In , "microbit" <microbit@c...> wrote: > Hi all, > > Out of curiousity, I've put in an ORG directive to > place 0x87654321 at address 0x1FC in Flash to see if > the code protection works. > Reading the code back and comparing with Bootloader > is succesful - thus the part isn't protected. > I'm using an LPC2119 Bootloader ID = 1.6. > > Anyone know what I'm doing wrong ? > I thought these parts had protection in there ? > > -- Kris Hi Kris, take a look at the usermanual(2004-05-03) at page 269. Sorry your bootloader version must be 1.61 or higher. Andreas

An Engineer's Guide to the LPC2100 Series

Hi all, Out of curiousity, I've put in an ORG directive to place 0x87654321 at address 0x1FC in Flash to see if the code protection works. Reading the code back and comparing with Bootloader is succesful - thus the part isn't protected. I'm using an LPC2119 Bootloader ID = 1.6. Anyone know what I'm doing wrong ? I thought these parts had protection in there ? -- Kris

Yes, thank you... I found that link easily on Google, but I wondered why Philips would now have that very important information in their documentation or even on their web site. I believe I had seen a message from Philips regarding the issue though on some other web forum. thanks, bob --- In , "Hugh O'Keeffe" <hugh.okeeffe@a...> wrote: > Hi Bob, > > Rest assured that flash protection works and is endorsed by Philips; they > are working on the docs AFAIK. . See the FAQ on our site for some important > information: > <http://www.ashling.com/support/lpc2000/knowledge_base.html> > http://www.ashling.com/support/lpc2000/knowledge_base.html. In particular, > the section " <http://www.ashling.com/support/lpc2000/knowledge_base.html#> > How do I enable LPC2000 Flash Read protection? " > > > Hugh @ <http://www.ashling.com/support/lpc2000/> > http://www.ashling.com/support/lpc2000/ > -----Original Message----- > From: bobtransformer [mailto:bgudgel@e...] > Sent: 05 May 2004 03:34 > To: > Subject: [lpc2000] Re: Code protection > > Hi folks... I'm coming from AVR land, (because of defective Atmel > silicon and looking at these LPC parts), and see that writing 0x1fc > with 0x87654321 (sector 0 ?) protects the flash from being read. > > I am curious if this is actually documented by Philips or somewhere > else. > > I cannot seem to find any references to it except on forums etc... > > Thanks, > bob > <http://rd.yahoo.com/SIG9k0qee0/M)5196.4901138.6052515.3001176/D= groups > /S06554205:HM/EXP83810837/A!28215/R=0/SIGse96mf6/*http:// companio > n.yahoo.com> click here > > <http://us.adserver.yahoo.com/l? M)5196.4901138.6052515.3001176/D=groups/S= > :HM/A!28215/rand5783158 > _____ > > > .

The reason I am interested in looking at other parts are because of Atmels bad silicon on the ATmega32,64, and 128 parts and Atmels poor response to customers problems. The parts don't work at 16 MHz and sometimes down to even 10 or 12 MHz when warm. http://www.avrfreaks.net/phpBB2/viewtopic.php?t647 Thanks, bob --- In , "douglasbolton" <doug@c...> wrote: > --- In , "bobtransformer" <bgudgel@e...> wrote: > > > > Hi folks... I'm coming from AVR land, (because of defective Atmel > > silicon and looking at these LPC parts), and see that writing > 0x1fc > > with 0x87654321 (sector 0 ?) protects the flash from being read. > > > > I am curious if this is actually documented by Philips or somewhere > > else. > > > > I cannot seem to find any references to it except on forums etc... > > > > Thanks, > > bob > > We are also moving to the LPC parts because of problems with the avr. > For my interest, was your problems with the avr corruption of flash > code at boot up ??

Message

Hi Bob,

Rest assured that flash protection works and is endorsed by Philips; they are working on the docs AFAIK. . See the FAQ on our site for some important information:

http://www.ashling.com/support/lpc2000/knowledge_base.html. In particular, the section "How do I enable LPC2000 Flash Read protection? "

Hugh @ http://www.ashling.com/support/lpc2000/

-----Original Message-----
From: bobtransformer [mailto:b...@eskimo.com]
Sent: 05 May 2004 03:34
To: l...@yahoogroups.com
Subject: [lpc2000] Re: Code protection

Hi folks... I'm coming from AVR land, (because of defective Atmel silicon and looking at these LPC parts), and see that writing 0x1fc with 0x87654321 (sector 0 ?) protects the flash from being read. I am curious if this is actually documented by Philips or somewhere else. I cannot seem to find any references to it except on forums etc... Thanks, bob

--- In , "bobtransformer" <bgudgel@e...> wrote: > > Hi folks... I'm coming from AVR land, (because of defective Atmel > silicon and looking at these LPC parts), and see that writing 0x1fc > with 0x87654321 (sector 0 ?) protects the flash from being read. > > I am curious if this is actually documented by Philips or somewhere > else. > > I cannot seem to find any references to it except on forums etc... > > Thanks, > bob We are also moving to the LPC parts because of problems with the avr. For my interest, was your problems with the avr corruption of flash code at boot up ??

Hi folks... I'm coming from AVR land, (because of defective Atmel silicon and looking at these LPC parts), and see that writing 0x1fc with 0x87654321 (sector 0 ?) protects the flash from being read. I am curious if this is actually documented by Philips or somewhere else. I cannot seem to find any references to it except on forums etc... Thanks, bob

Message

Hi Gus,

Yes, it does work, however, note the following:

It's only supported on 64-pin/144-pin LPC2000 devices with a Boot Loader ID >= 1.6 (you can check your device's ID using Ashlings FlashLPC utility or the Philips FlashISP utility).

Code read protection is enabled by programming the flash address location 0x1FC (User flash sector 0) with value 0x87654321 (2271560481 Decimal). If Read Protection is enabled then the device has to be fully erased (thus disabling Read Protection) before it can be re-programmed. In addition, you will not be able to "connect" to the device via JTAG, hence, erasing must be done using FlashLPC/FlashISP.

Hugh @ http://www.ashling.com/support/lpc2000/

-----Original Message-----
From: Gus [mailto:g...@yahoo.com]
Sent: 16 April 2004 18:51
To: l...@yahoogroups.com
Subject: [***SPAM*** Score/Req: 07.53/05.00] [lpc2000] Code protection

Hello, Does anyone know if FLASH read protect( 0x1FC with value 0x87654321 ) really works? Is there a work arround it to get to memory? Thanks, Gus

Hi Gus, This is a very interesting article on reverse engineering: http://www.cl.cam.ac.uk/~mgk25/sc99-tamper-slides.pdf -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ > -----Original Message----- > From: Gus [mailto:] > Sent: Friday, April 16, 2004 10:51 AM > To: > Subject: [lpc2000] Code protection > Hello, > > Does anyone know if FLASH read protect( 0x1FC with value > 0x87654321 ) really works? > > Is there a work arround it to get to memory? > > Thanks, > > Gus