Truncated match.
PICList
Thread
'Pic Source Book'
1998\09\16@204743
by
Brian Gracia
Hello,
Does anyone have the pic source book? Is it worth getting?
Brian
1998\09\16@212331
by
Bob Blick
Hi Brian,
If you mean the book by Scott Edwards, yes, I have had a copy for many
years. There's a chapter with program listings and explanations of all the
commands that the Basic Stamp has, written in assembler.
It's very useful for someone wanting to move from the Basic Stamp to
writing PIC assembler, but with one serious caveat:
Parallax mnemonics! Not Microchip!
Some of the routines have a very strange (at least in my opinion)
programming style. There are lots of useful routines there, though, and
Scott is a good writer.
I found the book useful when I was starting out with PICs, when there were
very few books on PIC assembler. Now there are many good books to choose
from, and Parallax mnemonics are not useful to many people(confusing even).
-Bob
At 07:42 PM 9/16/98 -0500, you wrote:
>Does anyone have the pic source book? Is it worth getting?
http://www.bobblick.com/
1998\09\16@224443
by
Mark Crosbie
|
In message <spam_OUT3.0.5.32.19980916194229.00fc0220TakeThisOuT
hotmail.com>, Brian Gracia writes:
>Does anyone have the pic source book? Is it worth getting?
It's also available on the web at:
http://www.dontronics.com/see.html
A big file, but worth its wait in gold. As Bob Blick pointed out in another
message, the assembler is written in Parallax mnemonics. However,
I have translated it into MPASM style assembly using the following hack:
1) assemble the code using spasm
2) Obtain the PIC disassembler from Timo Rossi:
http://www.trixatronic.co.jyu.fi/trossi/pic/
3) Compile the 12 bit PIC disassembler pic12dis.c
4) Give it the .obj file from spasm, and it gives you MPASM compatible output!
spasm serout.src
pic12dis serout.obj > serout.raw
Edit the serout.raw file to remove oddities and add headers.
For the Unix users out there:
p12dis serout.obj | awk '{print $3,$4;}' > serout.raw
vi serout.raw :-)
I will work on a PERL script to automate this and post it once it's done.
Enjoy!
Mark.
>Brian
--
Mark Crosbie http://www.best.com/~mcrosbie
Hewlett-Packard MS 47 LA .....mcrosbieKILLspam
@spam@cup.hp.com
19447 Pruneridge Avenue (408) 447-2308
Cupertino, CA 95014 (408) 447-6766 FAX
1998\09\17@035902
by
Dr. Imre Bartfai
Hi,
yes, I have. I got it purchased from the local (Hungarian) distributor,
including also floppy with source codes on it. It costs here about $25. It
is worth of the price, indeed. Unfortunately, it is written in the
8051-fashioned dialect of the SPASM, so I needed to back-translate it, but
it is not so bad. I got a lot of ideas from there.
I hope it helped.
Imre
On Wed, 16 Sep 1998, Brian Gracia wrote:
> Hello,
>
> Does anyone have the pic source book? Is it worth getting?
>
> Brian
>
>
1998\09\17@051318
by
paulb
Dr. Imre Bartfai wrote:
> Unfortunately, it is written in the 8051-fashioned dialect of the
> SPASM, so I needed to back-translate it, but it is not so bad.
Hey! You "knockers" out there, Parallax put a *lot* of development
effort into making that 8051-compatible dialect so all the (and there
are by all accounts a lot of) 8051-users wouldn't have to attempt to tax
their cerebra! It's a big marketing thing, didn't you know?
--
Cheers,
Paul B.
1998\09\18@032439
by
Dr. Imre Bartfai
|
Hey,
I apologize my being "knockers". I did not criticize neither the
8051-dialect, nor you, as you did. However, I think, the disadvantage of
the thing from my point of view, you won't know what happens if you write
some sort of that dialect (I mean timing, side effects, etc.). In the case
you know EXACTLY what is happening you can abandon that dialect, at least
in part. I personally mix the two thing. Furthermore, it is remarkable,
that Microchip itself has developped a small amount if extension of the
native PIC assembly (B, BZ, SKPNZ etc) and this is supported also by
Parallax. For me it is sufficient. To illustrate why it is very important
to know what is happening, look at the following code fragment:
SNZ
MOV REG,#123
Sapienti sat.
Best regards,
Imre
On Thu, 17 Sep 1998, me. wrote:
{Quote hidden}> Dr. Imre Bartfai wrote:
>
> > Unfortunately, it is written in the 8051-fashioned dialect of the
> > SPASM, so I needed to back-translate it, but it is not so bad.
>
> Hey! You "knockers" out there, Parallax put a *lot* of development
> effort into making that 8051-compatible dialect so all the (and there
> are by all accounts a lot of) 8051-users wouldn't have to attempt to tax
> their cerebra! It's a big marketing thing, didn't you know?
> --
> Cheers,
> Paul B.
>
>
1998\09\19@092800
by
paulb
|
Hello Imre.
> I apologize my being "knockers". I did not criticize neither the
> 8051-dialect, nor you, as you did.
You are missing some very "tongue-in-cheek" humour here.
Don«t fuss! ;) It is as I say; you wouldn«t (necessarily) want to
learn the 8051-emulation as a prime means of solving problems, but if
that«s what you already knew (and/ or had applications coded), it«s a
selling point.
> However, I think, the disadvantage of the thing from my point of view,
> you won't know what happens if you write some sort of that dialect
Most of us realise the timing implications, the effect of macros
(which this "dialect" mostly is, or can be emulated) on skips etc. I
*think* however that if you stick closely to the "8051" emulation mode,
the situation balances out. The favoured use of the skip in this mode
appears to be the "JNE" type which is of course "SKPEQ .. JMP", and if
you stick to using these, the skip cannot be split.
Timing implications are certainly more difficult to keep track of, but
obviously not all, indeed perhaps not too many applications involve
isosynchronous or time-critical code. You *certainly* wouldn«t try to
port these directly to the PIC from 8051.
> I personally mix the two thing.
*That* is what might get you, or in fact someone else, into trouble!
> Furthermore, it is remarkable, that Microchip itself has developed a
> small amount if extension of the native PIC assembly (B, BZ, SKPNZ
> etc) and this is supported also by Parallax.
You *can«t* complain about the single-word ones such as SKPNZ. You
can«t really complain about the branches either; just learn the timing
rules (three cycles if taken, two if not - fairly easy) and remember not
to skip over strange things - such as branches.
> Sapienti sat.
Likewise, I«m sure.
--
Cheers,
Paul B.
'PIC Source book'
2000\02\22@090144
by
Geoff Child
|
I have been trying to use the Bin_ASC routine from the online Scott Edwards
PICsource book on the Dontronics site. I downloaded the microchip format and
cannot assembly it( ~ 20 errors). I then followed what it said on the site
to do, reconvert the Parallex format ".src" with ParaPic. When I tried it
said I needed the ".lst file". Don't I need the old Parallex Assembler to
get this. I tried their site but I could not get through.
Does anyone know a site with a bunch of routines like this for the 877.
These ones are for the 16c55 it looks like but it should be fairly easy to
convert over, I think.
Also a question
buffer = 31 ; String buffer at end of memory.
ASC_0 = '0' ; ASCII numbers: 30h thru 39h.
Does the above assign the value to hex 31 to a variable called "buffer" and
assign the value to hex 30 to a variable called "ASC_0" or does it set up a
register called "buffer" at hex address 31 and set a register called "ASC_0"
at hex address 30 ('0"). Is "=" the same as "equ"
Thanks
2000\02\22@095333
by
adavis
|
Dontronics site has another page which is an exact copy of the sourcebook page
except everything has been converted into microchip assembler code.
http://www.dontronics.com/convert.html
-Adam
Geoff Child wrote:
{Quote hidden}>
> I have been trying to use the Bin_ASC routine from the online Scott Edwards
> PICsource book on the Dontronics site. I downloaded the microchip format and
> cannot assembly it( ~ 20 errors). I then followed what it said on the site
> to do, reconvert the Parallex format ".src" with ParaPic. When I tried it
> said I needed the ".lst file". Don't I need the old Parallex Assembler to
> get this. I tried their site but I could not get through.
>
> Does anyone know a site with a bunch of routines like this for the 877.
> These ones are for the 16c55 it looks like but it should be fairly easy to
> convert over, I think.
>
> Also a question
>
> buffer = 31 ; String buffer at end of memory.
> ASC_0 = '0' ; ASCII numbers: 30h thru 39h.
>
> Does the above assign the value to hex 31 to a variable called "buffer" and
> assign the value to hex 30 to a variable called "ASC_0" or does it set up a
> register called "buffer" at hex address 31 and set a register called "ASC_0"
> at hex address 30 ('0"). Is "=" the same as "equ"
>
> Thanks
2000\02\22@123126
by
jamesnewton
2000\02\22@143255
by
Tom Handley
|
At 08:07 AM 2/22/00 -0600, Geoff Child wrote:
>Also a question
>
>buffer = 31 ; String buffer at end of memory.
>ASC_0 = '0' ; ASCII numbers: 30h thru 39h.
>
>Does the above assign the value to hex 31 to a variable called "buffer" and
>assign the value to hex 30 to a variable called "ASC_0"
>Is "=" the same as "equ"
Geoff, the above is correct. As far as Binary to ASCII, check the
following:
204.210.50.240/techref/default.asp?from=/techref/microchip/math/&url=
radix/index.htm
If the above `obfuscated' URL `broke in two' in your mail reader, check the
following and select "Base Conversions":
http://techref.massmind.org/microchip/math/
- Tom
{Quote hidden}>I have been trying to use the Bin_ASC routine from the online Scott Edwards
>PICsource book on the Dontronics site. I downloaded the microchip format and
>cannot assembly it( ~ 20 errors). I then followed what it said on the site
>to do, reconvert the Parallex format ".src" with ParaPic. When I tried it
>said I needed the ".lst file". Don't I need the old Parallex Assembler to
>get this. I tried their site but I could not get through.
>
>Does anyone know a site with a bunch of routines like this for the 877.
>These ones are for the 16c55 it looks like but it should be fairly easy to
>convert over, I think.
[snip]
------------------------------------------------------------------------
Tom Handley
New Age Communications
Since '75 before "New Age" and no one around here is waiting for UFOs ;-)
2000\02\22@155552
by
paulb
Tom Handley wrote:
> If the above `obfuscated' URL `broke in two' in your mail reader,
> check the following and select "Base Conversions":
Umm, Tom, just a little technical point here; the URL doesn't "break"
in the mail reader, actually it breaks in *your* mail sender.
If you can cause your mailer to send it correctly, it may wrap when
you view it but will still be "clickable", viz:
204.210.50.240/techref/default.asp?from=/techref/microchip/math/&url=radix/index.htm
--
Cheers,
Paul B.
2000\02\23@020109
by
Dr. Imre Bartfai
|
On Tue, 22 Feb 2000, Geoff Child wrote:
--- [ snip ] ---
> Also a question
>
> buffer = 31 ; String buffer at end of memory.
> ASC_0 = '0' ; ASCII numbers: 30h thru 39h.
>
> Does the above assign the value to hex 31 to a variable called "buffer" and
> assign the value to hex 30 to a variable called "ASC_0" or does it set up a
> register called "buffer" at hex address 31 and set a register called "ASC_0"
> at hex address 30 ('0"). Is "=" the same as "equ"
>
ad 1. Neither. It says purely the compiler: if you find the word 'buffer',
replace it with '31'. It is completely irrelevant what do you intend
thereafter. It may be as well a register naming act as well as naming a
constant. I guess the 1st assignment would a register, and the 2nd one is
a named constant. Note, that the difference is purely the question of the
context. E. g. you can write
movlw buffer
movwf buffer
The 1st statement loads the constant 31 to W, the 2nd one moves W into the
register #31.
ad 2. Almost. Theoretically, equated variables (they are in fact compiler
variables, or - if you prefer - symbols) can not be changed afterwards,
but assigned can.
I hope this helps
Imre
2000\02\27@164251
by
Rob R
2000\02\28@124336
by
jamesnewton
More... (looser matching)
- Last day of these posts
- In 2000
, 2001 only
- Today
- New search...