??? 08/04/10 14:26 Read: times |
#177642 - Well, I'm with you there ... Responding to: ???'s previous message |
Michael Karas said:
I'd like to clarify that it shouldn't so much be "Good Tools" but more like be the "Right Tools". The tools required for one project may not be at all what is required for the next project. Serial port output may be essential for debugging in some instances while a totally useless approach in others. Using LEDs or port pins may be perfectly applicable for other debugging tasks whilst a log into a temporary external memory buffer may be the best for other cases.
There are two things that I have found to be an essential requirement for any project however. 1) Oscilloscope. I find a logic analyzer to be VERY helpful in cases wherein the oscilloscope is helpful. It enables me to examine what goes into and what comes out of my MCU, and, of course, any attached peripherals or other logic. It also clarifies any details, particularly in timing, I may have misunderstood, or which were badly specified. 2) Design. The design phase is quite complex and requires careful analysis of requirements. That's where most designs go awry, and it's really the most common error, as insufficient analysis before design will critically hamper the process. Michael Karas
Careful preparation in advance of any coding or hardware design is the best tool for achieving a successful outcome. If one properly defines and documents the problem at hand, derives and documents the requirements, devises and documents a solution, determines its suitability and documents the results, and demonstrates its function, one is well on the way to developing a successful implementation. Without the underlying analysis, the entire effort is likely to fail. The documentation is necessary in order to allow one to back off and regroup as necessary. It does happen, you know. RE |