??? 12/07/09 06:37 Read: times |
#171497 - not perfect and never perfectly debugged Responding to: ???'s previous message |
i would not consider any set of hardware, firmware, and documentation to be perfect unless it was really trivial, and if trivial why field it?
thus we have watchdogs, diagnostic routines, panic dumps, coverage testing with logic analyzer running, etc. also, a lot of times schedules are staggered, so that firmware is integrated and provided to qual testing while it is still under development. i would say having the firmware stop responding at random in runs that are months apart are indications that is not working. in the particular case i am thinking of, the uC/board manufacturer forgot to update their documentation after making a change to memory write state handling. |