Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Protection

2004-03-03 by philips_apps

Hi Kris,

good news and bad news about protection. Let's get the bad news out of
the way. The LPC2104/5/6 can not be upgraded with protection as the
design is done :-( 

Good news:
A block that is handling pin assignments is used in all the 64-pin and
144-pin devices for the protection feature. All 144-pin devices that
are coming from volume production (if you have them already they are
still samples, volume production devices are in the fab right now)
will have the protection feature.

64-pin devices can be protected but what is out there in the field
today does not have the protection (e.g. parts on the evaluation
boards from Keil). Will keep this forum posted as soon as the
protection is implemented on the 64-pin devices.

Regards, Robert

--- In lpc2000@yahoogroups.com, "microbit" <microbit@c...> wrote:
> Hi Robert,
> 
> > The protection (disabling JTAG) happens first thing at power up no
> > matter if protection is enabled or not.
> > Then the bootloader checks whether the protection is supposed to be
> > enabled and enables the JTAG interface if the protection pattern is
> > not found in the corresponding memory location.
> >
> > This is a preliminary wording of future documentation:
> 
> That makes sense, simple and nifty !
> Can you confirm wihich devices onward this will be implemented on ?
> 
> > Yes you will see more than 16k (32k to begin with) late fall this
year.
> 
> Great news.
> We're kinda spoiled with LPC2106's 64 K, and it makes for really fast
> debugging
> compared to Flashing.
> My main application, the BASIC interpeter with RF frontend ideally
has 32 -
> 64 K
> RAM on-chip. To keep PCB cost low, it's much better not to have busses
> around
> vis-a-vis EMI. It's a bugger to keep it out of IF strips in transceivers
> unless you
> can throw away several layers like it's out of fashion anyway.
> 
> 
> B regards,
> Kris

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.