'more eeprom pics?'
Does anybody know if Microchip is planning to develop more EEPROM pics? How
about a 28 pin EEPROM pic?
John Magrane (IsMail)
>>Does anybody know if Microchip is planning to develop more EEPROM pics?
>>>How about a 28 pin EEPROM pic?
There is a 28 pin PIC with EEPROM/RAM dataspace and EPROM program space
coming. The device is the PIC16C822.
Field Apps Eng
TONY NIXON 54964
>Does anybody know if Microchip is planning to develop more EEPROM pics? How
>about a 28 pin EEPROM pic?
If they developed a 16C74 with EEPROM storage, added all of their
existing modules, eg. comparator etc., put in extra ROM and 'stacks' of RAM,
I think they would have an extremely versatile and powerful chip. Especially
if they got rid of the paged ROM/RAM concept. It is probably useful
for multi-tasking projects, but mostly I find it a pain to use and it
wastes precious code space.
Another item I would like to see implemented in silicon is a multi-
byte timer which is capable of incrementing a value rather than
incrementing by one on each clock/prescale transition.
It's amazing how much you can squeeze into the PIC's code space though.
I programmed a 16C84 to operate as an ignition controller. In it's 1K
of program space I managed to squeeze in -
A simple operating system which allows the user to enter min rpm,
mid rpm, mid adv angle, final rpm, final adv angle, dwell, vacuum adv,
cylinders, a pin number, and to read this data out again.
A display interface
A 12 key keypad
The calculations needed to run the engine based on the input values.
Storage of the run parameters into EEPROM
Allow 2 sets of these parameters to be used and stored.
While the engine is running, control the advance, vac advance, dwell,
rev limit, and allow to change to other data set. All of which gets
computed in under 50uS @ 8MHz.
Monitor for a pin number and valid data at startup.
What a headache that was at times.
Just when I thought I knew it all,
I learned that I didn't.
At 17:33 05/11/96 -0800, John Magrane (IsMail) wrote:
>There is a 28 pin PIC with EEPROM/RAM dataspace and EPROM program space
>coming. The device is the PIC16C822.
Does anybody know a solution for storing non volatile program data which
comes in-circuit @56kbps via the serial interface (other than using a 8031
derivative with NVRAM as program & data storage)? I've got to download once
in a while a part of the program (2..4k), and there is no flow control possible.
More... (looser matching)
- Last day of these posts
- In 1996
, 1997 only
- New search...