To add to my previous post (see below), I would like to know the order code
for a PIC16F877 that fits in solderless breadboard (PDIP I think it's
called?).  I found
http://www.microchip.com/1010/pline/picmicro/category/embctrl/14kbytes/devic
es/16f877/options/index.htm, but I'm lost as to which one(s) could work.

Thanks again

> Hi again everyone :)
>
> > This list is particularly good at answering questions.  When you
> > read the documentation from microchip, you will probably
> > have more questions than you started with!
>
> Right!  I've printed the PIC16F877 datasheet (all 216 pages, halfway
through
> the cartrdige ran out), and read it as it printed, skipping things like
> voltage graphs etc., and I think I've got a much better idea now how it
all
> comes together.  But I do got some questions for yas :)
>
> (1) The "Parallel Port" mode, how does it work?  Could I do bidirectional
> comms with a PC parallel port?  What would be a typical application of it?
>
> (2) To access file registers in different banks from code, I know you must
> first set the appropriate STATUS bits, but after that do you refer to the
> memory location as the absolute address (e.g. 80h and upwards for bank 1)
or
> the relative address, (e.g. specify 0h).  I.e. to access byte 0 of page 1
> would you do:
>  (a) set page bits to "page 1" then MOVFW 80h
>   or
>  (b) set page bits to "page 1" then MOVFW 0h
>
> (3) I don't full understand the program memory paging.  Is it all
automatic,
> for example?  If you write enough code to fill page 0, will it starting
> filling page 1, and will all calls/gotos still work between pages
> (seemlessly)?  Or, does it error if you go over the page limit, and you
have
> to ORG 0x900 (or whatever page 1 begins at), and have to BCF/BSF the
PCLATH
> flags every time you goto/call (and what would you do on RETURN?)?
>
> (4) PIC-PIC serial comms.  Eventually my project will have at least 2 PICs
> working in unison (one will be using a math coprocessor to do lots of
> calculations, the other will be the central controller), and I was
wondering
> the easiest way to send messages between them?  I reckoned I could attach
2
> outputs from the central controller to an input on the other PIC, and 1
(or
> 2) the other way round.  One of the lines could trigger an interrupt on
the
> other one (or at least set an "interrupt occured" flag, so the PIC knows
the
> other one wants to send a message), then the other line would be for
serial
> comms.  Could/should I use the inbuilt S2C(I2C?)/UART feature(s) for this,
> is there an easier/better way?
>
> And finally (finally!), what would be the best alternative to breadboard
for
> me to develop higher-frequency circuits on?
>
> ~Le fin~
>
> -Kieren
>
> --
> http://www.piclist.com hint: The PICList is archived three different
> ways.  See http://www.piclist.com/#archives for details.
>

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.