Version 3.0.8 released.

[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.

[richard]

I have used mplabx for pbp3 in the past and find
1. code folding does not work
2. ram usage is always 0
3. it won't complie with dt-ints18 included
tried again this morning

"C:\PBP3\pbpx.exe" -ampasmx -k# -os -p18f45k20 C:/Users/rc/Documents/PBP3/tft/tft.X/tft.pbp
Error[116] C:\USERS\RC\DOCUMENTS\PBP3\TFT\TFT.X\TFT.ASM 2456 : Address label duplicated or different in second pass (Z00183)
Error[116] C:\USERS\RC\DOCUMENTS\PBP3\TFT\TFT.X\TFT.ASM 2519 : Address label duplicated or different in second pass (Z00184)
Error[116] C:\USERS\RC\DOCUMENTS\PBP3\TFT\TFT.X\TFT.ASM 2572 : Address label duplicated or different in second pass (Z00185)
Error[116] C:\USERS\RC\DOCUMENTS\PBP3\TFT\TFT.X\TFT.ASM 2603 : Address label duplicated or different in second pass (Z00186)

a click on the error shows this section of the asm file

ifdef OSCFIF  ;----{ Osc Fail  Interrupt Flag }-----------[PIR2, OSCFIF]---
      INT_Source  PIR2,OSCFIF, PIE2,OSCFIE, IPR2,OSCFIP
  endif

 ENDASM?

; C:\PBP3\DT_INTS-18.BAS    00313 Z00183 asm
Z00183
 ASM?
; -- Added for ver. 3.2 --
  ifdef SPPIF   ;----{ Streaming Parallel Port Read/Write }--[PIR1, SPPIF]---
      INT_Source  PIR1,SPPIF, PIE1,SPPIE, IPR1,SPPIP
  endif
  ifdef BCL1IF  ;----{ Bus 1 Collision }--------------------[PIR2, BCL1IF]---

4. worst of all you can't comment/uncomment a block of code

I don't think its worth the effort

[Tabsoft]

I use MPLAB all the time.
I develop and edit in MCS or UEStudio, then do all my source debugging in MPLAB.

It's really about the debugging for me using the simulator.
MPLAB debug in PBP Source and/or assembler.

I then move over to the Oshonsoft Simulator and finally to HW.