PIC microcontroller & C programmingWhich microcontrollers are you using and what language are you programming in?
Are the self test strategies for debugging the code or detecting future hardware failures?
Google "corner cases" & "edge cases" and risk an answer yourself.PIC microcontroller & C programming
Do you write self test code for embedded systems?
How do you write code for detecting device failure connected to microcontroller?
Before I retired, My job was to design automatic test systems for all kinds of products . I wrote the software to run them and did include some self diagnostics to ensure that the test systems were working correctly. The design of the diagnostics varied widely depending on the hardware used in the system, which, in turn, depended on exactly what was being tested. Each case was unique.PIC microcontroller & C programming
Do you write self test code for embedded systems?
How do you write code for detecting device failure connected to microcontroller?
It's seem some negative criticism for asking programming question.Busy since last April, the OP seems to be preparing a quite complete encyclopedia about programming based on the answers collected in AAC. Lot of chapters...
Or is it a questionnaire to be filled by the end of the semester?
your answer is too short to understand. can you explain it a bit
- Controllability
- Observability
You can't debug what you can't observe, and you can't fix what you can't control.your answer is too short to understand. can you explain it a bit
Not at all!It's seem some negative criticism for asking programming question.
To expand a bit. You need to consider these two things before the first design document is begun. Providing for them is part of the requirements for the whole project and not an after thought. Too many "cost sensitive" systems are specified in such a way that no provisions for controllability or observability are allowed. It is certain that such systems are unlikely to be a success.You can't debug what you can't observe, and you can't fix what you can't control.
#define TRACEINT(iTrace) traceInt(__FILE__, __LINE__, #iTrace, iTrace)
void traceInt(char *fileName, int lineNumber, char *varableName, int valueOfTrace)
{
printf("%s|%d|%s|%d\n\r", fileName, lineNumber, varableName, valueOfTrace);
}
TRACEINT(i);
maybe i didn't ask the right questionDo you mean debugging problem during development?
- this would be solved with debugging tools an strategy
or you mean some sort of system check-up during boot
- most embedded systems have some sort boot-time peripheral and memory checking
I agree 100% @KeithWalkerThey are examples of errors in assembly and programming. You can test the functionality of the code during de-bugging by displaying variables at suspect places in the code but there is no need to write special error messages as you will be the one de-bugging the code and will be the one who can interpret the results.
by Jake Hertz
by Jake Hertz
by Duane Benson
by Aaron Carman