A new MPLAB IDE

[Acetronics2]

Hi,

As told in the Title ...

Still a beta Version, but really promising. ;)

http://www.microchip.com/MPLABX

Alain

[Ioannis]

Hi Alain.

Have you tested with PBP? Does the new X IDE support the lanquage?

Ioannis

[Acetronics2]

Hi, Ioannis

The beta version , to the day, only supports "Microchip" compilers, but It's of course planned to support Third Party ones ... the "add toolsuite " feature already is here !!!
So you have to use assembler or C without conditionnal assembly ... for the moment.

remember it's NOT at production level and many features are still disabled.

PicStart plus is no more supported as a programmer ... halas !

Alain

[Ioannis]

Sorry for the late reply, but e-mail notifications still do not work...

Thanks for the feedback.

Sorry that PicStart and PicStart+ are not supported. I have the both of them...

Anyway, technology keeps moving forward, so we adapt, right?

Ioannis

[mackrackit]

Was/ is there a command line option for the PicStart+ ?

[Ioannis]

I could not find any up to this moment David.

Ioannis

[mackrackit]

Darn...
looks like another gadget for the shelf. But I have not used mine for a year or so anyway.

[Ioannis]

I got Picstart, Picstart+, ICD1, ICD3, Pickit3 and ELNEC PikProg+.

I think I have a record! Anyone else?

By the way, do you receive e-mail notifs?

Ioannis

[mackrackit]

You got me beat. I only have PicStart+, PicKit 1, and a couple of PicKit 2.

Nope, no email for a couple of weeks and no news either.

[Ioannis]

Ooh, I forgot. I am expecting another Pickit3, as a gift from the Local Microchip Seminar! (Plus the touch clock they gave us with a AAAA battery!)

Ioannis

[mister_e]

Was/ is there a command line option for the PicStart+ ?
there's PICP, but you may miss loads of new devices... it's an open-source though... worth it?

[mackrackit]

there's PICP, but you may miss loads of new devices... it's an open-source though... worth it?
Probably not worth it. Portable computers with serial ports getting hard to find/cost to much.....

A PicKit2 on the bench and one in the go bag and I am set.

I will just put the PicStart in the shed. The Tandy and C64 need company. :)

[mister_e]

http://www.hellinthehallway.net/wp-content/uploads/2009/12/oh-no-you-diint-emu.jpg

Those are beauty... when I was young... Any chance you have a TI99 and a VIC20 as well :D

BTW, did you have a look at Commodore website? He's back! http://www.commodoreusa.net/CUSA_C64.aspx

[mackrackit]

Any chance you have a TI99 and a VIC20 as well
Nope.

That new C64 looks interesting. It would make a great conversation piece...

But Steve... you are not looking so good :p

[mister_e]

Jealous :D

[Acetronics2]

Anyone for an Unicom 202SR, a HP35, HP29C, and full options HP86B ???
Plus Casio Fx 850 and 880P ...

:D

Alain

BTW, DO NOT upgrade MPLAB to V 8.63 ... there's a bug and previous ASM projects cause a MPLAB Locking when Built.
PBP projects do not seem to fail, but ... better to be careful.

[Darrel Taylor]

Alain,

Do you have an example program that will lockup with MPLAB 8.63?

I can't seem to duplicate it with ASM programs that I have.
If Microchip messed something up again, melabs needs to know.

Thanks,
DT

[Acetronics2]

Hi, Darrel

Nothing special with those asm files ... their compilation ALWAYS create an IDE locking.

I re-installed v 8.63 : still locking

went Back to V 8.60 and everything works fine ...

soooooo, I really think it's a bug !!! ( no line about any projects mods to do in the IDE release notes )

My OS is XP Home SP3 " up to date " ...

Have a happy new year :)

Alain

[Acetronics2]

I had made 4 attempts ...

4 times it has bugged ...

A last one to send Microchip a screenshot ....

MPLAB was very, very long to start this time ( ~ 5 minutes ) , and there were strange things about the last used compiler location ( blank address ! ) ... but , once correctly answered, project compiled correctly.

with no more strange issues.

Sooooo ... what has happend ???

Great Mystery !!! :confused:

Alain

[retepsnikrep]

The ide update appears to break mpasm

I now get the following error on all my old projects

error 118 overwrite previous address contents I tried to go back to 8.10 and still have the same error now :roll:

http://www.microchip.com/forums/m439213.aspx

Which working version are others using?

[mackrackit]

error 118 overwrite previous address contents
That is from setting the configs in two places. You must be setting them in code space with out commenting the PBP *.inc files.

[mackrackit]

Which working version are others using?
Use the one that came on the cd when you purchased PBP. That one works.

[ScaleRobotics]

Which working version are others using?
I am using MPLAB IDE 8.60 (MPASM 5.38) with PBP 2.60

What version of PBP do you have?

[retepsnikrep]

2.60A I'm away on holiday and dont have by pbp cd with me.

It's not setting the configs twice. The link I posted seems to suggest something has chan ged with mpasm.

[mackrackit]

Maybe if you posted your code and configs it would help.

Or just install from your CD when you can.... That is what it is for. Everything you need in one convenient place.

[retepsnikrep]

Sorted now it was the configs :roll: Appologies for doubting the gurus on here

[Acetronics2]

Hi, All

Great News ...

MPLABX supports PBP Now ....

Sure Charles could tell us some words about it ... ( about the use or not of PBPMPLAB.bat ... i.e.)

and may be explain me that ...



/usr/bin/make -f nbproject/Makefile-default.mk SUBPROJECTS= .build-conf
make[1]: Entering directory `/c/Program Files/Microchip/MPLAB IDE/Projets/X/Lights.X'
/usr/bin/make -f nbproject/Makefile-default.mk dist/default/production/Lights.X.production.cof
make[2]: Entering directory `/c/Program Files/Microchip/MPLAB IDE/Projets/X/Lights.X'
mkdir -p build/default/production
C:\\Program\ Files\\Microchip\\MPLAB\ IDE\\PBP\\PBPW.EXE -ampasmx -k# -p12f675 Lights.pbp
make[2]: *** [build/default/production/Lights\.cof] Error 1
make[1]: *** [.build-conf] Error 2
make: *** [.build-impl] Error 2
PICBASIC PRO(TM) Compiler 2.60C, (c) 1998, 2011 microEngineering Labs, Inc.
All Rights Reserved.
ERROR: Unable to execute mpasmx.make[2]: Leaving directory `/c/Program Files/Microchip/MPLAB IDE/Projets/X/Lights.X'
make[1]: Leaving directory `/c/Program Files/Microchip/MPLAB IDE/Projets/X/Lights.X'
BUILD FAILED (exit value 2, total time: 609ms)



Alain

[HenrikOlsson]

Yes, do tell us more please.
I've been playing around with the evaluation version of UltraEdit and I'm starting to get code folding and syntax highlighting to a place where I want it but there are many other things that needs sorting (and removed from the default layout) for it to be worth it.

If MBLAB X is the bee's knees then there's no need to spend the time and cash on UE.

[Acetronics2]

Download is here :

http://www.microchip.com/en_US/family/mplabx/index.html

Alain

[Demon]

How does this compare with Mecanique Microcode Studio Plus?

Is it worth changing if I'm used to MCSP?

I know it's free, but MCSP is already paid.

I remember looking at MPLAB when I first started and it didn't look as user friendly as MCS, things just didn't look at intuitive. It could have been just me, tastes and first impressions affect our choices so drastically.

[Acetronics2]

IMPORTANT



For beta 6 support PICBASIC PRO and CCSC was added. However, support to import an MPLAB 8 project using this compilers is not there yet. You need to recreate the projects using the "Standalone Project" wizard.
Also, to use the PICBASIC PRO, you might need to add mpasmx to your path: add $InstallationDir\mpasmx. For example, if you installed to the default MPLAB X installation directory in a 32 bit Windows system, you'd need this in your path:
C:\Program Files\Microchip\MPLABX\mpasmx

Do this if you get the error:
ERROR: Unable to execute mpasmx.make[2]:

If you change your path, you need to re-start MPLAB X.



Alain

[Ioannis]

I sure agree with you Robert.

The MPLAB feels like the ... bad old DOS environment.

I prefer the MCS too.

The X is different from the old 8.xx and promisses to give some whistles and bells.

If anyone has tested the editor please report.

I do not want to download the over 200Mb beast just to see that I do not like it...

Ioannis

[rmteo]

The X is different from the old 8.xx and promisses to give some whistles and bells.

If anyone has tested the editor please report.

I do not want to download the over 200Mb beast just to see that I do not like it...

Ioannis
Plenty of user experiences over at the MCHP Forums http://www.microchip.com/forums/default.aspx

[HenrikOlsson]

Hi,

How does this compare with Mecanique Microcode Studio Plus?
MCSP is great but it doesn't seem to be maintained any more which is unfortunate. It lacks code folding (so does MPLAB 8.xx when used with PBP, AFAIK) and it lacks "true" source level debugging.

Norm is onto something with his FineLineIDE but I don't think it'll provide source level debugging.

/Henrik.

[Ioannis]

Plenty of user experiences over at the MCHP Forums http://www.microchip.com/forums/default.aspx

Have not found something related to PBP though...

Ioannis

[rmteo]

Perhaps Ace is the only one who has used it with PBP - and he's not telling. ;)

[Ioannis]

Alain? Are you hiding something from us?:)

Ioannis

[mister_e]

I say, no picture, no proof, I don't believe it... like a recent Barak Obama Annoucement... (cough)(cough)

[ScaleRobotics]

I've got proof ....

Proof that it doesn't work for me ....

But I obviously don't get as far as Alain.

http://www.picbasic.co.uk/forum/attachment.php?attachmentid=5458&d=1304647126

[Demon]

I installed MPLAB when I reinstalled everything recently, I just never got around to giving it a 2nd look.

Right now MCSP does pretty much all I need so I'm content.



...
It lacks code folding (so does MPLAB 8.xx when used with PBP, AFAIK) and it lacks "true" source level debugging.
...


I don't know what either one is anyways.

True source is being able to look at the assembler-generated code maybe?


So I fired up MCSP to see what the last dates were in the HELP/ABOUT; 2001, 2005.

So I clicked on the FORUM to see what that looked like and it sent me here. LOL

[rmteo]

True source level debugging allows you to debug code using source (Basic, C, Pascal, etc.) statements or the generated ASM statements. It should display both types of code side-by-side and allow easy switching between windows. More importantly, a good debugger should have the following features:

a. debugging in hardware - not simulation.
b. single stepping through code (source or ASM).
c. step into, step over, step out of routines.
d. ability to set multiple hardware breakpoints - code stops on breakpoints.
e. conditional breakpoints using expressions, eg. stop when x>100 and y=0.
f. ability to control how hardware operates in a breakpoint, eg. should a timer continue running or stop.
g. ability to examine and/or change every SFR and memory location.
h. ability to watch memory location in real-time with hardware running (watchpoints).
i. ability to do automatic cycle counting.

[cncmachineguy]

Does such an animal exist for use with PBP?

[mister_e]

yes... and really good.

[cncmachineguy]

oh pray tell!!!

[mister_e]

everyone will know when the final version will be available.

It really kick MCSP and MPLAB a$$ hands down... none the less.

[cncmachineguy]

wheres the beta? or even alpha?

[mister_e]

somewhere hidden in a vortex.

[rmteo]

Does such an animal exist for use with PBP?

Someday, hopefully, keep your fingers crossed. ;);)

I do use a system that has all the features I mentioned (and more) on a daily basis, though.

[mister_e]

but on another platform i guess?!? :P

[rmteo]

but on another platform i guess?!? :P

That should be pretty obvious. :)

[mister_e]

IT'S A PICBASIC FORUM HERE lol!


I have a dream

http://www.holiday-celebration.com/images/dreams-martin-luther-king-i-have-a-dream.jpg

[HenrikOlsson]

I don't know what either one is anyways.
True source is being able to look at the assembler-generated code maybe?Code folding is where the IDE/Editor "folds away" the code when you don't need to see it. For example, it hides everything between IF and ENDIF statements, then you can "expand/hide" the section by toggling a little a button right next to the start of the section. See the attached screenshot.

rmteo gave a good explanation pof source level debugging. MCSP provides it, sort of, but the way its done with MCSP has several drawbacks. It's possible to do tight now with MPLAB 8.xx (and I suppose x).

What's this I hear about a new IDE? Are there a new version of MCS on its way or is something completely different? Speak up! ;-)

/Henrik.

[mister_e]

You haven't checked WikiLeak?!?

It's something in progress since years and who's having reach another level, and still in progress. Can't say much... just be patient.

[Ioannis]

If someone really pays me a lot, I can give a name:)

Ioannis

[mister_e]

Yeah me too... some NDA signed as well :eek:

[rmteo]

Hopefully this new, super-secret vaporware (oops vectorware) works better than this http://www.microchip.com/forums/tm.aspx?m=576676&mpage=1#576676


Hi - I have just downloaded and tested Beta 6 after not using MPLAB X for some time due to its useability.

I still find that the product is still not really useable. It is very slow in debugging and stepping, does not allow debugging of interrupt service routines and is pretty unstable.

I personally do not feel that this platform will ever be a replacement for the present MPLAB IDE due to the inherent problems with NetBeans. If A new editor was slotted into MPLAB IDE 8 it would probably be a far better route than MPLAB X.