Yahoo Groups archive

Lpc2000

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

Message

Re: FLASH Security

2005-12-19 by jayasooriah

--- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@a...> wrote:
>
> At 10:42 PM 12/18/05 +0000, jayasooriah wrote:
> That's somewhat intriguing.  It's the first I've heard of any hint
at all 
> that the parts can be programmed via a parallel programming algorithm 
> rather than only via JTAG and serial port.  In fact given what has been 
> revealed of the internals I would have said it was unlikely to be 
> possible.  Have you any Philips references?  I can find no mention
on their 
> web site, indeed the closest I could find was a table that indicated
that 
> parallel programming was not an option for any of the LPC family.
> 
> Robert

The Product Overview Edition 08/2005 says otherwise.  It is claimed to
have been prepared by Philips Microcontroller Customer Technical
Support Group.

Though I cannot find any parallel programming information for LPC2105
in data sheet or user manual, Philips has confirmed to me (in email)
that these parts can be parallel programmed.

This prompted me to searched for parallel programming information for
LPC series and found the product overview chart.

I am not sure about others, but from what I learnt in the last couple
of weeks in relation to: a) on-chip flash programming algorithm; b)
parallel programming info; c) errata sheets for LPC2105; and d) source
for the supplied boot loader code, it is now pretty clear to me why
Philips has chosen to provide boot loader code so that they do not
*have* to release the kind of information I discovered.

However, the issue relating to code security is a pressing one and I
cannot continue working on prototype designes for clients unless I
know for sure that the embedded code is secure from preying eyes.

So far one customer has already asked for LPC2105 to be replaced with
equivalent OKI replacement because of problems flash programming and
boot loader requirements.

Jaya

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.