A new MPLAB IDE

[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

[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

[rmteo]

Hopefully this new, super-secret vaporware (oops vectorware) works better than this http://www.microchip.com/forums/tm.a...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.