> -----Original Message-----
> From: spam_OUTpiclist-bouncesTakeThisOuT
mit.edu [.....piclist-bouncesKILLspam
@spam@mit.edu] On
Behalf
{Quote hidden}> Of Bob Blick
> Sent: 29 April 2010 21:13
> To: Microcontroller discussion list - Public.
> Subject: Re: [PIC] Using picc8.05. How to add new PIC?
>
>
> On Thu, 29 Apr 2010 14:56:07 -0500, "microsoftwarecontrol" said:
> > New PIC have so good function. I want to leave F877 and start to use
> F886
> > or F1939, etc.
> > The first, all of them have internal 32 MHz osci
>
> The easy answer is to use the latest version of PICC.
>
> But you can hack away and add SOME newer PICs to your old 8.05. I did
it
> for the 884/6/7
>
> You need to create a 16F887.h file and you also need to add new
sections
> to the pic.h and picinfo.ini files.
>
> As far as 16F1939, I have no idea.
>
> Cheerful regards,
>
> Bob
I recently added support for the 12F617 to PICC8.05 for a small project
at home and it was rather more involved than I was hoping!
1) Create device header and add to the include folder.
2) Modify pic.h to include the new header if the symbol _12F617 was
defined.
3) Create a custom FLASH_READ() macro in pic.h just for the 12F617
variant.
4) Add device info into picinfo.ini in the lib folder.
At this stage I was hoping it would work, but it fell over during
compilation stating that a library file was missing "pic10--u.lib".
This target name was not even present in the library makefile...so
5) Edit sources\makefile and add pic10--u.lib to 'ALLLIBS'
6) Modify target picpph to create picpph.lib with CHIP=12F617
7) Copy picpph.lib to pic10--u.lib and move it to the lib folder (this
library uses the FLASH_READ macro created in step 3). This should
become clear if you examine the makefile.
This wouldn't compile if the FLASHTYPE was set to READWRITE_A in
picinfo.ini, but I only needed read capability so set FLASHTYPE=READ and
it all compiled and (somewhat surprisingly) worked perfectly, including
debugging. I had only a few words of program memory left by the time I
finished the project so gave it a good work out.
To add flash write capability to the library I suspect I would need to
edit flashcopy.c and recompile the library...or just create a flash
write function in my code.
Regards
Mike
=======================================================================
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.
=======================================================================