Searching \ for '[PIC]: Interoperability of MPLAB versions 6.6x and' 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=mplab
Search entire site for: 'Interoperability of MPLAB versions 6.6x and'.

Exact match. Not showing close matches.
PICList Thread
'[PIC]: Interoperability of MPLAB versions 6.6x and'
2005\10\14@165303 by Ian Chapman

flavicon
picon face
I'd appreciate any guidance from people who have made the upgrade from
MPLAB V6.xx to V7.xx, and especially anyone who has scars to prove it.
:-)  I understand that there were some problems with at least the early
V7.xx releases.

I've been happily using MPLAB 6.62 for the last 18 months.  I've been
resisting the upgrade to V7.xx on the basis "if it ain't broke, don't
fix it" but now I need to start a project using a dsPIC30F6014A (the
new 'A'-suffixed part) which isn't supported by V6.62.  I also need to
continue working on projects that I have started in V6.62, and I want
to avoid any significant downtime on those.

I can see two possibilities:

1.  Replace V6.2x with V7.2x.  Am I likely to see any problems when I
open and rebuild projects created with V6.62?  Is it better to remove
V6.6x first and then install V7.2x, or just to install V7.2x over the
top of V6.6x?

2.  Install V7.2x alongside V6.62.  I have read suggestions that this
is possible.  Is it done simply by specifying a different installation
directory?  Are there any conflicts or side-effects to watch out for?
I'm concerned about "DLL Hell" or problems with shared Registry keys.

Incidentally, I'm using a USB-connected MPLAB ICD2 with MPLAB IDE for
debugging and development programming.  Also, I'm still on Windows XP
SP1.  I guess it's clear by now that I'm not very keen on making major
upgrades in the middle of development work.  ;-)

Many thanks in advance for any pointers.
--
Ian Chapman
Chapmip Technology, UK

2005\10\14@171423 by olin piclist

face picon face
Ian Chapman wrote:
> 1.  Replace V6.2x with V7.2x.

Yes.  Just do it.

> Am I likely to see any problems when I
> open and rebuild projects created with V6.62?

A new directive has been introduced that is supposed to replace __CONFIG for
some 18Fs.  Just add the following line before your __CONFIG and all will be
fine:

 errorlevel -230 ;shut up about __CONFIG deprecated already!

> Is it better to remove V6.6x first and then install V7.2x

Yes.  Always do it that way.

> 2.  Install V7.2x alongside V6.62.

Really bad idea.

> Also, I'm still on Windows XP SP1.

So fix it.


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

2005\10\14@173052 by Jan-Erik Soderholm

face picon face
Olin Lathrop wrote :

> A new directive has been introduced that is supposed to
> replace __CONFIG for some 18Fs.

Some 18Fs ?
The MPASM readme file says : "The __CONFIG directive
has been deprecated for all other PIC18 devices."

(And is not suported at all on the PIC18 *J* devices.)

> Just add the following line before your __CONFIG
> and all will be fine:
>
>   errorlevel -230 ;shut up about __CONFIG deprecated already!

Seems easier just to use the new syntax. Much cleaner and easier
to read code.

For examples, see the end of the INC file for any PIC18 device
(in the new MPLAB, of course...)

Regards,
Jan-Erik.



2005\10\14@174553 by olin piclist

face picon face
Jan-Erik Soderholm wrote:
> Some 18Fs ?
> The MPASM readme file says : "The __CONFIG directive
> has been deprecated for all other PIC18 devices."

Yeah, OK.  I used weasel words because I wasn't sure and didn't feel like
looking it up.

> Seems easier just to use the new syntax. Much cleaner and easier
> to read code.

Yes, for new code.  But if you've got existing code that is working fine,
there's no point taking a chance introducing a bug by converting to the new
directive.


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

2005\10\17@074917 by Ian Chapman

flavicon
picon face
Olin Lathrop wrote:
>Yes.  Just do it.

Thanks for the reassurance.  I've now un-installed V6.62 and replaced it
with V7.21 on two PCs.  The procedure went fine and I was then able to
re-build three fairly complex projects without any problems.  Even the
Hex output files were identical (they needn't have been, but they were)
which gave me extra confidence.

>A new directive has been introduced that is supposed to replace __CONFIG for
>some 18Fs.

That won't be a problem.  I need to create new releases of my 18F code
anyway, so I'll just slip in the new directive when I do that.  I had
seen the new "CONFIG" in some code listings, but it didn't register with
me that it was a new directive.  I didn't study it in any detail and I
just assumed that someone had done a #DEFINE CONFIG __CONFIG because
they didn't like underscores.  :-)

>> Also, I'm still on Windows XP SP1.
>So fix it.

My main reason for holding back on SP2 was that I read some postings on
the Microchip forums which appeared to blame it for some problems with
early MPLAB V7.xx releases.  I haven't seen any recent mentions of this,
so I assume that these were either resolved in a later release or were
mis-attributed in the first place.

Many thanks once again.  I'm relieved that, having made the jump, I can
carry on development as if nothing had happened.  Not all upgrades are
that straightforward.
--
Ian Chapman
Chapmip Technology, UK

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