Searching \ for '[PIC] Multiple simultaneous instances of MPLAB.' 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: 'Multiple simultaneous instances of MPLAB.'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] Multiple simultaneous instances of MPLAB.'
2011\09\26@034717 by Forrest Christian

flavicon
face
To tonight, CCS PIC-C has irritated me once again.   Basically had an almost impossible time hunting down a missing #endif (actually had typed it as #end instead).   This was primarily due to the preference of CCS to use a single compilation unit, with multiple files being handled with #includes..... and as such it was hiding the file that I had typoed in...

And yes, I know that CCS supposedly supports multiple compilation units but I seem to recall that the last time I tried to switch my code to multiple compilation units - well, let's just say it went down in flames.  Add to that that my PIC-C maintenance is due again, to the tune of $250 per year... and I've about had it with production code living in PIC-C.

At this point, all the new code is going into at least a PIC18 - so I don't really need the PIC16 compiler which is where this code started...  BUT, the one thing which is keeping me from doing this is the dire warning when you try to start MPLAB a second time on a machine:

"MPLAB IDE is already running on this machine.  It is not recommended to run multiple simultaneous instances of MPLAB IDE".

The problem is that I am regularly writing code that talks between two pics - the 'master' is an 18F which has it's code in MPLAB, and the 'slave' generally is written in PIC-C.   And often I'm toggling between the two for debugging purposes.    So I really need two copies of MPLAB, and possibly two debuggers running, and well two of everything.   And I really don't want to play either the multiple machine or multiple vm game....

So....  I'm wondering what dire things are going to happen if I ignore that warning - or more specifically what it's warning about.   Does anyone have any experience running a couple of copies of MPLAB on a machine?

Thanks.

-forres

2011\09\26@050311 by V G

picon face
On Mon, Sep 26, 2011 at 3:47 AM, Forrest Christian <spam_OUTforrestcTakeThisOuTspamimach.com>wrote:

{Quote hidden}

Yes, I tried this just for fun, but REAL ICE got really buggy (expected) and
MPLAB crashed due to it. If you have two debuggers I think it should work
though. Try it out and see. Why not just run it in a VM, or another
computer? You don't need a particularly *good* computer

2011\09\26@053944 by Isaac Marino Bavaresco

flavicon
face
Em 26/9/2011 04:47, Forrest Christian escreveu:
> To tonight, CCS PIC-C has irritated me once again.   Basically had an
> almost impossible time hunting down a missing #endif (actually had typed
> it as #end instead).   This was primarily due to the preference of CCS
> to use a single compilation unit, with multiple files being handled with
> #includes..... and as such it was hiding the file that I had typoed in...
>
> And yes, I know that CCS supposedly supports multiple compilation units
> but I seem to recall that the last time I tried to switch my code to
> multiple compilation units - well, let's just say it went down in
> flames.  

Same for me. Some months ago I posted here about it. One of my clients
with a huge application had to do the #include thing.
The system became unmanageable.


{Quote hidden}

I simply ignore the warning.


> The problem is that I am regularly writing code that talks between two
> pics - the 'master' is an 18F which has it's code in MPLAB, and the
> 'slave' generally is written in PIC-C.   And often I'm toggling between
> the two for debugging purposes.    So I really need two copies of MPLAB,
> and possibly two debuggers running, and well two of everything.


I know that one ICD2 plus one ICD3 works OK, I already tested. I
remember reading somewhere that two of the same don't work together.


> And I really don't want to play either the multiple machine or multiple vm
> game....


That's a safer way for two debuggers of the same model.


> So....  I'm wondering what dire things are going to happen if I ignore
> that warning - or more specifically what it's warning about.   Does
> anyone have any experience running a couple of copies of MPLAB on a machine?
>
> Thanks.
>
> -forrest


I didn't get any specially bad side-effects.


Isaac

2011\09\26@180753 by Matt Bennett

flavicon
face
On Mon, September 26, 2011 2:47 am, Forrest Christian wrote:
> "MPLAB IDE is already running on this machine.  It is not recommended to
> run multiple simultaneous instances of MPLAB IDE".
>
> The problem is that I am regularly writing code that talks between two
> pics - the 'master' is an 18F which has it's code in MPLAB, and the
> 'slave' generally is written in PIC-C.   And often I'm toggling between
> the two for debugging purposes.    So I really need two copies of MPLAB,
> and possibly two debuggers running, and well two of everything.   And I
> really don't want to play either the multiple machine or multiple vm
> game....
>
> So....  I'm wondering what dire things are going to happen if I ignore
> that warning - or more specifically what it's warning about.   Does
> anyone have any experience running a couple of copies of MPLAB on a
> machine?

I think the warning is largely "Microchip doesn't recommend this. It might
work, it might not. It wasn't tested, and if you find a problem and things
break, we told you not to do it. P.S. C'mon, you're an engineer. You have
to have at least one spare computer kicking around in storage or
preventing your lab bench from wobbling.  Blow the dust off and plug it
in.  It may not have the horsepower to run the latest first person
shooter, but it will debug a microcontroller just fine." Or something like
that.

The biggest problem I've heard of comes in the way of debugging- MPLAB 8.x
doesn't have a way to tell between 2 different debuggers of the same type,
and as VG pointed out, things go south really quickly.  It doesn't know
what debugger it is talking to.

MPLAB X has the ability to differentiate between debuggers based on serial
numbers (or "friendly name" if you choose to use that)- you can have
multiple projects open at the same time- I frequently do, more because I
just don't get around to closing one project before I open another- it
works pretty seamlessly.  But be warned, parts can get destroyed if MPLAB
decides to apply 5V to a 3.3V only part.

Matt Bennett

The views I express are my own, not that of my employer, a large
multinational corporation that you are familiar with

2011\09\27@060543 by cdb

flavicon
face
::The problem is that I am regularly writing code that talks between two
::pics - the 'master' is an 18F which has it's code in MPLAB, and the
::'slave' generally is written in PIC-C

Not intending to start 'compiler wars 900', have a look at FED-C (ie: Wiz-C with the Wizard switched off), the pro version allows multiple projects to talk to each other. It's plus is an excellent simulator and the downside is a very annoying text editing function in the IDE. It is MBLAB'able though.

Colin
--
cdb, .....colinKILLspamspam@spam@btech-online.co.uk on 27/09/2011
Web presence: http://www.btech-online.co.uk   Hosted by:  http://www.justhost.com.au
 This email is to be considered private if addressed to a named  individual or Personnel Department, and public if addressed to a blog,  forum or news article.

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