I asked a similar question a while back on the beta, but I just noticed MPLABX has finally been released.
I tried it briefly ages ago when it was in early beta, but I quickly decided it was better to wait till they ironed the problems out.
So, is anyone using it now?
If so, is it "any good"? (e.g. stable, easy to use, useful, well documented, worth the shift from MPLAB, etc)
Oli Glaser wrote 2012-01-28 22:01:
> Hi all,
>
> I asked a similar question a while back on the beta, but I just noticed
> MPLABX has finally been released.
> I tried it briefly ages ago when it was in early beta, but I quickly
> decided it was better to wait till they ironed the problems out.
> So, is anyone using it now?
> If so, is it "any good"? (e.g. stable, easy to use, useful, well
> documented, worth the shift from MPLAB, etc)
>
I installed it a while ago. Gave up when I could not in 5 min
find SIM and went back to MPLAB 8. A good thing is that two projects,
one MPLAB 8 the other MPLAB X, can share the same source files, so
switching between them is rellatively easy
> Oli Glaser wrote 2012-01-28 22:01:
>> Hi all,
>>
>> I asked a similar question a while back on the beta, but I just noticed
>> MPLABX has finally been released.
>> I tried it briefly ages ago when it was in early beta, but I quickly
>> decided it was better to wait till they ironed the problems out.
>> So, is anyone using it now?
>> If so, is it "any good"? (e.g. stable, easy to use, useful, well
>> documented, worth the shift from MPLAB, etc)
>>
>
> I installed it a while ago. Gave up when I could not in 5 min
> find SIM and went back to MPLAB 8. A good thing is that two projects,
> one MPLAB 8 the other MPLAB X, can share the same source files, so
> switching between them is rellatively easy.
Been using it on Ubuntu 10.10 and 11.10 for 6 months+. Been through the betas but just ran into a very frustrating issue. I tried to change the target device in the project properties. The project was initially setup for the PIC32MX120F032D, ran out of memory on the target so I wanted to switch to the PIC32MX150F128D now that Microchip is shipping that version. Well Microchip doesn't have the latest MPLAB-X and PIC32 Compiler setup to handle this part (Bad on them). But during the process, the system just hung while trying to parse the project file. Needless to say my MPLAB-X environment is trashed and the project is dead. I had to pull the source files out and build a new project. AND when I went to the Microchip download site to grab another copy of the PIC32 complier, their link pointed to the Mac OS-X version even though I selected the Linux version, again Bad on them!! Oh yea, and they have never really answered the question as to whether users with purchased Windows co!
mpiler licenses will have to pay again to get the multi-platform versions of the compilers, but I'm betting we will. Hope there is a discount for those of us that have spent money on the Windows versions of the compilers.
And one more issue, in the drop down window for selecting a target device in the project properties, the window is NOT wide enough to see the complete description of the device. No way I've found to open that drop down selection widget up any to see the full name of the device. I'm sure there are many more issues, but these have caused me special heartburn of late. And this is a released product?????
> Works flawlessly on Slackware 13.37 x64.
>
> On Sun, Jan 29, 2012 at 12:13 AM, Jan-Erik Soderholm
> <.....jan-erik.soderholmKILLspam@spam@telia.com> wrote:
>> Oli Glaser wrote 2012-01-28 22:01:
>>> Hi all,
>>>
>>> I asked a similar question a while back on the beta, but I just noticed
>>> MPLABX has finally been released.
>>> I tried it briefly ages ago when it was in early beta, but I quickly
>>> decided it was better to wait till they ironed the problems out.
>>> So, is anyone using it now?
>>> If so, is it "any good"? (e.g. stable, easy to use, useful, well
>>> documented, worth the shift from MPLAB, etc)
>>>
>>
>> I installed it a while ago. Gave up when I could not in 5 min
>> find SIM and went back to MPLAB 8. A good thing is that two projects,
>> one MPLAB 8 the other MPLAB X, can share the same source files, so
>> switching between them is rellatively easy.
On Sat, 2012-01-28 at 21:01 +0000, Oli Glaser wrote:
> Hi all,
>
> I asked a similar question a while back on the beta, but I just noticed
> MPLABX has finally been released.
> I tried it briefly ages ago when it was in early beta, but I quickly
> decided it was better to wait till they ironed the problems out.
> So, is anyone using it now?
> If so, is it "any good"? (e.g. stable, easy to use, useful, well
> documented, worth the shift from MPLAB, etc)
Hadn't touched MPLAB in ages.
Decided to give MPLABX a go since I'm on a MAC now and just received my
Pickit3.
Was REALLY surprised at how quickly I got stuff up and running. Was
running code on my 10F322 demo board in about 20 minutes.
It seems VERY nice. Haven't really gone too deep into things yet, but so
far, so good.
On Sat, Jan 28, 2012 at 4:01 PM, Oli Glaser <oli.glaserKILLspamtalktalk.net> wrote:
> Hi all,
>
> I asked a similar question a while back on the beta, but I just noticed
> MPLABX has finally been released.
> I tried it briefly ages ago when it was in early beta, but I quickly
> decided it was better to wait till they ironed the problems out.
> So, is anyone using it now?
> If so, is it "any good"? (e.g. stable, easy to use, useful, well
> documented, worth the shift from MPLAB, etc)
I am using it on my MacBook Pro under OSX 10.6 with my PICkit2 without
any difficulties. My needs are pretty basic, but I have found it to
be very easy to use. MPLAB was not an option for Mac, obviously.
One quirky thing I have come up against...I can't figure out how to
turn the device off from MPLABX (i.e., the equivalent of pk2cmd -Ppart
-W from the command line)
I may give it another go - I do quite a bit of development in Eclipse (Android, ARM, etc) and Visual Studio so I am pretty used to the powerful features that are present in such tools. MPLAB is beginning to feel more and more dated in this regard, though I kinda like it anyway as it's solid and "no fuss".
I guess it's a case of what you are used to, but based on the replies, and since MPLABX is based around Eclipse, plus the fact you can use the same source for both MPLAB/MPLABX, I get the feeling it should be pretty painless to get up to speed.
Oli Glaser write:
>
> I may give it another go - I do quite a bit of development in Eclipse
> (Android, ARM, etc) and Visual Studio so I am pretty used to the
> powerful features that are present in such tools. MPLAB is beginning to
> feel more and more dated in this regard, though I kinda like it anyway
> as it's solid and "no fuss".
> I guess it's a case of what you are used to, but based on the replies,
> and since MPLABX is based around Eclipse, plus the fact you can use the
> same source for both MPLAB/MPLABX, I get the feeling it should be
> pretty painless to get up to speed.
Oli Glaser wrote 2012-01-29 22:44:
> Thanks for all the replies.
>
> I may give it another go - I do quite a bit of development in Eclipse
> (Android, ARM, etc) and Visual Studio so I am pretty used to the
> powerful features that are present in such tools. MPLAB is beginning to
> feel more and more dated in this regard, though I kinda like it anyway
> as it's solid and "no fuss".
> I guess it's a case of what you are used to, but based on the replies,
> and since MPLABX is based around Eclipse, plus the fact you can use the
> same source for both MPLAB/MPLABX,
Note that "X" can read/import an "8" project but if you do
project changes in the "X" environment (like adding another
source file) these changes are not written back to the "8"
project file. You have to manualy add the same source file
over there.
But as long as the project configuration is stable (only the
source file content changes), I think you can switch between
them as you like.
Jan-Erik.
I get the feeling it should be pretty
> painless to get up to speed.
On 29/01/2012 22:03, William "Chops" Westfield wrote:
> On Jan 29, 2012, at 1:44 PM, Oli Glaser wrote:
>
>> since MPLABX is based around Eclipse
> MPLABX is based around "NetBeans", one of the less well-known competitors to Eclipse.
>
> BillW
>
Ah yes, so it is.
For some reason I had Eclipse in mind - probably because they are quite similar and it's been ages since I tried the beta.
Are there any big differences between the two I should be aware of?
Coincidently, I've been moving to simpler measures such as custom
make/cmake files and a text editor and a terminal. But I also like mplab
because of the debugger features and real ice integration.
> Thanks for all the replies.
>
> I may give it another go - I do quite a bit of development in Eclipse
> (Android, ARM, etc) and Visual Studio so I am pretty used to the
> powerful features that are present in such tools. MPLAB is beginning to
> feel more and more dated in this regard, though I kinda like it anyway
> as it's solid and "no fuss".
> I guess it's a case of what you are used to, but based on the replies,
> and since MPLABX is based around Eclipse, plus the fact you can use the
> same source for both MPLAB/MPLABX, I get the feeling it should be pretty
> painless to get up to speed.
>
I've taken various versions of the Beta and the current release for a spin
under Ubuntu. Three quick comments:
1. Development tools work.
2. Slow.
3. Simulator does not work. Period. This is a dealbreaker for me.
I could become a happy camper again if I could locate simulation tools that
work with the 16F enchanced chipset that worked on my Linux boxes. Joseph
Julicher from Microchip built a version of gpasm that supports the
instruction set. However, gpsim has not yet been updated...
Typically with IDE's I get frustrated with all the infrastructure. For most
projects, a single file that is edited, assembled, and programmed is
sufficient to get the job done. Having to manage projects, figuring out how
to get files in and out of projects, and locating the appropriate tool to
get a job done just gets in my way.
I'd put up with MPLABX and that modality if it would properly simulate. But
like I said, it's a dealbreaker.
BTW there are years and years of my comments on Wine, virtual machines, and
the like. No need to suggest them to me.
Right now I'm developing on plain hardware, using a serial port for
debugging output. It's working, but sometimes it's easier to simulate an
idea and get all the kinks out before dumping it into real hardware.
BAJ
On Sat, Jan 28, 2012 at 09:01:21PM +0000, Oli Glaser wrote:
> Hi all,
>
> I asked a similar question a while back on the beta, but I just noticed
> MPLABX has finally been released.
> I tried it briefly ages ago when it was in early beta, but I quickly
> decided it was better to wait till they ironed the problems out.
> So, is anyone using it now?
> If so, is it "any good"? (e.g. stable, easy to use, useful, well
> documented, worth the shift from MPLAB, etc)
>
> -
telia.com> wrote:
