We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
can you help.
im a pasionate programmer and never leave bugs in my code but i have a problem.
i have my uvision project and it works great. i download it to my dev board and it works great. i put it into another board but it sometimes doesnt work. the board works great and the hw guy says i have a bug in my code. i put code into another board. the only thing i can think is the compiler added a bug to my code.
anyone else seen this?
One very common reason for software working on a Simulator or DevKit but not custom hardware is because of misconceptions, misinterpretations, or misunderstandings of the hardware operation.
It could be that the HW engineer misinterpreted the spec, so the actual hardware operation doesn't (quite) match the spec;
It could be that the SW engineer misinterpreted the spec, so the way he has coded the system doesn't match the actual hardware
Or a combination of the above!
This is before you even start to think about actual bugs in the HW or SW design, mistakes in the implementations, and/or faults in components, assembly, etc...
... hardware bugs that appear as software bugs and software bugs that appear as hardware bugs.
an example of a software bug that appear as a hardware bug would be clocking a peripheral device too fast, some may work, some may not.
Erik
This is precisely the kind of thing that would not show up in simulation, and result in some board "working" (sic) while others "don't work".
Which is exactly why, "dev board ... works great" is almost entirely meaningless!
Similarly for all sorts of other "timing issues"...
Another, I think, is Tenacity: that is, not just giving up and saying, "it doesn't work"; but hanging-in there until you find out why it doesn't work!
And, of course, once you know why it doesn't work - you're well on the way to fixing it!