Yahoo Groups archive

Lpc2000

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

Thread

Overclocking

Overclocking

2003-12-06 by Leon Heller

Here is a note from someone about overclocking the LPC210x:

http://runryder.com/helicopter/t66907p2/

He has had one running at 120 MHz.

Leon
--
Leon Heller, G1HSM
Email: aqzf13@...
http://www.geocities.com/leon_heller

Re: Overclocking, risky, risky

2003-12-08 by lpc2100_fan

Hi,

we also did some speed testing. From internal RAM (room temperature)
we got the first suspicious behavior between 90 and 100 MHz. I guess
this is very good performance. Nevertheless, if the device is at its
lowest voltage and higest temperature (this is worst case), it is
probably not a lot faster than the specification. We decided NOT to
overclock because we would be on our own in case there is any
misbehavior of the device and this is my recommendation for everybody
who wants to develop a serious application with the 21xx.

Also for the flash block, the MAMTIM has to be increased if running at
a faster speed. The MAMTIM determines the delay for the initial flash
access after a branch.

The device seems to run faster than specified but that should be the
case under lab conditions anyhow, otherwise it would fail miserably
under worst case conditions. 

Cheers, Bob


--- In lpc2100@yahoogroups.com, "Leon Heller" <leon_heller@h...> wrote:
Show quoted textHide quoted text
> Here is a note from someone about overclocking the LPC210x:
> 
> http://runryder.com/helicopter/t66907p2/
> 
> He has had one running at 120 MHz.
> 
> Leon
> --
> Leon Heller, G1HSM
> Email: aqzf13@d...
> http://www.geocities.com/leon_heller

Re: [lpc2100] Re: Overclocking, risky, risky

2003-12-08 by microbit

Hi Bob,
> lowest voltage and higest temperature (this is worst case), it is
> probably not a lot faster than the specification. We decided NOT to
> overclock because we would be on our own in case there is any
> misbehavior of the device and this is my recommendation for everybody
> who wants to develop a serious application with the 21xx.
This is a very WISE decision and also sound advice Bob !
Surely you have been in the position where I have been on many occasions. :
You run into problems with (officially) "unknown" silicon problems.
If anything is *slightly" out of characterisation, they JUMP on the chance for an excuse.
(If all excuses are exhausted, it falls back to the good old "ESD" damage story, pathetic really)
You can always tell when you submit a concise report describing the silicon problem.
You suddenly get a stream of *seemingly* off-topic or dumb questions from the vendor.
That's when you know for sure you've run into a silicon snag.
Once a US RF silicon vendor had the audacity to even go to the extent in their dumb cover-up to
suggest that my "problem" was caused by it being summer in Australia, and that I had to constantly
keep spraying freezer spray on the chip.
Can you believe that ???
Or the good old back-dated Errata sheets !!!!!!!!!!!!! (ie. > ;2 years :-)
-- Kris

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.