--- In m..., Kipton Moravec wrote:
>
> ... when I tried to connect to a running system using
> the IAR toolset. My only option was to reload the software through the
> debugger....
>
Try click at [project] -> [options]
under [Catagory], select [FET Debugger]
under the Tab [setup]:[Download control]
check both [Verify download] and [Suppress download]
I think this will let you compare what you just compiled with
what is currently in the Flash. It will give you warnings if
they are different.
Lock up through power cycling.
Started by ●February 20, 2007
Reply by ●February 21, 20072007-02-21
Reply by ●February 21, 20072007-02-21
TI says that if the Flash is erased and programmed properly, it will
last 100 years at 25 degrees C.
To store a MSP430 at 150 degree C will not damage it. But the properly
erased and programmed Flash last only a month or two.
Any what about not properly erased and programmed devices?
last 100 years at 25 degrees C.
To store a MSP430 at 150 degree C will not damage it. But the properly
erased and programmed Flash last only a month or two.
Any what about not properly erased and programmed devices?
Reply by ●February 21, 20072007-02-21
>When I cycle power it stays locked up, until I
>reload the software using the IAR tool set.
With as much capacitance as you have on the board, are you sure it really
powers down when you cycle power? The MSP430 draws such little power, and
you have so much bulk capacitance, it may not actually be powering down and
back up, and therefore not going through reset. Have you tried toggling the
reset line to see if that pulls it out?
If it always seems to fail after a certain time interval, you likely have
some kind of problem with your code. If the failure time is more random,
you may have noise problems. We have seen noise kill the oscillator
completely and only a power down would restart it. It seems the MSP430 is
particularly sensitive to noise, more than I have seen on other micros,
especially when using a 32 KHz crystal for the clock.
Lou
_________________________________________________________________
Want a degree but can't afford to quit? Top school degrees online - in as
fast as 1 year
http://forms.nextag.com/goto.jsp?url=/serv/main/buyer/education.jsp?doSearch=n&tm=y&searchcation_text_links_88_h288c&s@79&pQ16
>reload the software using the IAR tool set.
With as much capacitance as you have on the board, are you sure it really
powers down when you cycle power? The MSP430 draws such little power, and
you have so much bulk capacitance, it may not actually be powering down and
back up, and therefore not going through reset. Have you tried toggling the
reset line to see if that pulls it out?
If it always seems to fail after a certain time interval, you likely have
some kind of problem with your code. If the failure time is more random,
you may have noise problems. We have seen noise kill the oscillator
completely and only a power down would restart it. It seems the MSP430 is
particularly sensitive to noise, more than I have seen on other micros,
especially when using a 32 KHz crystal for the clock.
Lou
_________________________________________________________________
Want a degree but can't afford to quit? Top school degrees online - in as
fast as 1 year
http://forms.nextag.com/goto.jsp?url=/serv/main/buyer/education.jsp?doSearch=n&tm=y&searchcation_text_links_88_h288c&s@79&pQ16
Reply by ●February 21, 20072007-02-21
On Wed, 2007-02-21 at 07:39 -0600, Lou C wrote:
> >When I cycle power it stays locked up, until I
> >reload the software using the IAR tool set.
>
> With as much capacitance as you have on the board, are you sure it really
> powers down when you cycle power? The MSP430 draws such little power, and
> you have so much bulk capacitance, it may not actually be powering down and
> back up, and therefore not going through reset. Have you tried toggling the
> reset line to see if that pulls it out?
We considered that, and had it powered down for over 1 hour and it still
did not come up right. In addition, when it fails, the LED fails on,
which is drawing about 8 mA. It goes out in about 6-7 seconds.
>
> If it always seems to fail after a certain time interval, you likely have
> some kind of problem with your code. If the failure time is more random,
> you may have noise problems. We have seen noise kill the oscillator
> completely and only a power down would restart it. It seems the MSP430 is
> particularly sensitive to noise, more than I have seen on other micros,
> especially when using a 32 KHz crystal for the clock.
>
That was one reason I had extra capacitance was to minimize the noise on
the power and ground planes. The clock driving the timer is indeed a 32
KHz crystal but the power down will not get things going. Next time it
fails I will check to see if the crystal is still oscillating.
Thanks,
Kip
> Lou
>
> _________________________________________________________________
> Want a degree but can't afford to quit? Top school degrees online - in as
> fast as 1 year
> http://forms.nextag.com/goto.jsp?url=/serv/main/buyer/education.jsp?doSearch=n&tm=y&searchcation_text_links_88_h288c&s@79&pQ16
>
>
> Yahoo! Groups Links
--
Kipton Moravec
> >When I cycle power it stays locked up, until I
> >reload the software using the IAR tool set.
>
> With as much capacitance as you have on the board, are you sure it really
> powers down when you cycle power? The MSP430 draws such little power, and
> you have so much bulk capacitance, it may not actually be powering down and
> back up, and therefore not going through reset. Have you tried toggling the
> reset line to see if that pulls it out?
We considered that, and had it powered down for over 1 hour and it still
did not come up right. In addition, when it fails, the LED fails on,
which is drawing about 8 mA. It goes out in about 6-7 seconds.
>
> If it always seems to fail after a certain time interval, you likely have
> some kind of problem with your code. If the failure time is more random,
> you may have noise problems. We have seen noise kill the oscillator
> completely and only a power down would restart it. It seems the MSP430 is
> particularly sensitive to noise, more than I have seen on other micros,
> especially when using a 32 KHz crystal for the clock.
>
That was one reason I had extra capacitance was to minimize the noise on
the power and ground planes. The clock driving the timer is indeed a 32
KHz crystal but the power down will not get things going. Next time it
fails I will check to see if the crystal is still oscillating.
Thanks,
Kip
> Lou
>
> _________________________________________________________________
> Want a degree but can't afford to quit? Top school degrees online - in as
> fast as 1 year
> http://forms.nextag.com/goto.jsp?url=/serv/main/buyer/education.jsp?doSearch=n&tm=y&searchcation_text_links_88_h288c&s@79&pQ16
>
>
> Yahoo! Groups Links
--
Kipton Moravec
Reply by ●February 21, 20072007-02-21
--- In m..., Kipton Moravec wrote:
>
> On Wed, 2007-02-21 at 07:39 -0600, Lou C wrote:
> > >When I cycle power it stays locked up, until I
> > >reload the software using the IAR tool set.
> >
> > With as much capacitance as you have on the board, are you sure it
really
> > powers down when you cycle power? The MSP430 draws such little
power, and
> > you have so much bulk capacitance, it may not actually be powering
down and
> > back up, and therefore not going through reset. Have you tried
toggling the
> > reset line to see if that pulls it out?
>
> We considered that, and had it powered down for over 1 hour and it still
> did not come up right. In addition, when it fails, the LED fails on,
> which is drawing about 8 mA. It goes out in about 6-7 seconds.
At the point the LED goes out, the forward voltage may still be high
enough to cause problems in the processor - it is at least .7V,
correct? Are you sure that zero transistors inside the MSP430 will
operate at .7V?
You need to ground your power supply rail (with power unplugged) with
that much capacitance.
1 hour isn't going to do it when your processor is capable of having
transistors inside doing stuff on a few dozen microamps.
Paul
>
> On Wed, 2007-02-21 at 07:39 -0600, Lou C wrote:
> > >When I cycle power it stays locked up, until I
> > >reload the software using the IAR tool set.
> >
> > With as much capacitance as you have on the board, are you sure it
really
> > powers down when you cycle power? The MSP430 draws such little
power, and
> > you have so much bulk capacitance, it may not actually be powering
down and
> > back up, and therefore not going through reset. Have you tried
toggling the
> > reset line to see if that pulls it out?
>
> We considered that, and had it powered down for over 1 hour and it still
> did not come up right. In addition, when it fails, the LED fails on,
> which is drawing about 8 mA. It goes out in about 6-7 seconds.
At the point the LED goes out, the forward voltage may still be high
enough to cause problems in the processor - it is at least .7V,
correct? Are you sure that zero transistors inside the MSP430 will
operate at .7V?
You need to ground your power supply rail (with power unplugged) with
that much capacitance.
1 hour isn't going to do it when your processor is capable of having
transistors inside doing stuff on a few dozen microamps.
Paul
Reply by ●February 21, 20072007-02-21
________________________________
From: m... [mailto:m...] On Behalf
Of Kipton Moravec
Sent: Wednesday, February 21, 2007 9:48 AM
To: m...
Subject: RE: [msp430] Lock up through power cycling.
On Wed, 2007-02-21 at 07:39 -0600, Lou C wrote:
> >When I cycle power it stays locked up, until I
> >reload the software using the IAR tool set.
>
> With as much capacitance as you have on the board, are you sure it
really
> powers down when you cycle power? The MSP430 draws such little power,
and
> you have so much bulk capacitance, it may not actually be powering
down and
> back up, and therefore not going through reset. Have you tried
toggling the
> reset line to see if that pulls it out?
We considered that, and had it powered down for over 1 hour and it still
did not come up right. In addition, when it fails, the LED fails on,
which is drawing about 8 mA. It goes out in about 6-7 seconds.
>
> If it always seems to fail after a certain time interval, you likely
have
> some kind of problem with your code. If the failure time is more
random,
> you may have noise problems. We have seen noise kill the oscillator
> completely and only a power down would restart it. It seems the MSP430
is
> particularly sensitive to noise, more than I have seen on other
micros,
> especially when using a 32 KHz crystal for the clock.
>
That was one reason I had extra capacitance was to minimize the noise on
the power and ground planes. The clock driving the timer is indeed a 32
KHz crystal but the power down will not get things going. Next time it
fails I will check to see if the crystal is still oscillating.
The large caps on the power line won't do much for high frequency noise.
If you are looking to get rid of high frequency stuff throw some small
caps in there. Pay careful attention to trace lengths here. Trace
inductance can effectively remove the caps from the circuit if you are
not very careful. Putting a pi filter on the line can help as well.
>From your description I would be surprised if it was a power problem.
Now, granted, I've been surprised before but I'd focus my efforts on
that 32KHz crystal and the flash write routines. TI has an app note on
checking the stability of 32K crystals where you mess with the
equivalent series resistance. Might want to dig into there website and
take a look there. Its relatively new and would have saved us months of
headaches. Just to eliminate a possibility, is it possible to power the
circuit through a known good source to eliminate the issue completely?
Maybe skip the switcher and feed 12V into a 3.3 regulator?
Dan M
Thanks,
Kip
> Lou
>
> __________________________________________________________
> Want a degree but can't afford to quit? Top school degrees online - in
as
> fast as 1 year
>
http://forms.nextag.com/goto.jsp?url=/serv/main/buyer/education.jsp?doSe
arch=n&tm=y&searchcation_text_links_88_h288c&s@79&pQ16
earch=n&tm=y&searchcation_text_links_88_h288c&s@79&pQ16>
> Yahoo! Groups Links
--
Kipton Moravec >
From: m... [mailto:m...] On Behalf
Of Kipton Moravec
Sent: Wednesday, February 21, 2007 9:48 AM
To: m...
Subject: RE: [msp430] Lock up through power cycling.
On Wed, 2007-02-21 at 07:39 -0600, Lou C wrote:
> >When I cycle power it stays locked up, until I
> >reload the software using the IAR tool set.
>
> With as much capacitance as you have on the board, are you sure it
really
> powers down when you cycle power? The MSP430 draws such little power,
and
> you have so much bulk capacitance, it may not actually be powering
down and
> back up, and therefore not going through reset. Have you tried
toggling the
> reset line to see if that pulls it out?
We considered that, and had it powered down for over 1 hour and it still
did not come up right. In addition, when it fails, the LED fails on,
which is drawing about 8 mA. It goes out in about 6-7 seconds.
>
> If it always seems to fail after a certain time interval, you likely
have
> some kind of problem with your code. If the failure time is more
random,
> you may have noise problems. We have seen noise kill the oscillator
> completely and only a power down would restart it. It seems the MSP430
is
> particularly sensitive to noise, more than I have seen on other
micros,
> especially when using a 32 KHz crystal for the clock.
>
That was one reason I had extra capacitance was to minimize the noise on
the power and ground planes. The clock driving the timer is indeed a 32
KHz crystal but the power down will not get things going. Next time it
fails I will check to see if the crystal is still oscillating.
The large caps on the power line won't do much for high frequency noise.
If you are looking to get rid of high frequency stuff throw some small
caps in there. Pay careful attention to trace lengths here. Trace
inductance can effectively remove the caps from the circuit if you are
not very careful. Putting a pi filter on the line can help as well.
>From your description I would be surprised if it was a power problem.
Now, granted, I've been surprised before but I'd focus my efforts on
that 32KHz crystal and the flash write routines. TI has an app note on
checking the stability of 32K crystals where you mess with the
equivalent series resistance. Might want to dig into there website and
take a look there. Its relatively new and would have saved us months of
headaches. Just to eliminate a possibility, is it possible to power the
circuit through a known good source to eliminate the issue completely?
Maybe skip the switcher and feed 12V into a 3.3 regulator?
Dan M
Thanks,
Kip
> Lou
>
> __________________________________________________________
> Want a degree but can't afford to quit? Top school degrees online - in
as
> fast as 1 year
>
http://forms.nextag.com/goto.jsp?url=/serv/main/buyer/education.jsp?doSe
arch=n&tm=y&searchcation_text_links_88_h288c&s@79&pQ16
earch=n&tm=y&searchcation_text_links_88_h288c&s@79&pQ16>
> Yahoo! Groups Links
--
Kipton Moravec >
Reply by ●February 21, 20072007-02-21
The device is not getting warm or cold at all. Everything is room
temperature, which is closer to 23 deg C.
I am using the FET debugger and the voltage seems steady at 3.3V with
the debugger plugged in, so I doubt it is not programmed correctly.
Thanks for the suggestion,
Kip
On Wed, 2007-02-21 at 04:43 +0000, old_cow_yellow wrote:
> TI says that if the Flash is erased and programmed properly, it will
> last 100 years at 25 degrees C.
>
> To store a MSP430 at 150 degree C will not damage it. But the properly
> erased and programmed Flash last only a month or two.
>
> Any what about not properly erased and programmed devices?
>
> Yahoo! Groups Links
--
Kipton Moravec
temperature, which is closer to 23 deg C.
I am using the FET debugger and the voltage seems steady at 3.3V with
the debugger plugged in, so I doubt it is not programmed correctly.
Thanks for the suggestion,
Kip
On Wed, 2007-02-21 at 04:43 +0000, old_cow_yellow wrote:
> TI says that if the Flash is erased and programmed properly, it will
> last 100 years at 25 degrees C.
>
> To store a MSP430 at 150 degree C will not damage it. But the properly
> erased and programmed Flash last only a month or two.
>
> Any what about not properly erased and programmed devices?
>
> Yahoo! Groups Links
--
Kipton Moravec
Reply by ●February 21, 20072007-02-21
Below certain voltage most of semiconductor based circuits reduces the current
drawing to several microAmps.
The LED will turn off long time before this voltage is reached. So, you may keep some MSP based circuits off
power for longer than one hour and it does still with enough voltage to have the 32KHz clock working.
To be sure you have zero volts you must short-circuit the MSP's VCC to GND after turning power off, of course.
You can use a tweezer touching both sides of a SMD decoupling capacitor, for example.
Use a voltimeter to check the VCC value after turning power off. You may have another hiden power source in
your circuit, too. JTAG cables like to play this way quite often.
Also, often you don't need large capacitors for filtering the VCC.
Capacitors in the supply rail must be fast and their values must supply current only for short periods while
current comming from power regulator travels through the impedance of the circuit.
Normally you don't need more than 10uF Tantalum for VCC in parallel with a 10nF multilayer chip capacitor.
-Augusto
---------- Cabelho original -----------
De: m...
Para: m...
Cia:
Data: Wed, 21 Feb 2007 09:47:53 -0600
Assunto: RE: [msp430] Lock up through power cycling.
> On Wed, 2007-02-21 at 07:39 -0600, Lou C wrote:
> > >When I cycle power it stays locked up, until I
> > >reload the software using the IAR tool set.
> >
> > With as much capacitance as you have on the board, are you sure it really
> > powers down when you cycle power? The MSP430 draws such little power, and
> > you have so much bulk capacitance, it may not actually be powering down and
> > back up, and therefore not going through reset. Have you tried toggling the
> > reset line to see if that pulls it out?
>
> We considered that, and had it powered down for over 1 hour and it still
> did not come up right. In addition, when it fails, the LED fails on,
> which is drawing about 8 mA. It goes out in about 6-7 seconds.
>
> >
> > If it always seems to fail after a certain time interval, you likely have
> > some kind of problem with your code. If the failure time is more random,
> > you may have noise problems. We have seen noise kill the oscillator
> > completely and only a power down would restart it. It seems the MSP430 is
> > particularly sensitive to noise, more than I have seen on other micros,
> > especially when using a 32 KHz crystal for the clock.
> > That was one reason I had extra capacitance was to minimize the noise on
> the power and ground planes. The clock driving the timer is indeed a 32
> KHz crystal but the power down will not get things going. Next time it
> fails I will check to see if the crystal is still oscillating.
>
> Thanks,
> Kip
> > Lou
> >
> > _________________________________________________________________
> > Want a degree but can't afford to quit? Top school degrees online - in as
> > fast as 1 year
> >
http://forms.nextag.com/goto.jsp?url=/serv/main/buyer/education.jsp?doSearch=n&tm=y&searchcation_text_links_88_h288c&s@79&pQ16
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> --
> Kipton Moravec
> Yahoo! Groups Links
The LED will turn off long time before this voltage is reached. So, you may keep some MSP based circuits off
power for longer than one hour and it does still with enough voltage to have the 32KHz clock working.
To be sure you have zero volts you must short-circuit the MSP's VCC to GND after turning power off, of course.
You can use a tweezer touching both sides of a SMD decoupling capacitor, for example.
Use a voltimeter to check the VCC value after turning power off. You may have another hiden power source in
your circuit, too. JTAG cables like to play this way quite often.
Also, often you don't need large capacitors for filtering the VCC.
Capacitors in the supply rail must be fast and their values must supply current only for short periods while
current comming from power regulator travels through the impedance of the circuit.
Normally you don't need more than 10uF Tantalum for VCC in parallel with a 10nF multilayer chip capacitor.
-Augusto
---------- Cabelho original -----------
De: m...
Para: m...
Cia:
Data: Wed, 21 Feb 2007 09:47:53 -0600
Assunto: RE: [msp430] Lock up through power cycling.
> On Wed, 2007-02-21 at 07:39 -0600, Lou C wrote:
> > >When I cycle power it stays locked up, until I
> > >reload the software using the IAR tool set.
> >
> > With as much capacitance as you have on the board, are you sure it really
> > powers down when you cycle power? The MSP430 draws such little power, and
> > you have so much bulk capacitance, it may not actually be powering down and
> > back up, and therefore not going through reset. Have you tried toggling the
> > reset line to see if that pulls it out?
>
> We considered that, and had it powered down for over 1 hour and it still
> did not come up right. In addition, when it fails, the LED fails on,
> which is drawing about 8 mA. It goes out in about 6-7 seconds.
>
> >
> > If it always seems to fail after a certain time interval, you likely have
> > some kind of problem with your code. If the failure time is more random,
> > you may have noise problems. We have seen noise kill the oscillator
> > completely and only a power down would restart it. It seems the MSP430 is
> > particularly sensitive to noise, more than I have seen on other micros,
> > especially when using a 32 KHz crystal for the clock.
> > That was one reason I had extra capacitance was to minimize the noise on
> the power and ground planes. The clock driving the timer is indeed a 32
> KHz crystal but the power down will not get things going. Next time it
> fails I will check to see if the crystal is still oscillating.
>
> Thanks,
> Kip
> > Lou
> >
> > _________________________________________________________________
> > Want a degree but can't afford to quit? Top school degrees online - in as
> > fast as 1 year
> >
http://forms.nextag.com/goto.jsp?url=/serv/main/buyer/education.jsp?doSearch=n&tm=y&searchcation_text_links_88_h288c&s@79&pQ16
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> --
> Kipton Moravec
> Yahoo! Groups Links
Reply by ●February 21, 20072007-02-21
--- In m..., "aee" wrote:
> ... You may have another hiden power source in
> your circuit, too. JTAG cables like to play this way quite often.
> ...
True. I have pin 2 and pin 4 of the JTAG disconnected but my MSP430
target keeps running "without any power source".
> ... You may have another hiden power source in
> your circuit, too. JTAG cables like to play this way quite often.
> ...
True. I have pin 2 and pin 4 of the JTAG disconnected but my MSP430
target keeps running "without any power source".
Reply by ●February 21, 20072007-02-21
I got to thinking that I was going to do the SVS but had not gotten
around to it, and it may help me if it was indeed a power problem. So I
hooked up the partner board to the one I am having problems with, (since
I am still waiting the 30 hours or so for it to fail.) And added the SVS
code.
I am measuring 3.32V for power.
So in my initialization I added the line
mov.b #0xA8,&SVSCTL ; Set the threshold at 3.05V and POR
I set a break point on that line, and ran to it.
I single stepped (using IAR Compiler) while watching the SVSCTL register
in the debugger, and the SVSCTL register went to 0xFF, and the IAR
Debugger locked up on me. I had to get out of the IAR IDE to recover.
Now I can not talk to the board at all. I have rebooted the PC (multiple
times). I was using the USB JTAG debugger, and switched to the parallel
port debugger. Same thing.
The message I get is:
Emulator
No device found or device disconnected.
Please reconnect the device and press Retry to reconnect
Or press Cancel to abort.
I commented out the line and grabbed another board and was able to talk
to it with the debugger. So it is not the debugger.
Back to the dead board, it looks like the power is O.K. but neither the
32KHz or 3.56MHz is oscillating. I use the 32 KHz crystal for the ACLK
and 3.56 MHz crystal for the SMCLK, and the internal osc for the MCLK.
I think the '1611 died at that instant.
Any ideas for recovery or just solder a new chip on?
===============
As for the flash write, I only do it once to initialize the information
memory. I will comment it out after the first run, and tell the compiler
not to erase the information memory, then I will not have any code that
writes to flash in the program.
On Tue, 2007-02-20 at 16:21 +0000, Joerg Schulze-Clewing wrote:
> Hello Kip,
>
> Could there be any section in your code that might initiate a spurious
> flash write? I am a hardware guy so my first look would be at the
> supply voltage. Is the SVS/BOR configured properly (chapter 6 of
> family spec)? If so, do you have a digital scope that features nifty
> trigger qualifiers so you can set it to go off and log when the supply
> voltage falls outside a window? Tektronix TDS series or something like
> that.
>
> I don't know what else is on your circuit board but could there be
> anything that can generate spikes beyond of what the bypass capacitors
> can muffle?
>
> Regards, Joerg
>
> http://www.analogconsultants.com/
>
>
> Yahoo! Groups Links
--
Kipton Moravec
around to it, and it may help me if it was indeed a power problem. So I
hooked up the partner board to the one I am having problems with, (since
I am still waiting the 30 hours or so for it to fail.) And added the SVS
code.
I am measuring 3.32V for power.
So in my initialization I added the line
mov.b #0xA8,&SVSCTL ; Set the threshold at 3.05V and POR
I set a break point on that line, and ran to it.
I single stepped (using IAR Compiler) while watching the SVSCTL register
in the debugger, and the SVSCTL register went to 0xFF, and the IAR
Debugger locked up on me. I had to get out of the IAR IDE to recover.
Now I can not talk to the board at all. I have rebooted the PC (multiple
times). I was using the USB JTAG debugger, and switched to the parallel
port debugger. Same thing.
The message I get is:
Emulator
No device found or device disconnected.
Please reconnect the device and press Retry to reconnect
Or press Cancel to abort.
I commented out the line and grabbed another board and was able to talk
to it with the debugger. So it is not the debugger.
Back to the dead board, it looks like the power is O.K. but neither the
32KHz or 3.56MHz is oscillating. I use the 32 KHz crystal for the ACLK
and 3.56 MHz crystal for the SMCLK, and the internal osc for the MCLK.
I think the '1611 died at that instant.
Any ideas for recovery or just solder a new chip on?
===============
As for the flash write, I only do it once to initialize the information
memory. I will comment it out after the first run, and tell the compiler
not to erase the information memory, then I will not have any code that
writes to flash in the program.
On Tue, 2007-02-20 at 16:21 +0000, Joerg Schulze-Clewing wrote:
> Hello Kip,
>
> Could there be any section in your code that might initiate a spurious
> flash write? I am a hardware guy so my first look would be at the
> supply voltage. Is the SVS/BOR configured properly (chapter 6 of
> family spec)? If so, do you have a digital scope that features nifty
> trigger qualifiers so you can set it to go off and log when the supply
> voltage falls outside a window? Tektronix TDS series or something like
> that.
>
> I don't know what else is on your circuit board but could there be
> anything that can generate spikes beyond of what the bypass capacitors
> can muffle?
>
> Regards, Joerg
>
> http://www.analogconsultants.com/
>
>
> Yahoo! Groups Links
--
Kipton Moravec
