gnupic: mcp2510.inc in gpasm headers?
Subject:
Re: mcp2510.inc in gpasm headers?
From:
"Niklas Wennerstrand" ####@####.####
Date:
4 Nov 2001 17:41:01 -0000
Message-Id: <000001c16558$f3450a00$705b43d5@telia.com>
Hello Brandon,
The MCP2510 is a CAN controller and in some of the PIC18C this peripheral is
included into the core (PIC18C658). It will also be included in the future
PIC18FXXX.
MCP2510 is rather complex and its not too easy to include it as an external
or internal peripheral. Its not as "easy" as implementing a timer or PWM
etc. The gpsim guys had some discussion on include peripheral devices as
LED, 7segLED, buttons and other peripheral. To start with a CAN-controller
is probably a bad idea. As my C++ teacher tough me once: KISS (Keep It
Simple Stupid), the best advise I can give to any students and its also a
great rock'n roll band. The include file for 18C658 is easy to copy from the
MCHP include file but I guess you are looking for simulator support in gpsim
and my guess is that, that devise have to wait until a lot of other devices
is supported in gpsim. Trust me, a CAN core is nothing you would like to
start with. gpasm is the assembler for PICmicro under Linux and the 18C658
include file wont help you if you have a external MCP2510.
Regards
Niklas
-----Ursprungligt meddelande-----
Från: ####@####.#### ####@####.#### För Brandon
Fosdick
Skickat: den 3 november 2001 02:06
Till: ####@####.####
Ämne: mcp2510.inc in gpasm headers?
Would it be possible to get mcp2510.inc included in the gpasm distro? It
doesn't have any copyright info at the top and it doesn't mention that
it was created by Microchip (only that its for a Microchip device). The
other header files look the same as the set that comes with MPLAB
(although I haven't looked at MPLAB in some time), so I assume its okay
to include.
For those that don't know, mcp2510.inc is the header file for
Microchip's CAN controller.
---------------------------------------------------------------------
To unsubscribe, e-mail: ####@####.####
For additional commands, e-mail: ####@####.####
