Yahoo Groups archive

Lpc2000

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

Message

Re: read wrong part id of lpc2136

2006-03-26 by Jayasooriah

Hi Pandurang,

Alternatively you can use my loader available at:

   http://www.cse.unsw.edu.au/~jayas/esdk/sill.html

which reports top ROM (flash) and RAM addresses when you hit the space bar.

I expect the addresses you get will correspond to LPC2131.

The difference between LPC2136 and LPC2131 inside the package is the part 
ID that is stored in the boot parameter block.  The boot loader loads this 
part ID to a special register on startup and this determines how much RAM 
and ROM is enabled.

I too am interested in what you find out.

Jaya

--- In lpc2000@yahoogroups.com, Peter Jakacki <peterjak@...> wrote:
 >
 > It is possible that it is branded incorrectly or that an incorrect ID
 > has been loaded. What you can do is to construct a 32K dummy file to
 > confirm that it does load and then step it up to 64K, 128K and so on
 > until you ascertain the memory size.
 >
 > Once you are sure of your facts you can go back to your supplier to
 > rectify the situation.
 >
 > Either way, let us know what you found out.
 >
 > *Peter*


Pandurang Shinde wrote:
 > thanks Peter for reply, on the chip it is printed as
 >
LPC2136FBD64
 >
S60735.1        04
 >
ZPG0602B
 >
 >                       So i am concludung that is LPC2136 only ,but reading
LPC2131.
 >                       Why this happen.
 >                       Can u suggest any solution for it.
          

[Non-text portions of this message have been removed]

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.