gnupic: Moving from PIC16 to PIC18 Adding chip to gpasm and picp


Previous by date: 14 Feb 2011 20:57:16 -0000 Re: Moving from PIC16 to PIC18 Adding chip to gpasm and picp, Marko Kohtala
Next by date: 14 Feb 2011 20:57:16 -0000 Re: Moving from PIC16 to PIC18 Adding chip to gpasm and picp, captain.deadly.gmail.com
Previous in thread: 14 Feb 2011 20:57:16 -0000 Re: Moving from PIC16 to PIC18 Adding chip to gpasm and picp, Marko Kohtala
Next in thread: 14 Feb 2011 20:57:16 -0000 Re: Moving from PIC16 to PIC18 Adding chip to gpasm and picp, captain.deadly.gmail.com

Subject: Re: Moving from PIC16 to PIC18 Adding chip to gpasm and picp
From: Peter Stuge ####@####.####
Date: 14 Feb 2011 20:57:16 -0000
Message-Id: <20110214205711.10684.qmail@stuge.se>

Please answer Marko's questions.

####@####.#### wrote:
> I've got to move to the PIC18 chips
..
> The last time I checked SDCC didn't support PIC18

Note that PIC16 and PIC18 are very very similar. They're basically
the same architecture, except that PIC18 can have a call stack, to
make code generation in C compilers easier.


//Peter

Previous by date: 14 Feb 2011 20:57:16 -0000 Re: Moving from PIC16 to PIC18 Adding chip to gpasm and picp, Marko Kohtala
Next by date: 14 Feb 2011 20:57:16 -0000 Re: Moving from PIC16 to PIC18 Adding chip to gpasm and picp, captain.deadly.gmail.com
Previous in thread: 14 Feb 2011 20:57:16 -0000 Re: Moving from PIC16 to PIC18 Adding chip to gpasm and picp, Marko Kohtala
Next in thread: 14 Feb 2011 20:57:16 -0000 Re: Moving from PIC16 to PIC18 Adding chip to gpasm and picp, captain.deadly.gmail.com


Powered by ezmlm-browse 0.20.