[En-Nut-Discussion] Ethernut component failure assesment
uprinz2 at netscape.net
Mon May 18 15:07:27 CEST 2009
It is difficult to help you, as you do not state where or when the code
stopped to work. May be you could give some more details. The NutO/S
itself does not do any selftest.
I always add some debug output before and after each stage of
initialisation of each important component. But it is difficult to
implement general debug output as the debug media is unknown. Some
people use serial port, some use displays others unse a simple LED. On
AVR only few people use JTAG.
From: Petri Hyötylä <phyotyla at gmail.com>
To: Ethernut User Chat (English) <en-nut-discussion at egnite.de>
Sent: Fri, 15 May 2009 5:05 pm
Subject: [En-Nut-Discussion] Ethernut component failure assesment
I'm doing a risk assessment for our little project.
I remember that an Ethernut2 stopped working for some unknown reason
(possibly ESD) about 1,5-2 years ago and I replaced the MCU but Nut/OS
testing code still did not work on the board while normal Atmega128 code
seemed to work. I was wondering if there is some power-on self test
is it possible that the MCU will wait indefinitely when there is some
hardware malfunction. If there is some possibility of waiting
is there a possibility of this happening while the system is running? If
these are not possible or likely, I must have done something wrong.
More information about the En-Nut-Discussion