Searching \ for '[PIC] New ASM30 incompatibility' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/languages.htm?key=asm
Search entire site for: 'New ASM30 incompatibility'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] New ASM30 incompatibility'
2005\05\23@144006 by olin_piclist

face picon face
I just found out the hard way that the new version of ASM30 has an important
incompatibility to older versions.  I just upgraded MPLAB to 7.11 from some
older release of version 7.  I used to be able to do IFDEF on SFR symbols to
automatically configure code to the particular processor.  However, these
IFDEFs now always indicate the symbol is not defined.

After some rummaging around, I think this has to do with different treatment
of external symbols.  Previously an external symbol would be "defined" as
reported by IFDEF, but is not in the new version.  In other words the
following snippet of code would act differently on old and new versions of
ASM30:

extern xxx
ifdef xxx
   .print "xxx defined"
 .else
   .pring "xxx undefined"
 .endif

This really messes up my code, and I'm trying to figure out how to address
this problem.  I haven't heard back from Microchip whether this is a bug or
an intentional change.  If the latter, it's going to take some work to get
around.  The only robust method I can think of is to write code that
interprets the linker file, extracts definitions of symbols to fixed
addresses, and automatically creates an include file containing those
symbols for each processor.  Writing the general parser for the complete
linker file syntax will take a day or two, and a simple parser will be
vulnerable to legitimate changes to linker file structure.  Yuck.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

2005\05\26@012215 by Chen Xiao Fan

face
flavicon
face
It seems that they are moving very fast with the dsPIC support
tools. Does this mean the tool chain are not that stable
yet? C30 has gone quite some changes recently. So does MPLAB's
dsPIC support.

I have yet to see good tutorial and examples for dsPIC. Together
with the lack of a low cost programmer (lower than ICD2), dsPIC
seems not an option for hobbyists right now.

Xiaofan

{Original Message removed}

2005\05\26@072230 by John J. McDonough

flavicon
face
----- Original Message -----
From: "Chen Xiao Fan" <spam_OUTxiaofanTakeThisOuTspamsg.pepperl-fuchs.com>
Subject: RE: [PIC] New ASM30 incompatibility


> I have yet to see good tutorial and examples for dsPIC. Together
> with the lack of a low cost programmer (lower than ICD2), dsPIC
> seems not an option for hobbyists right now.

Didn't Olin indicate that he has (or will soon have) dsPIC support?

And I wouldn't suggest that ICD2 is really out of the range for hobbyists.
It is on the high end,  but there are a couple of homebrew clones out there,
too, for someone with a little time.

--McD

2005\05\26@080248 by olin_piclist

face picon face
Chen Xiao Fan wrote:
> It seems that they are moving very fast with the dsPIC support
> tools. Does this mean the tool chain are not that stable
> yet? C30 has gone quite some changes recently. So does MPLAB's
> dsPIC support.

Things are evolving more rapidly than for the older PICs, but that should be
expected.  You can definitely get work done with the tools.  Watch out for
the C30 compiler though.  I've got code that seems to work when compiled for
debugging.  Things get a little flaky when turning off debug mode.  They get
more flaky when turning on optimization.

I still haven't heard from Microchip whether the problem I reported was a
deliberate change or an oops they will fix shortly.  In the mean time I
worked around the problem by writing a program that parses the linker files,
extracts the fixed symbol definitions, then writes these out in the form of
an assembler include file using hard .EQUIV directives.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

2005\05\26@082926 by olin_piclist

face picon face
John J. McDonough wrote:
> Didn't Olin indicate that he has (or will soon have) dsPIC support?

The ProProg has dsPIC support.  I haven't migrated that to the EasyProg yet
for two reasons.

First, the consensus here was that other chips were more important to the
hobbyist, and any hobbyist doing dsPIC development would have an ICD2
anyway.

Second, the programming pinout for DIP dsPICs is totally different than
"normal" 18, 28, and 40 pin DIP PICs.  This means you couldn't plug a dsPIC
into the EasyProg ZIF socket, and would need an adapter or only program it
in-circuit.  I'm worried about the support issues of people putting a
30F3013 in the ZIF socket anyway, no matter how prominent I write the
warning not to do that.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

More... (looser matching)
- Last day of these posts
- In 2005 , 2006 only
- Today
- New search...