Post by thread:16c84 resources

I have recently started 16c84 assembler programming. My habit on a new platform is to start making libraries, so I have made some (delays, rs232 send/receive, conversions etc.). Making a general-purpose library routine often requires some choices, which are basically trade-offs, for instance between code size, data size, stack usage and speed. Question for experienced 16C84 assembler programmers: In your experience, what is the most severe limit on a 16C84: - processing speed - stack depth - code size - data size (file registers) - eeprom size - I/O pins - ???? I realise that no single definitive answer exists, but I'd like to hear some opinions.

> Question for experienced 16C84 assembler programmers: > In your experience, what is the most severe limit on a 16C84: > - processing speed > - stack depth > - code size > - data size (file registers) > - eeprom size > - I/O pins > - ???? Well, almost any design can trade off some of the above for others or for external circuitry. For example, the lack of I/O may be mitigated by the addition of one or more 74HC595 (serial->parallel) or 74HC165 (parallel-> serial) chips. Using 3 pins, you can add any number of outputs or inputs (each 595 or 165 will get you 8 more). Use 4 pins and you can add any number of outputs AND inputs. The only limitation is that you must shift out ALL of the bits in order to read or write any (note that the 595 is double-buffered, so the outputs will be glitch-free while shifting data). I have never found the stack depth on the '84 to be a problem; I'd say the most common limitation I've hit (on the 'C84) was a lack of registers; the double-size register file on the 'F84 should make that less of a problem. Otherwise, I've run up against all the other limitations but fount the most common obstacle to using an '84 is simply price; it costs more than the other OTP devices. Otherwise I just love the things.

This is a PERSONAL opinion but in my opinion my problems are: (from biggest problem to lowest) 1) CODE SIZE (But then I am using a C compiler..... ) 2) I/O pins 100 - TIE) Data size 100 - TIE) Stack depth 101) EEPROM size 500) Processing Speed (Generally I spend most of my time delaying for slower hardware I am interfacing to.) --Alan +--------------------------------------------------------- | Alan G. Smith | spam_OUTagsTakeThisOuTpoboxes.com | http://www.innovatus.com/ags {Original Message removed}

-----Original Message----- From: Floortje Hanneman & Wouter van Ooijen <.....wfKILLspam@spam@XS4ALL.NL> To: PICLISTKILLspamMITVMA.MIT.EDU <.....PICLISTKILLspam.....MITVMA.MIT.EDU> Date: Wednesday, October 08, 1997 17:02 Subject: 16c84 resources {Quote hidden}>Question for experienced 16C84 assembler programmers: >In your experience, what is the most severe limit on a 16C84: >- processing speed >- stack depth >- code size >- data size (file registers) >- eeprom size >- I/O pins >- ???? > >I realise that no single definitive answer exists, >but I'd like to hear some opinions. I am not very experienced, but I find the amount of I/O pins is the most severe limit, but that is just my opinion. TTYL