??? 01/16/07 08:20 Modified: 01/16/07 08:22 Read: times |
#130854 - Perhaps you\'d like to do some essential work first Responding to: ???'s previous message |
Lay the groundwork ...
Before you can design anything, you have to determine what the requirements are. (A requirement is something without which youre effort will fail to meet its goals.) These are immediate goals. You should never, Never, NEVER, incorportate things that you might need later. They will cause trouble, and won't serve any immediate purpose. How much program memory does your application require? How much data memory does your application require? What sorts of I/O do you have to have. (don't include what would be "nice bit not necessary.") What sort of data processing has to be done, and within what time frame? How many interrupts will you need? What is the operating voltage that you need? With what sorts of external hardware do you have to interface? How many units do you plan to produce (1/year ... 10K/week ...) Do you need any sort of analog I/O? You get the picture ... RE |