Version 3.0.8 released.

[HenrikOlsson]

To get away from MicroCodeStudio which is crashing on me now and again.
To to be able to use source level debugging.
To be able to use revision control (that is of course possible outside of any IDE)
To get code folding in the editor.
To be able to easily see how much RAM is being used.

But mainly to get source level debugging.

[Ioannis]

I know that code folding is available through FineLine IDE.

As for sorce level debugging, yes I'd like that too...

About RAM, the MCS gives the number at the end of compilation.

Also the MCS seems stable at my end so far. I remember you had problems, so you still have. Sorry about that. Maybe you can setup a virtual machine and run MCS in this environment.

Ioannis

[pedja089]

Code folding and RAM doesn't work in MPLABX, it just show how much FLASH is used.
Used RAM is always 0%

[Dave]

I have also updated my PBP to 3.0.8 and I use it with MPLAB 8.73a with out any problems. What's the big deal with MPLABX?

[Ioannis]

Are you absolutely sure that you compile with the 3.0.8 and not with an older version of the PBP compiler?

Ioannis

[HenrikOlsson]

Hi,
> I know that code folding is available through FineLine IDE.
Are you sure about that? As far as I can see from Norms post a couple of weeks back it's not.

> About RAM, the MCS gives the number at the end of compilation.
Are you sure about that? As far as I know it tells you how big the compiled program is, not how much RAM it uses.

> Also the MCS seems stable at my end so far. I remember you had problems, so you still have. Sorry about that. Maybe you can setup a virtual machine and run MCS in this environment.
Yes, it still does it from time to time. No, I don't know how to setup a virtual environment and there should be no need to. It crashes for me on at home and at work and I'm not alone so the problem isn't strictly at my end. Even Darrel reported he had crashes with it - more so than he initially thought,

> Code folding and RAM doesn't work in MPLABX, it just show how much FLASH is used.
Oh, that sucks. But you aren't using the latest version of MPLABX are you? Not saying it works there but it IS listed as one of the features so a properly implemented toolchain plugin or whatever it is that is needed "should" allow it to work.

> I have also updated my PBP to 3.0.8 and I use it with MPLAB 8.73a with out any problems. What's the big deal with MPLABX?
What if you try to compile for a part for which support was added in 3.0.8, like the 18F96J99? Does it work then? I suspect it doesn't really need MPLABX but it needs the latest version of MPASM (which comes WITH the latest version MPLABX) in order to assemble code for the new devices.

The big deal with MPLAB is to be able to use source level debugging and to get away from MCSX which crashes from time to time.

/Henrik.

[Tabsoft]

I was seriously thinking of upgrading from PBP 3.0.7.4 to 3.0.8, but with all I have read here maybe not?
I too like Henrik rely heavily on MPLAB for source level debugging and simulation and I can't afford to lose that functionality.

Henrik, have you pinged Charles Leo about these issues?
Hopefully they can put together an install MOP/Manual to get 3.0.8 working for all of us with the correct version of MPLABX with the functions we need working.

[Acetronics2]

To get away from MicroCodeStudio which is crashing on me now and again.
To to be able to use source level debugging.
To be able to use revision control (that is of course possible outside of any IDE)
To get code folding in the editor.
To be able to easily see how much RAM is being used.

But mainly to get source level debugging.

...
my MPLAB 8.92 still works fine ( even for debugging ) ... of course it doesn't know the very, very late chips ...

but I'm happy with it ... and I still can use my gentle 20 years old Picstart plus !!!

Alain