Yahoo Groups archive

Lpc2000

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

Thread

LPC2106 code run problems?

LPC2106 code run problems?

2004-02-25 by tsvetanusunov

Hello,
This is a message which I posted last Friday on Philips 
microcontroller forum. It seems that nobody from Philips is reading 
this forum though as the only one who responded was Leon who observed 
the same problem to one of his boards too, so I cross post here with 
hope that somebody with more information/experience on LPC2106 would 
help:

----QUOTE---
Hi everybody, 

We have designed few development boards for LPC2106. 
The schematics are posted at http://www.olimex.com/dev 
Now we are running lot of 250 pcs LPC-P1 boards and experience the 
following problem: if we program simple blinking led program into 
LPC2106 flash and then disconnect and re-connect power supply in 
random timely manner on 10 % of the boards sometimes LED doesn't 
start to blink i.e. program is not executing, but after several 
plug/unplugs LED start to blink. 
In both cases i.e. program run or program doesn't run oscillator is 
working with same frequency and amplitude i.e. it's not oscillator 
powerup problem. 
It's not reset problem also as even if we hold reset button while 
plug/unplug and release reset button after power supply is stabilized 
i.e. 1 second the code still may not run. 
The power supply is adjusted to be exactly 3.3V with 1% resistors on 
LM1117. 
An interesting thing happens if we decrease input power supply (by 
adding the Z diode i.e. disconnect Z_J jumper) in this case LM1117 
have no enough Vin to make 3.3V and decrease output to 2.5V but here 
is the interesting part: all boards which run the code in randomly 
manner now are working each time if the Vcc is 2.5V! 
As I wrote above this happend to only 10% of the boards all other 90% 
works solid no matter what power supply is. 
I looked desperately on Philips LPC2106 web for technical support 
link to report this issue but there apparently have not such, so I 
decided to post this here in the forum. 

So any ideas? 

Best regards 
Tsvetan
---END QUOTE---

Re: [lpc2000] LPC2106 code run problems?

2004-02-25 by Bill Knight

Random guess.  Power supply sequencing and SCR latchup internal to the
part.  Does the problem occur is both supplies are discharged to ground?

"POSSIBLE" solution, i.e. untried guess.  Backbias a schotty diode across
3.3v and 1.8v supplies so the 3.3v supply will never go below the 1.8v
supply.  No guarantees, but something to try.


Regards
-Bill Knight
R O SoftWare



On Wed, 25 Feb 2004 07:31:31 -0000, tsvetanusunov wrote:

Hello,
This is a message which I posted last Friday on Philips 
microcontroller forum. It seems that nobody from Philips is reading 
this forum though as the only one who responded was Leon who observed 
the same problem to one of his boards too, so I cross post here with 
hope that somebody with more information/experience on LPC2106 would 
help:

----QUOTE---
Hi everybody, 

We have designed few development boards for LPC2106. 
The schematics are posted at http://www.olimex.com/dev 
Now we are running lot of 250 pcs LPC-P1 boards and experience the 
following problem: if we program simple blinking led program into 
LPC2106 flash and then disconnect and re-connect power supply in 
random timely manner on 10 % of the boards sometimes LED doesn't 
start to blink i.e. program is not executing, but after several 
plug/unplugs LED start to blink. 
In both cases i.e. program run or program doesn't run oscillator is 
working with same frequency and amplitude i.e. it's not oscillator 
powerup problem. 
It's not reset problem also as even if we hold reset button while 
plug/unplug and release reset button after power supply is stabilized 
i.e. 1 second the code still may not run. 
The power supply is adjusted to be exactly 3.3V with 1% resistors on 
LM1117. 
An interesting thing happens if we decrease input power supply (by 
adding the Z diode i.e. disconnect Z_J jumper) in this case LM1117 
have no enough Vin to make 3.3V and decrease output to 2.5V but here 
is the interesting part: all boards which run the code in randomly 
manner now are working each time if the Vcc is 2.5V! 
As I wrote above this happend to only 10% of the boards all other 90% 
works solid no matter what power supply is. 
I looked desperately on Philips LPC2106 web for technical support 
link to report this issue but there apparently have not such, so I 
decided to post this here in the forum. 

So any ideas? 

Best regards 
Tsvetan
---END QUOTE---





Yahoo! Groups Links

Re: [lpc2000] LPC2106 code run problems?

2004-02-25 by Robert Adsett

At 06:34 AM 2/25/04 -0600, you wrote:
>Random guess.  Power supply sequencing and SCR latchup internal to the
>part.  Does the problem occur is both supplies are discharged to ground?
>
>"POSSIBLE" solution, i.e. untried guess.  Backbias a schotty diode across
>3.3v and 1.8v supplies so the 3.3v supply will never go below the 1.8v
>supply.  No guarantees, but something to try.

Worth a try although Philips does say there are no sequencing requirements 
on the supplies.  Actually given what they do say on the supplies I suspect 
that the I/O supply (3.3V) has wider tolerances than they admit to.

>----QUOTE---
>Hi everybody,
>
>We have designed few development boards for LPC2106.
>The schematics are posted at http://www.olimex.com/dev
>Now we are running lot of 250 pcs LPC-P1 boards and experience the
>following problem: if we program simple blinking led program into
>LPC2106 flash and then disconnect and re-connect power supply in
>random timely manner on 10 % of the boards sometimes LED doesn't
>start to blink i.e. program is not executing, but after several
>plug/unplugs LED start to blink.
>In both cases i.e. program run or program doesn't run oscillator is
>working with same frequency and amplitude i.e. it's not oscillator
>powerup problem.
>It's not reset problem also as even if we hold reset button while
>plug/unplug and release reset button after power supply is stabilized
>i.e. 1 second the code still may not run.
>The power supply is adjusted to be exactly 3.3V with 1% resistors on
>LM1117.

The 3.3V supply is for I/O so +/- 2% should be more than precise 
enough.    What's happening to the core supply (1.8 V)?

It would be worth putting an oscilloscope on both supplies and (provided it 
still happens) see what the supplies do in both the working and non-working 
cases.

Do you have a power supply monitor driving the reset line?


" 'Freedom' has no meaning of itself.  There are always restrictions,
be they legal, genetic, or physical.  If you don't believe me, try to
chew a radio signal. "

                         Kelvin Throop, III

Re: [lpc2000] LPC2106 code run problems?

2004-02-25 by Igor Janjatovic

> following problem: if we program simple blinking led program into
> LPC2106 flash and then disconnect and re-connect power supply in
> random timely manner on 10 % of the boards sometimes LED doesn't
> start to blink i.e. program is not executing, but after several
> plug/unplugs LED start to blink.

This is just wild guess...

Take one of those "problematic" boards and try this:
Connect three 1N4148 diodes in series from 3.3V to 1.8V.
Also, connect one schottky diode from 1.8V to 3.3V.

Like this:
3.3V    ->|-->|-->|-    1.8V
3.3V    -|<-    1.8V

Keyword is this: Supply Voltage Sequencing and Separation Cautions. Sounds
familiar? No?

OK then... for more detailed explanation of the problem, go to Motorola web
site and download MCF5249UM.pdf document. It is User's Manual for MCF5249
ColdFire processor. Now go to page 409. That's it.

Let us know if this helps since it could be useful for other people who are
using LPC. I'm not using it but everyone else on this group does :))


Regards,
Igor

Re: LPC2106 code run problems?

2004-02-25 by jim_e_dallas

Hello,

You talked about the 3.3V supply and that things worked at 2.5V, 
however, you did not mention what was happening with the 1.8V supply. 
Since the core and memory run from the 1.8V supply, you might want to 
monitor what is going on there to see if it sheds any light onto the 
problem.

Jim

--- In lpc2000@yahoogroups.com, "tsvetanusunov" <tusunov@m...> wrote:
> Hello,
> This is a message which I posted last Friday on Philips 
> microcontroller forum. It seems that nobody from Philips is reading 
> this forum though as the only one who responded was Leon who 
observed 
> the same problem to one of his boards too, so I cross post here 
with 
> hope that somebody with more information/experience on LPC2106 
would 
> help:
> 
> ----QUOTE---
> Hi everybody, 
> 
> We have designed few development boards for LPC2106. 
> The schematics are posted at http://www.olimex.com/dev 
> Now we are running lot of 250 pcs LPC-P1 boards and experience the 
> following problem: if we program simple blinking led program into 
> LPC2106 flash and then disconnect and re-connect power supply in 
> random timely manner on 10 % of the boards sometimes LED doesn't 
> start to blink i.e. program is not executing, but after several 
> plug/unplugs LED start to blink. 
> In both cases i.e. program run or program doesn't run oscillator is 
> working with same frequency and amplitude i.e. it's not oscillator 
> powerup problem. 
> It's not reset problem also as even if we hold reset button while 
> plug/unplug and release reset button after power supply is 
stabilized 
> i.e. 1 second the code still may not run. 
> The power supply is adjusted to be exactly 3.3V with 1% resistors 
on 
> LM1117. 
> An interesting thing happens if we decrease input power supply (by 
> adding the Z diode i.e. disconnect Z_J jumper) in this case LM1117 
> have no enough Vin to make 3.3V and decrease output to 2.5V but 
here 
> is the interesting part: all boards which run the code in randomly 
> manner now are working each time if the Vcc is 2.5V! 
> As I wrote above this happend to only 10% of the boards all other 
90% 
Show quoted textHide quoted text
> works solid no matter what power supply is. 
> I looked desperately on Philips LPC2106 web for technical support 
> link to report this issue but there apparently have not such, so I 
> decided to post this here in the forum. 
> 
> So any ideas? 
> 
> Best regards 
> Tsvetan
> ---END QUOTE---

Re: LPC2106 code run problems?

2004-02-25 by tsvetanusunov

Thanks to everybody who replied, we'll check if the diode schematic 
will improve situation (never liked to make voltage drop with diodes 
as it vary with current consumption)

>You talked about the 3.3V supply and that things worked at 2.5V,
>however, you did not mention what was happening with the 1.8V supply.

1.8V is always solid 1.8V in both cases (code run or code not run), 
the observation that code always run with 2.5V power supply was side 
effect we found during our digging for the reason for the problem.
LM1117 which make +1.8V (core supply) have always sufficient voltage 
drop to ensure proper operation, just the second LM1117 which is used 
for IO +3.3V power supply voltage vary when we include Zener to the 
power supply (i.e. decrease Vin).

Tsvetan

Re: [lpc2000] LPC2106 code run problems?

2004-02-26 by tsvetanusunov

>Random guess. Power supply sequencing and SCR latchup internal to the
part.

Bill, 

this is the exact source of the problem!
adding 47uF capacitor to the +3.3V LM1117 removed the problem, it 
seems that for whatsoever reason on these boards +3.3V rises faster 
than +1.8V and this latch up LPC2106.
On all our future boards we'll put 10uF to +1.8V and 47uF to +3.3V 
regulator thus will ensure some delay on +3.3V.

this explains why these boards started to work when +3.3V vreg was 
working to +2.5V with insufficient Vin - in this case the output of 
+3.3V vreg rises slower and ensure the correct sequencing.

Best regards
Tsvetan

Re: [lpc2000] LPC2106 code run problems?

2004-02-26 by Robert Adsett

At 05:09 PM 2/26/04 +0000, you wrote:
> >Random guess. Power supply sequencing and SCR latchup internal to the
>part.
>
>Bill,
>
>this is the exact source of the problem!
>adding 47uF capacitor to the +3.3V LM1117 removed the problem, it
>seems that for whatsoever reason on these boards +3.3V rises faster
>than +1.8V and this latch up LPC2106.
>On all our future boards we'll put 10uF to +1.8V and 47uF to +3.3V
>regulator thus will ensure some delay on +3.3V.
>
>this explains why these boards started to work when +3.3V vreg was
>working to +2.5V with insufficient Vin - in this case the output of
>+3.3V vreg rises slower and ensure the correct sequencing.
>
>Best regards
>Tsvetan

Definitely report this to Philips.  They claim there are no sequencing 
requirements for the power supplies.

Robert

" 'Freedom' has no meaning of itself.  There are always restrictions,
be they legal, genetic, or physical.  If you don't believe me, try to
chew a radio signal. "

                         Kelvin Throop, III

Re: [lpc2000] LPC2106 code run problems?

2004-02-26 by Alaric B Snell

tsvetanusunov wrote:
>>Random guess. Power supply sequencing and SCR latchup internal to the
> 
> part.
> 
> Bill, 
> 
> this is the exact source of the problem!
> adding 47uF capacitor to the +3.3V LM1117 removed the problem, it 
> seems that for whatsoever reason on these boards +3.3V rises faster 
> than +1.8V and this latch up LPC2106.
> On all our future boards we'll put 10uF to +1.8V and 47uF to +3.3V 
> regulator thus will ensure some delay on +3.3V.

*My* investigations of my strange interrupt handling problems are now 
looking into the high levels of noise I see on the /RST pin when lots of 
serial I/O is happening :-)

> Best regards
> Tsvetan

ABS

RE: [lpc2000] LPC2106 code run problems?

2004-02-26 by Hugh O'Keeffe

Bill/Tsvetan:
This is really impressive work/analysis and demonstrates the power of
this group. I think we all need to look at our schematics ;-) . Please
keep us all posted on any responses from Philips.
 



Hugh @  <http://www.ashling.com/support/lpc2100/>
http://www.ashling.com/support/lpc2100/ 
Show quoted textHide quoted text
-----Original Message-----
From: Alaric B Snell [mailto:alaric@...] 
Sent: 26 February 2004 17:22
To: lpc2000@yahoogroups.com
Subject: Re: [lpc2000] LPC2106 code run problems?


tsvetanusunov wrote:
>>Random guess. Power supply sequencing and SCR latchup internal to the
> 
> part.
> 
> Bill, 
> 
> this is the exact source of the problem!
> adding 47uF capacitor to the +3.3V LM1117 removed the problem, it 
> seems that for whatsoever reason on these boards +3.3V rises faster 
> than +1.8V and this latch up LPC2106.
> On all our future boards we'll put 10uF to +1.8V and 47uF to +3.3V 
> regulator thus will ensure some delay on +3.3V.

*My* investigations of my strange interrupt handling problems are now 
looking into the high levels of noise I see on the /RST pin when lots of

serial I/O is happening :-)

> Best regards
> Tsvetan

ABS



  _____  

Yahoo! Groups Links


*	To visit your group on the web, go to:
http://groups.yahoo.com/group/lpc2000/
  

*	To unsubscribe from this group, send an email to:
lpc2000-unsubscribe@yahoogroups.com
<mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe> 
  

*	Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> .

Re: [lpc2000] LPC2106 code run problems?

2004-02-26 by Joseph Tapay

Philips is recommending CAPFREE LDO-s (SA57000-33D and SA57017-18D) . Could
this sequencing problem the reason?
Is it possible to run LDO power supplies with no caps?
(TI, National etc. all recommend bypass caps, Philips does not)
j
----- Original Message ----- 
Show quoted textHide quoted text
From: "tsvetanusunov" <tusunov@...>
To: <lpc2000@yahoogroups.com>
Sent: Thursday, February 26, 2004 12:09 PM
Subject: Re: [lpc2000] LPC2106 code run problems?


> >Random guess. Power supply sequencing and SCR latchup internal to the
> part.
>
> Bill,
>
> this is the exact source of the problem!
> adding 47uF capacitor to the +3.3V LM1117 removed the problem, it
> seems that for whatsoever reason on these boards +3.3V rises faster
> than +1.8V and this latch up LPC2106.
> On all our future boards we'll put 10uF to +1.8V and 47uF to +3.3V
> regulator thus will ensure some delay on +3.3V.
>
> this explains why these boards started to work when +3.3V vreg was
> working to +2.5V with insufficient Vin - in this case the output of
> +3.3V vreg rises slower and ensure the correct sequencing.
>
> Best regards
> Tsvetan
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>

Re: [lpc2000] LPC2106 code run problems?

2004-02-26 by Robert Adsett

At 05:09 PM 2/26/04 +0000, you wrote:
> >Random guess. Power supply sequencing and SCR latchup internal to the
>part.
>
>Bill,
>
>this is the exact source of the problem!
>adding 47uF capacitor to the +3.3V LM1117 removed the problem, it
>seems that for whatsoever reason on these boards +3.3V rises faster
>than +1.8V and this latch up LPC2106.
>On all our future boards we'll put 10uF to +1.8V and 47uF to +3.3V
>regulator thus will ensure some delay on +3.3V.
>
>this explains why these boards started to work when +3.3V vreg was
>working to +2.5V with insufficient Vin - in this case the output of
>+3.3V vreg rises slower and ensure the correct sequencing.

A quick question.  What is the rise time difference in going from a 10uF to 
a 47uF cap?


" 'Freedom' has no meaning of itself.  There are always restrictions,
be they legal, genetic, or physical.  If you don't believe me, try to
chew a radio signal. "

                         Kelvin Throop, III

Re: [lpc2000] LPC2106 code run problems?

2004-02-26 by Robert Adsett

At 05:09 PM 2/26/04 +0000, you wrote:
> >Random guess. Power supply sequencing and SCR latchup internal to the
>part.
>
>Bill,
>
>this is the exact source of the problem!
>adding 47uF capacitor to the +3.3V LM1117 removed the problem, it
>seems that for whatsoever reason on these boards +3.3V rises faster
>than +1.8V and this latch up LPC2106.
>On all our future boards we'll put 10uF to +1.8V and 47uF to +3.3V
>regulator thus will ensure some delay on +3.3V.
>
>this explains why these boards started to work when +3.3V vreg was
>working to +2.5V with insufficient Vin - in this case the output of
>+3.3V vreg rises slower and ensure the correct sequencing.

It may not be that simple.  The fact that Philips has been claiming there 
are no sequencing requirements was bothering me so I just did a simple 
experiment.  I disconnected the 1.8V supply from the micro and powered it 
up.  After the other supplies had stabilized I reconnected the 1.8V supply 
by hand.  The micro started w/o a problem.  I've got to refine the setup a 
little more but straightforward sequencing is not at fault.


Robert

" 'Freedom' has no meaning of itself.  There are always restrictions,
be they legal, genetic, or physical.  If you don't believe me, try to
chew a radio signal. "

                         Kelvin Throop, III

Re: [lpc2000] LPC2106 code run problems?

2004-02-27 by tsvetanusunov

>It may not be that simple. The fact that Philips has been claiming 
>there are no sequencing requirements was bothering me so I just 
>did a simple experiment. I disconnected the 1.8V supply from the 
>micro and powered it up. After the other supplies had stabilized I 
>reconnected the 1.8V supply by hand. The micro started w/o a 
>problem. I've got to refine the setup a little more but 
>straightforward sequencing is not at fault.

indeed it may be not that simple, I believe in our case Vreg rise 
time difference is matter of milliseconds.
we didn't measure rise times on +1.8 +3.3V with 10uF/47uF but this 
just solved the problem
we'll do some more experiments
Tsvetan

Re: [lpc2000] LPC2106 code run problems?

2004-02-27 by Bill Knight

On Fri, 27 Feb 2004 05:45:27 -0000, tsvetanusunov wrote:

>It may not be that simple. The fact that Philips has been claiming 
>there are no sequencing requirements was bothering me so I just 
>did a simple experiment. I disconnected the 1.8V supply from the 
>micro and powered it up. After the other supplies had stabilized I 
>reconnected the 1.8V supply by hand. The micro started w/o a 
>problem. I've got to refine the setup a little more but 
>straightforward sequencing is not at fault.

indeed it may be not that simple, I believe in our case Vreg rise 
time difference is matter of milliseconds.
we didn't measure rise times on +1.8 +3.3V with 10uF/47uF but this 
just solved the problem
we'll do some more experiments
Tsvetan
=================================================================
Yes.  dv/dt is a known cause for false triggering of scr's.
Another problem we had with some of the Atmel AT91's is a poor
reset of the nTRST line which caused the JTAG chain to go active
and halt the processor core.  It showed up as 3 memory accesses
to fill the pipeline, then no bus activity at all.  I have no idea
if any of this applies, just passing on observations that might
apply.

-Bill

Re: [lpc2000] LPC2106 code run problems?

2004-02-28 by Robert Adsett

At 06:47 AM 2/27/04 -0600, you wrote:
>On Fri, 27 Feb 2004 05:45:27 -0000, tsvetanusunov wrote:
>
> >It may not be that simple. The fact that Philips has been claiming
> >there are no sequencing requirements was bothering me so I just
> >did a simple experiment. I disconnected the 1.8V supply from the
> >micro and powered it up. After the other supplies had stabilized I
> >reconnected the 1.8V supply by hand. The micro started w/o a
> >problem. I've got to refine the setup a little more but
> >straightforward sequencing is not at fault.
>
>indeed it may be not that simple, I believe in our case Vreg rise
>time difference is matter of milliseconds.
>we didn't measure rise times on +1.8 +3.3V with 10uF/47uF but this
>just solved the problem
>we'll do some more experiments
>Tsvetan
>=================================================================
>Yes.  dv/dt is a known cause for false triggering of scr's.
>Another problem we had with some of the Atmel AT91's is a poor
>reset of the nTRST line which caused the JTAG chain to go active
>and halt the processor core.  It showed up as 3 memory accesses
>to fill the pipeline, then no bus activity at all.  I have no idea
>if any of this applies, just passing on observations that might
>apply.
>
>-Bill

Since if there is a sequencing problem it will have an effect on all of us 
I figured this was worth a little effort to gather some information if it 
was possible.  So I did in fact refine my setup here.  I've bodgered a 
prototype board and it now has a couple of switches taped to it.

The bad news is I can't duplicate the problem.  I do, however, have some 
data that Tsvetvan may be able to use together with what he has to narrow 
down the search.  Maybe.

I put switches on the 1.8V line and the power monitor reset line from the 
1.8V monitor (monitors were left on the 3.3V and 5V lines).  I ran the 
following tests (a minimum 100 cycles each) w/o seeing any lockups.

1- Disconnect/connect main power
2- Disconnect/connect main power w 1.8V monitor out disabled.
3- Use switch to disconnect/connect 1.8V (3.3V and 5v on continuously)
4- Use switch to disconnect/connect 1.8V (3.3V and 5v on continuously), 
1.8V monitor out disabled.
5- Repeat test 1 and 2 with a weaker pullup on the reset line.

I also ran test 1 on a Nohau evaluation board I have.

My test used the serial port rather than a blinky LED and sent an audible 
BEL so I could do the switching with all of my visual attention and just 
listen for the tone.

Both boards (mine and Nohau's) are 4 layer boards with linear supplies.  I 
have power monitor circuitry monitoring all the power lines(5v, 3.3V and 
1.8v) with 4K7 pullup to 5V (I don't trust RC reset circuits to be 
reliable).  Nohau appears to have a simple pull-up (3+ K effective) to 
3.3V.  Strangely I can't find a cap on the Nohau circuit, I suspect I've 
just overlooked it but the CD they sent containing the schematic is no 
longer readable (it appears to have slowly deteriorated). Maybe someone 
else can check for it?

Some rise times

Nohau eval board (2106)
reset - ~320uS
1.8V - ~1200uS (to stable) ~110uS rise
3.3V - ~350uS (to stable) ~230uS rise

My board (2104)

reset - ~1.1uS (That's with the weaker 15K pullup, the stronger pullup is 
probably a little faster).  It's also well after the monitor supplies have 
stabilized since the reset is help for mS.

1.8V - ~620uS (to stable) ~390 rise
3.3V - ~560uS (to stable) ~470 rise

With switch on the 1.8V line
1.8V - ~27uS (to stable) ~12uS rise

Tsvetvan, if your power rise times are in fact in the multiple mS range 
that would suggest they are quite slow in comparison.  It might be 
interesting to know how clean the reset line was on startup.

Of course I may just be (un)lucky here but I also had to replace the micro 
a couple of time during this (my errors while modifying the board) and none 
of the ones I used showed a problem.

I hope this is of some help Tsvetvan.  I'm eager to hear what you find.

Robert

" 'Freedom' has no meaning of itself.  There are always restrictions,
be they legal, genetic, or physical.  If you don't believe me, try to
chew a radio signal. "

                         Kelvin Throop, III

Re: [lpc2000] LPC2106 code run problems?

2004-02-28 by Robert Adsett

>reset - ~1.1uS (That's with the weaker 15K pullup, the stronger pullup is
>probably a little faster).  It's also well after the monitor supplies have
>stabilized since the reset is help for mS.

Umm, that should be held for mS.

" 'Freedom' has no meaning of itself.  There are always restrictions,
be they legal, genetic, or physical.  If you don't believe me, try to
chew a radio signal. "

                         Kelvin Throop, III

Re: LPC2106 code run problems? (from Alaric B Snell)

2004-07-12 by embyy27

--- In lpc2000@yahoogroups.com, Alaric B Snell <alaric@a...> wrote:
> 
> *My* investigations of my strange interrupt handling problems are 
now 
> looking into the high levels of noise I see on the /RST pin when 
lots of 
> serial I/O is happening :-)
> 
> ABS

Did you ever resolve this problem?  What did you find?

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.