>The above statements by you caught my attention as I have done
> both of these things in my one and only (so far) PIC project.
> Could you please elaborate on why the code shouldn't start at 0
> and why EQU shouldn't be used to define data addresses?
Thanks, I was hopping those comments would start a thread on programming
styles.
>>... It is right up there with starting
>>your code at location zero in any PIC (other than an '84)!
On 5X PICs, the locations <100H (in each bank) are precious for callable
finctions and computed goto's. There is no reasion to start your code
there, as
the GOTO at the ind of code space can point anywhere (I usually use 100H).
Secondly, the first 40H locations are subject to attack in 5X's and 71's,
so if
you have your start-up code there, it makes it subject to interception by
revengers. For this reason, all unused locations in 00-3FH should be also
be
filled with zero, to prevent down-programming.
>>PS. Another handy way to start a lively thread is to mention using EQU
>>to define data addresses.
Using EQU's to define data memory locations an I/O ports is a style of
which I am
not fond.
If you use the porgram counter and .DS (aka. RES) to define all storage, it
makes
memory and IO usage clearer and more portable (adding or deleting routines
which
require stored data is automatic).
Here are a couple of excerpts from REGS.ASM in DEMO.ZIP which is available
on
my BBS, Microchip's BBS and a few ftp sites:
.seg REGS ;org for register declarations
ind .ds 1 ;Pseudo-reg 0 for INDIRECT (FSR)
RTCC .ds 1 ;Real time counter
PCL .ds 1 ;PC
STATUS .ds 1 ;STATUS REG
FSR .ds 1 ;File select reg 0-4=indirect add.dss
;************************************************************************
;* PORT A Definitions
;************************************************************************
B.PROBE = 0,* ;Probe input / AN0 (MUST BE BIT 0)
B.BP2 = 1,* ;LCD backplane bit (3 level)
B.BP1 = 2,* ;LCD backplane bit (3 level)
B.BP3 = 3,* ;LCD backplane bit (3 level)
B.SCALE = 4,* ;Scale / Bias for Probe, RTCC IN, schmitt
PORTA .ds 1 ;Port A I/O register (4 bits)
TAINIT = ^B.PROBE|^B.BP1|^B.BP2|^B.BP3 ;initial TRISA value 1=in
PAINIT = ^B.SCALE ;port A init
-----------------------------------------------------------------------
| Note how the above coding forces you to consider initialization values.
| It also makes the bit label definitiions more portable as they can be
| easilly moved from port to port (eg. B.PROBE is currently defined as
| BIT 0 of PORTA.
|
| Then, later in the code...
-----------------------------------------------------------------------
.seg REGS
;**********************************************************************
;* Start of program-specific registers. More are defined in the modules
;* in which they are required.
;**********************************************************************
REGBASE: ;first reg cleared by RESET code.
TEMP: .ds 1 ;General temporary reg. for LOCAL USE ONLY.
TEMP2: .ds 1 ;General temporary reg. for LOCAL USE ONLY.
VALUE: .ds 4 ;Working value from display (long)
MISCFLAGS: ;miscelaneous flags
B.RA5ON = 0,* ;Flag - RA5 (attenuator) is ON (set to 0)
B.NEWLOGIC = 1,* ;Flag - new logic cycle
B.ZEROENAB = 2,* ;Flag enable zeros for display (0=trim leading 0's)
B.PULSE = 3,* ;Probe detected a pulse
B.PULSE2 = 4,* ;Time delayed PULSE detect
B.SLOPE = 5,* ;Flag - negative slope on waveform
B.NUMPROC = 6,* ;FLAG - enterring a number (LCD and VALUE are
valid)
B.ONETRIG = 7,* ;Flag - Single trigger only
.ds 1 ;
-----------------------------------------------------------------------
Even if you change processors, REGBASE, and all of the flags in
MISCFLAGS are automatically moved.
Yes, there are ways to use EQU for this, but they invite errors, like
not reserving enough space for VALUE if the code is re-used in another
project.
> However, I still feel that the EQU approach is preferable to define the
> special-function registers. The location of these is immutable, so it is
> better (in my mind) to assign them a fixed value.
(actually they are not... Note that they have been known to change from
PIC to PIC (especially when moving from 16cXX to 17CXX parts!)
> If you use .DS/RES and
> make a mistake (i.e. forget a line) then the error will propagate to all
> the other SFRs.
Actually, I (personal "religion" here) prefer the fact that using DS forces
me to check that I have dealt with all registers. The segment management
macros profided with ASPIC take care of boundary checking automatically.
And in the same therad, Chuck McManis (and others) asked:
>> Secondly, the first 40H locations are subject to attack in 5X's and
>> 71's, so if you have your start-up code there, it makes it subject
>> to interception by revengers.
> What does this mean? What is a "revenger?"
A revenger is a person who reverse engineers products or systems. The fact
that
the first 40H words of program memory are re-programmable even while code
protected on some of the PIC parts is fertile ground for revengers. The
security concious programmer must therefore be aware of this and take the
appropriate precautions.
The problem is that no one will openly talk (see how we dance arround it)
about these things (even though it's right there in white-on-white in the
spec sheet). The security precautions are simple and effective.
1st of all someone was asking who was on this listserv and where
they came from.... Well I'm new to this list, I live in Ontario, Canada.
I'm curently a student in the University of Ottawa in Mechanical
Engineering. I'm in my 3rd year. The reason that I joined this listserv
is that I have a big interest in Robotics. The only problem with this is
that it is costly. (any suggestions???)
2nd. I'm got a slight ideal what a PIC is but can someone
clarify it for me.... like it's applications, how hard they are to use in
a robotic application.... and whatever you thinks would be usefull
information. It would be appreciated.
Since we are all introducing ourselves I would like to say hello. I
subscribed to the list last week, and although it went a bit quiet I am
interested in what is going back and forth now.
My name is Andrew Errington and I work as a PC consultant at Lancaster
University (UK). My interest in PICs came about after building a project
with a BASIC Stamp last year and deciding I could do more if I controlled
the processor directly. I bought Microchip's Embedded Control Handbook,
which is _full_ of cool ideas, and I built the 16C84 development programmer
detailed in there. I modified David Tait's controller software so I now
have a development environment that cost me about ?20 (or $30).
The PIC84 is excellent for development as it's EEPROM memory allows you to
recode and reprogram with no effort. I have a project underway (in my spare
time (ha ha!)), and I will probably be looking at other PIC's for other
projects later.
Seeing we are introducing ourselves, I am an Aussie living & working in
Malaysia (interested to see someone here from Singapore - very close).
I am an electronics engineer, but haven't realy started playing with PIC's
yet. I bought a couple of 16C55 chips with the idea of reverse engineering
& improving on a phone monitor circuit that I bought. Then I found out
about the code protect fuse, so that blew that idea.
I am now waiting for some Stamp II units to be released so I can build a
unit to monitor the signal strength of our radio transmitter (just tap onto
the LED lines of our digital signal strength meter) so I can convert to
RS-232 & log the data on a PC.
While I'm here - are the development tools (software & cable) the same for
the Stamp II & Stamp I? If so, I might as well order the development tools
& a couple of Stamp I units & do some initial testing.
Dave
--
-------------------------------------------------------------------------
| David Baker | Internet ID (home) - davidKILLspambaker.pc.my |
| Electronics Engineer | Internet ID (work) - .....davidKILLspam.....gmetra.po.my |
| | Fax - 60-3-2612870 |
| Kuala Lumpur, Malaysia | Compuserve ID - 70461,2360 |
-------------------------------------------------------------------------
My name is Lou Sortman and I am currently working in Chapel Hill, North Carolina
USA administering a Solaris system and the gopher, http, ftp, etc. servers on
it.
I haven't actually used a PIC yet, but I am somewhat familiar with its
architecture. I have, however, designed and built an unusual clock around an
8051 which is probably overkill. The next version will probably run on a PIC
unless I just absolutely need to be able to query/set the time via RS232. 8-)
Gotta get the time <no pun> though.
I might actually have to go and built David Tait's programmer, though I despise
hanging things off of my printer port. Maybe Access.bus (or something better)
will be in common use before I am dead.
The reason that I joined this listserv
is that I have a big interest in Robotics. The only problem with this is
that it is costly. (any suggestions???)
2nd. I'm got a slight ideal what a PIC is but can someone
clarify it for me.... like it's applications, how hard they are to use in
a robotic application.... and whatever you thinks would be usefull
information. It would be appreciated.
I might suggest looking into some papers on subsumption
arechitecture, and implementing a "small" robot using it. The
reason I suggest subsumption is that you could implement self
sufficient components, get the feeling of accomplishment of
having each one work independantly, and then after having several
working, you can have them work in unison to solve a 'bigger'
problem.
I see a PIC as being good for this, because of their small size,
weight, external components required, and $ (especially for the
small ones), you can afford to put a little computing power a lot
of places, which should help in making your robot modular.
> ----- Begin Included Message -----
>
> [snip]
>
> The reason that I joined this listserv
> is that I have a big interest in Robotics. The only problem with this is
> that it is costly. (any suggestions???)
>
> 2nd. I'm got a slight ideal what a PIC is but can someone
> clarify it for me.... like it's applications, how hard they are to use in
> a robotic application.... and whatever you thinks would be usefull
> information. It would be appreciated.
>
> Thanks
>
> Andre Dault
> @spam@s635355KILLspamaix2.uottawa.ca
>
>
> ----- End Included Message -----
>
>
> Andre,
>
> I might suggest looking into some papers on subsumption
> arechitecture, and implementing a "small" robot using it. The
> reason I suggest subsumption is that you could implement self
> sufficient components, get the feeling of accomplishment of
> having each one work independantly, and then after having several
> working, you can have them work in unison to solve a 'bigger'
> problem.
>
> I see a PIC as being good for this, because of their small size,
> weight, external components required, and $ (especially for the
> small ones), you can afford to put a little computing power a lot
> of places, which should help in making your robot modular.
>
> I hope that helps ... JC
I agree. Although I'm not involved in robotics directly, my colleagues in the
AI group are, and this approach has been suggested. It would almost certainly
be the only sensible way to do it using PICs anyway, since they don't really
have enough program space for large applications.
Using the 16C84's would allow the devices to be programmed whilst still in situ
on the robot. I've been trying in-circuit programming using these devices and
it works well; we're considering the construction of a mobile robot using some
simple geared motors / sensors and a number of PICs programmable via external
jack lines. This is only one of a number of projects which may be constructed,
however! If it happens, I'll post some news.
Because of this interest, we'd be pleased if anyone who has already done any
work on a mobile robot in this way would get in touch and let us know how it
worked / is working...
At 05:02 PM 7/21/97 -0400, you wrote:
>Could somebody remind me as to the definition of PIC?
Peripheral Interface Controller
Presently Induced Confusion
Positively Ignominious Confabulation
Purile Invective Colloquialism
Past any Interest or Care
Any additions ?
Rgds
Mike
Perth, Western Australia
Where I should be asleep at 5:31am - uuurgh !
Some say there is no magic but, all things begin with thought then it becomes
academic, then some poor slob works out a practical way to implement all that
theory, this is called Engineering - for most people another form of magic.
Massen
>
> At 05:02 PM 7/21/97 -0400, you wrote:
> >Could somebody remind me as to the definition of PIC?
>
> Peripheral Interface Controller
>
> Presently Induced Confusion
>
> Positively Ignominious Confabulation
>
> Purile Invective Colloquialism
>
> Past any Interest or Care
>
> Any additions ?
>
> Rgds
>
> Mike
> Perth, Western Australia
>
> Where I should be asleep at 5:31am - uuurgh !
>
> Some say there is no magic but, all things begin with thought then it becomes
> academic, then some poor slob works out a practical way to implement all that
> theory, this is called Engineering - for most people another form of magic.
> Massen
>Could somebody remind me as to the definition of PIC?
>
>CAry
>
>PHRIPHERIAL INTERFACE CONTROLER
Oh dear - I can only laugh cause I'm still awake at 7:27am - uuuurgrgrgh !
Potentially Inviolate Constipation
Rgds
mike
erth, Western Australia
Some say there is no magic but, all things begin with thought then it becomes
academic, then some poor slob works out a practical way to implement all that
theory, this is called Engineering - for most people another form of magic.
Massen
Tim Crist wrote:
>
> >Could somebody remind me as to the definition of PIC?
>
> Mike,
>
> FYI, I was told:
>
> Programmable Integrated Circuit
>
> also:
>
> Parts In Chandler
>
> I like the latter.
>
> Regards,
>
> Tim
I'm just starting , I would like to know what will I need to program the
pic12c508 chips. I have never done this before. I have no hardware or
software can anyone please help me.
Take a look at the Microchip website for details on what you might need.
And take a look at the PicList Web Archive at http://www.iversoft.com/piclist/
There are links to other resources and to Microchip too.
Robert D. Rupert wrote:
>
> I'm just starting , I would like to know what will I need to program the
> pic12c508 chips. I have never done this before. I have no hardware or
> software can anyone please help me.
> I'm just starting , I would like to know what will I need to program
> the pic12c508 chips. I have never done this before. I have no
> hardware or software can anyone please help me.
<< I'm just starting , I would like to know what will I need to program the
pic12c508 chips. I have never done this before. I have no hardware or
software can anyone please help me. >>
If you have no HARDWARE can a I sugest a computer or shares in rubber is a
good place to start !
But seriously a Picstart + and MPlab may not be the cheepest soulition but its
worth every pound / dollar / various other stange currency.
Just looking for programs for the pic when I saw this posting. Ive had the
same problem and it seems that the only thing to do in this situation is to
use a powered crystal osc. at 20MHz. They are completely isolated from
outside capacitances so they only output the set frequency of their operation.
>Just looking for programs for the pic when I saw this posting. Ive
had the
>same problem and it seems that the only thing to do in this situation
is to
>use a powered crystal osc. at 20MHz. They are completely isolated
from
>outside capacitances so they only output the set frequency of their
operation.
Well, one could use a paralell resonant crystal with proper loading
capacitors, if one wanted to save a lot of money...
> >Just looking for programs for the pic when I saw this posting. Ive
> had the
> >same problem and it seems that the only thing to do in this situation
> is to
> >use a powered crystal osc. at 20MHz. They are completely isolated
> from
> >outside capacitances so they only output the set frequency of their
> operation.
>
> Well, one could use a paralell resonant crystal with proper loading
> capacitors, if one wanted to save a lot of money...
And a lot of power. I've yet never managed to see a canned oscillator that
draws less than 20 mA at > 1 Mhz. That's about five times the PIC power
drain in a 'normal' application.
It is a recurring question on this list. I have Microchip PIC documentation
running back to 1982 (General Instruments) The 1982 data book assumed
that the meaning of the PIC acronym was so well known that it used PIC
everywhere but did not define what it meant.
On Fri, 27 Nov 1998 09:25:25 -0500 Walter Banks <EraseMEwalterBYTECRAFT.COM>
writes:
>It is a recurring question on this list. I have Microchip PIC
>documentation
>
>running back to 1982 (General Instruments) The 1982 data book assumed
>that the meaning of the PIC acronym was so well known that it used
>PIC
>everywhere but did not define what it meant.
>
I seem to recall from 1977 that the P in PIC stood for pachyderm. The
Cal Poly Rose Float entry that year had an animated elephant, and a PIC
controlled it. The Mustang Daily (the school newspaper) called it a
"Pachyderm [...] Controller" (I can't recall what the I stood for!
___________________________________________________________________
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com/getjuno.html
or call Juno at (800) 654-JUNO [654-5866]
>It is a recurring question on this list. I have Microchip PIC documentation
>
>running back to 1982 (General Instruments) The 1982 data book assumed
>that the meaning of the PIC acronym was so well known that it used PIC
>everywhere but did not define what it meant.
I have an OLD book somewhere that I'm positive said 'Peripheral Interface
Controller'. I can't lay my hands on it at this instant and I'm a bit fuzzy
right now so I could easily be wrong.
>>PIC
>>everywhere but did not define what it meant.
BTW...... :
P I C
Peripheral Interface Controller
- - -
"The PIC16/17 was originally designed as a Peripheral Interface Controller (PIC)
for a 16-bit microprocessor. It was essentially an I/O controller designed
to be very fast. It had a small microcoded instruction set. This design
became the basis for Microchip Technology's PIC16C5X family of
microcontrollers."
Hi,
I agree. I took part on a Microchip seminar, and us was told the same, i.
e. PIC = Peripherial Interface Controller. It least it was the origin.
Imre
> >It is a recurring question on this list. I have Microchip PIC documentation
> >
> >running back to 1982 (General Instruments) The 1982 data book assumed
> >that the meaning of the PIC acronym was so well known that it used PIC
> >everywhere but did not define what it meant.
>
> I have an OLD book somewhere that I'm positive said 'Peripheral Interface
> Controller'. I can't lay my hands on it at this instant and I'm a bit fuzzy
> right now so I could easily be wrong.
>
> dwayne
>
>
> Dwayne Reid <RemoveMEdwaynerspam_OUTKILLspamplanet.eon.net>
> Trinity Electronics Systems Ltd Edmonton, AB, CANADA
> (403) 489-3199 voice (403) 487-6397 fax
>
>
Josh Koffman
Admin 5
--
A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete
fools.
-Douglas Adams
Royce Simmons wrote:
> How do I unsubscribe form this list?
Unfortunately it is impossible to unsubscribe from the list.
Once subscribed that is it for life- or the closure of the list
whichever is sooner.
HOWEVER it is possible to unsubscribulate, and perhaps this is what
you intended.
To do this one must first email some of the more cantakerous :))
members at least 15 times asking some annoying questions and then in
absolute fury you'll find yourself directed to the PICLIST web page
where unsubscribulation is explained in detail.
If you're really lucky these direction will also appear at the bottom
of the messages.
Your final option would be to purchase a PicList T-Shirt or Mug these
also have the unsubscriptulating directions on them.
Unfortunately it is impossible to unsubscribe from the list.
Once subscribed that is it for life- or the closure of the list
whichever is sooner.
HOWEVER it is possible to unsubscribulate, and perhaps this is what
you intended.
To do this one must first email some of the more cantakerous :))
members at least 15 times asking some annoying questions and then in
absolute fury you'll find yourself directed to the PICLIST web page
where unsubscribulation is explained in detail.
If you're really lucky these direction will also appear at the bottom
of the messages.
Your final option would be to purchase a PicList T-Shirt or Mug these
also have the unsubscriptulating directions on them.
"You can signoff any time you like, but you can never leave. Welcome to the
......."
(For anyone sufficiently inexperienced in Americana to be puzzled by this
line, change signoff to "check out" and use Google :-) ). (WAV files are
available on net).
> >Your final option would be to purchase a PicList T-Shirt or Mug these
> >also have the unsubscriptulating directions on them.
> >
> >bodgy o:))
>
> Ahh thats how you get one of those
>
> "I unscribulated and all that happened was this lousy teeshirt"
> teeshirts..... ;-]
>
> If I unscribulate twice can I get a 2xl teeshirt?
>
> "You can signoff any time you like, but you can never leave. Welcome to the
> ......."
>
> (For anyone sufficiently inexperienced in Americana to be puzzled by this
> line, change signoff to "check out" and use Google :-) ). (WAV files are
> available on net).
>
> RM
>
> > >Your final option would be to purchase a PicList T-Shirt or Mug these
> > >also have the unsubscriptulating directions on them.
> > >
> > >bodgy o:))
> >
> > Ahh thats how you get one of those
> >
> > "I unscribulated and all that happened was this lousy teeshirt"
> > teeshirts..... ;-]
> >
> > If I unscribulate twice can I get a 2xl teeshirt?
>
> --
> http://www.piclist.com#nomail Going offline? Don't AutoReply us!
> email RemoveMElistservspamBeGonemitvma.mit.edu with SET PICList DIGEST in the body
--- [snip] ---
> Unfortunately it is impossible to unsubscribe from the list.
> Once subscribed that is it for life- or the closure of the list
> whichever is sooner.
^^^^^^
I do not understand how the list could sense the termination of
subscriber's life. I guess this may not lead to an unsubscription. Even if
it would so, the marked word should be changed to "later".
huh ? a doctor with a sense of humour .... ring the bells!
On Friday 19 July 2002 11:03 am, you wrote:
> --- [snip] ---
>
> > Unfortunately it is impossible to unsubscribe from the list.
> > Once subscribed that is it for life- or the closure of the list
> > whichever is sooner.
>
> ^^^^^^
>
> I do not understand how the list could sense the termination of
> subscriber's life. I guess this may not lead to an unsubscription. Even if
> it would so, the marked word should be changed to "later".
>
> Regards,
> Imre
Hmm, not only can one never leave, but one cannot get in :))))
>Your message is being returned to you unprocessed because it
>looks like a LISTSERV command, rather than material intended for
>distribution to the members of the PICLIST list. .........
I received the above when trying to send this :)))
> "You can signoff any time you like, but you can never leave.
>Welcome to the ......."
and here is me thinking they are made in Arizona, not California.
Typically the technician who manages the email account of the recently
deceased notices the exceptional disk space the deceased is using on the
email server and notifies the piclist that they've passed on, ceased to
be, expired, stiff, bereft of life, rests in peace, pushing up the
daisies, kicked the bucket, shuffled off his/her mortal coil, run down
the curtian and joined the choir invisible.
It has happened before - I think it was a co-worker who notified the list.
Coincidently the list was pretty rude about it. It went something like
this:
Email: How do I unsubscribe from the list
List: Lots of rude comments, jibes, etc (the usual)
Email: Actually, I'm unsubscribing my coworker (this is not my email).
He passed away last week and I've been taking care of his email.
List: Oops! Sorry!
So it doesn't always pay off to assume the person asking to get off is
unable to follow directions. Could be they've never read them.
>--- [snip] ---
>
>
>>Unfortunately it is impossible to unsubscribe from the list.
>>Once subscribed that is it for life- or the closure of the list
>>whichever is sooner.
>>
>>
> ^^^^^^
>
>I do not understand how the list could sense the termination of
>subscriber's life. I guess this may not lead to an unsubscription. Even if
>it would so, the marked word should be changed to "later".
>
>Regards,
>Imre
>
>--
>http://www.piclist.com#nomail Going offline? Don't AutoReply us!
>email EraseMElistserv@spam@mitvma.mit.edu with SET PICList DIGEST in the body
>
>
>
>
>
>
>
Hi dudes
I am going to work on a speech recognition project of mine. I was
wondering which PIC to use. Has anyone done anything similar to this before?
I will be using vector quantization to perform a limited isolated speech
recognition.
> I need to perform basic integration and basic differentiation using
> 8 bit algorithms in assembler,
>
> Would you know the basic approach or where I could find out how to do
> it,
>
The basic approach should be described in any beginning numeric
algorithms book,
and consists essentially a return to the basics of calculus - picking
lines that
approximate the slope on your graph, or adding together
rectangles/trapazoids/etc.
HOWEVER; those algorithms are likely to be heavily based on relatively
accurate
floating point (part of the numeric analysis class is learning to keep
track of
the errors that accumulate in spite of having 32+ bits of number.)
You're likely
to need an awful lot of thought applied to doing things with 8 bit
integers instead.
(just for instance, differentiation is the slope of a line, and it's
going to
be less than 1 about half the time...)
> Just wondering if you could help me out,
>
> I need to perform basic integration and basic differentiation using 8
> bit algorithms in assembler,
>
> Would you know the basic approach or where I could find out how to do it,
The differential of a vector of samples taken at constant intervals is a
vector that contains the difference between adjacent samples in the
input vector, for each pair of samples. The first output sample will be
missing (it's a point of discontinuity so the differential is
undefined). So:
Each diff[i] is the slope of the line defined by the points input[i] and
input[i-1], with ordinate length 1. The differential vector is offset
from the original vector by 1/2 sample to the right on the abscissa (X
or t axis).
The integral of a vector of samples as above can be described otherwise
like: the input vector is the differential vector of the integral
vector of the input. So, from above:
input[i] = int[i] - int[i-1];
The missing part is 'c' the undefined part of the integral, and we need
to supply it before starting. So int[0] = input[i] + c, int[i] =
input[i] + int[i-1], ... . Note that we add a lot and the potential for
overflow is huge (and you really want to check for it and limit the
integral function or something similar):
c = 2^7; // for example
int[0] = input[0] + c;
for i=1; i<N; ++i
int[i] = input[i] + int[i-1];
Again as above the int[i] vector is offset wrt to the input abscissa by
1/2 sample to the left.
The offset problem can be fixed for example by oversampling to 2 x the
sample rate and interpolation (which can be simple or complex). It
automatically increases the accuracy of the int[] and diff[] vectors, if
the interpolation function is well choosen.
These forms be rewritten to operate on a stream if needed (remove the
loop and execute a step with every input event or interrupt or stream
byte or what you need). Note that if c=0 then int[N-1] is the area under
the graph described by input[0..N] if you remove the sign from input[i]
before adding it in.
I'm affraid you've asked a wrong question. First you'll not be able to
use "all 16F and 18F pics". So I suggest to define exactly which one
(or more) you'll use and then to choose a free programmer already
available on the web.
The best free software programmer is without doubt ICPROG, http://www.ic-prog.com, which works OK with many hardware. However not all
pics are supported by icprog.
The second choose will be the port interface for the PC, if you have a
poor 3Ghz laptop then you'll have only USB and free USB pic programmer
combination (hardware and software) are quite hard to found.
so, choose then...
:)
>
> Hello everybody
> I am new to this topic but i want to learn and i hope one of you can
> "light" my way. I have a question in my head and i cannot find a
> straight answer anywhere on google or microchip website.
> Is it possible to make a very simple circuit to program EVERY 16F and
> 18F pics using ICSP ? If so, can you help me with directions on web
> where i can find such info ?
> Thank you in advance
> dics
>
On 6/28/05, Maarten Hofman <cashimorspamBeGonegmail.com> wrote:
> > Read the datasheet for the PIC16F84 or PIC16F628 (I'd suggest the F628)
> > or if you already have a breadboard/experimenter's kit, read the data
> > sheet for the part on that kit's protoboard.
>
> I'd seriously recommend AGAINST the PIC16F84A.
Disagree. Chose the simplest PIC with the smallest numbers of
special function registers and without fancy facilities like AD,
comparators PWM etc. Take a look on the web. PIC16F84 is still the
best represended as ideeas, complete application, codes etc. This does
not mean you have to remain sticked on the 16F84. However will be the
simplest PIC datasheet for reading. AFTER you will knew well 16F84 use
any PIC from the 16 or 18 series you may want. These old PIC users
forgot how difficult was to write the first piece of own code.
> > So what will you suggest one to learn, dsPIC or AVR or even ARM if one
> > wants to upgrade his or her programming skills on medium end MCU
> > (higher end than the PIC12/16 or even PIC18)?
>
> IMHO the step above the PIC/AVR should not be the 30F or a high-end AVR
> but an ARM or another high-end processor (I am not familiar with others,
> but they probably exist).
>
> > Then again one would like to use cheap ARM (LPC2xxx) than the
> > very high
> > end AVRs like AtMega2560. Are there any cheap ARM development tools
> > like STK500 or MPLAB ICD2? I know there is the GNU C compiler.
> > Are there any cheap ARM demo board one can buy or build within
> > a few days of spare time (cheap means <US$100)?
>
> Check Olimex. The Philips ARMs have a build-in bootloader and can be
> programmed with a JTAG wiggler (also available from Olimex). The IDE we
> used in my classes can be found at
> http://et.fnt.hvu.nl/et/docenten/Bent/arm/ARMDevEnv.exe (GNU C,
> Assembler), the latest basic project files are at
> http://www.voti.nl/hvu/D3EEMS1/ram-rom.zip. For next school year I might
> integrate Java into the IDE.
> On 7/7/05, Wouter van Ooijen <.....wouterRemoveMEvoti.nl> wrote:
> > > So what will you suggest one to learn, dsPIC or AVR or even ARM if one
> > > wants to upgrade his or her programming skills on medium end MCU
> > > (higher end than the PIC12/16 or even PIC18)?
> >
> > IMHO the step above the PIC/AVR should not be the 30F or a high-end AVR
> > but an ARM or another high-end processor (I am not familiar with others,
> > but they probably exist).
> >
> > > Then again one would like to use cheap ARM (LPC2xxx) than the
> > > very high
> > > end AVRs like AtMega2560. Are there any cheap ARM development tools
> > > like STK500 or MPLAB ICD2? I know there is the GNU C compiler.
> > > Are there any cheap ARM demo board one can buy or build within
> > > a few days of spare time (cheap means <US$100)?
> >
> > Check Olimex. The Philips ARMs have a build-in bootloader and can be
> > programmed with a JTAG wiggler (also available from Olimex). The IDE we
> > used in my classes can be found at
> > http://et.fnt.hvu.nl/et/docenten/Bent/arm/ARMDevEnv.exe (GNU C,
> > Assembler), the latest basic project files are at
> > http://www.voti.nl/hvu/D3EEMS1/ram-rom.zip. For next school year I might
> > integrate Java into the IDE.
>
>
> Try something powerful than Philips ARM :
>
> http://www.sandbrigetech.com
hey,
i really need help on pic16f877 using mplab
previously,i only play along with pic 16f84
i intend to create a program like a temperature controller
1. set temperature
2.if temperature inside box exceeding set temperature heater will off
below i send along the flow chart and the circuit of the design
hope you guys can help me about this program with fully write program or any info
thanks
aix2.uottawa.ca
