any idea how the document, describing code porting from 16f to 18f pics = is called? I couldn't find something like that at microchip. thanx! tino *************************************************************************= ***************************** >-----Original Message----- >From: Michael Rigby-Jones [mailto:Michael.Rigby-Jones@BOOKHAM.COM] >Sent: Thursday, June 03, 2004 11:00 AM >To: PICLIST@MITVMA.MIT.EDU >Subject: Re: [PIC:] drop in replacement for pic 16f876 > >>-----Original Message----- >>From: "B=FChler, Martin" [mailto:Martin.Buehler@KEYMILE.COM] >>Sent: 03 June 2004 09:29 >>To: PICLIST@MITVMA.MIT.EDU >>Subject: [PIC:] drop in replacement for pic 16f876 >> >> >>my code got bigger and bigger, and there is no room left for >>further improvements of the design, as the 16f876 is >>completely full. there is also no way to use the icd >>debugger, as this one consumes some memory too. >> >>as further compression of the code is impossible, I wonder if >>there is an easy way to replace the 16f876 (28 pin pdip) with >>anything bigger. I think this has to be something from the >>18fxxx family. >> >>is there a fully pin and function compatible device, that >>allows me to replace the controller 'in the field', without >>touching the board? >> >>my design uses all pins as digital i/o's and has an icd interface. >> >>thank you for your help! >>tino > > >The 18F252 is pin compatible apart from the low voltage programming pin >(PGM) which was moved from pin 24 on the 16F876 to pin 26 on the 18F252 >part. Not a problem if you don't use low voltage programming however. > >The part has 16K words of program memory. Note you will have to use = the >ICD2 debugger, the original ICD does not support the 18F parts. > >Of coures you will still need to port your 16F code over, but Microchip >does >have a document showing the main aspects of porting to the 18F familly = (but >I don't know the doc number, sorry!). > >Regards > >Mike > > > > >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >This e-mail is intended for the person it is addressed to only. The >information contained in it may be confidential and/or protected by >law. If you are not the intended recipient of this message, you must >not make any use of this information, or copy or show it to any >person. Please contact us immediately to tell us that you have >received this e-mail, and return the original to us. Any use, >forwarding, printing or copying of this message is strictly prohibited. >No part of this message can be considered a request for goods or >services. >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >Any questions about Bookham's E-Mail service should be directed to >postmaster@bookham.com. > >-- >http://www.piclist.com#nomail Going offline? Don't AutoReply us! >email listserv@mitvma.mit.edu with SET PICList DIGEST in the body -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email listserv@mitvma.mit.edu with SET PICList DIGEST in the body