Yahoo Groups archive

Lpc2000

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

Message

Re: CRP (Code Read Protection) investigation by stepping through the boot loader

2006-04-23 by unity0724

Hi,
It does not matter whether there are any differences between 
LPC2103 and LPC2124/3x/4x.   Important point is I did NOT need 
to switch parts if there were NO such tons of CRP posts at all.

OK,   Now I remember you are the one who claims CRP of  
LPC2124/3x/4x could be broken by:
- External JTAG breaking in before Booloader could disables the
  JTAG port fast enough (Some 30-70 clocks thing)..??
- Philips planted a Trojan horse inside the bootloader..??
- Crashing of bootloader by some undocumented ISP commands..??

Since you are so expert in LPC21xx, could you help to disassemble
few lines of the LPC2103 startup code??
(I'm some guy who could only write a few lines of C-codes for
simple 8-bit applications.    No capability of reverse engineering 
but know how to do few DWords code dump to serial port)
Give me the address of code segment to be dumped to UART0
if you want to disassemble.

Regards



--- In lpc2000@yahoogroups.com, "jayasooriah" <jayasooriah@...> 
wrote:
>
> --- In lpc2000@yahoogroups.com, "unity0724" <unity0724@> wrote:
> 
> > I switched over to LPC2103, after being frightened by those tons
> > of questions/posts on the LPC2124/3x/4x's CRP.
> 
> How is LPC2103 is any different in relation to CRP?  I had a look 
at
> the user manual and could not find anything that suggests CRP
> implementation is any different.
> 
> I did find one reference to Code Security Protection Register 
(CSPR)
> as a read-only register at 0xe01fc180 -- see page 16 of user 
manual. 
> There seems to be no other information about this register 
elsewhere
> though.
> 
> You may want to look at the startup code in your boot loader 
either by
> disassembly or using debugging method to see if it is any 
different.
> 
> 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.