??? 10/16/09 14:59 Read: times |
#169791 - problems with the development tools Responding to: ???'s previous message |
Andy Neil said:
Real life just doesn't divide cleanly like that - with clear, black-and-white dividing lines between "hardware" and "firmware" and "software" (however you define those terms). Richard Erlacher said:
It's no problem differentiating between problems with the development tools and the other two categories. That may be true in many cases. However, the problem itself may not be with the development tools - but the application of some specific feature(s) of the development tools may provide a solution to the hard/firm-ware problem. I think there would be just too many "overlap" cases where it wouldn't so clear whether it's "hardware" or "firmware" - the very nature of "firmware" is, after all, that it's close to the hardware.. If it's listed as a firmware problem, it should included a code listing. Sure - be the listing may be meaningless without the schematic! eg, a lot of new posters think they have a firmware problem because their LED won't blink - when it's really a hardware problem because they've connected the LED wrong! I know that's a trivial example, but I've had cases where I've been convinced it was one, and it turned out to be the other! |