WRITE: One more PBP 2.60 Surprise ...

[Darrel Taylor]

Yeah, I saw that one last month and reported it. It happens if ONLY WORD variables are used with WRITE. If you use a WRITE with a BYTE var anywhere in the program, the WRITE's with WORD vars will be ok. Or you could fix the problem in the .MAC file.

The WRITE?W macro is missing the WRITE_USED = 1 line.
If a WORD variable is used, it gives a [225] undefined symbol 'write' error.

If any other write statements (without WORDs) are in the program, it's OK.
Or adding DEFINE WRITE_USED 1 works too.

WRITE?W macro Win
        MOVE?WA Win
        L?CALL  WRITE
    endm
WRITE_USED = 1    ; <------ Missing
  endmod

HTH,
DT

They mentioned something about creating a list of problems on thier website since the fixes won't be available untill the next Patch.
But I don't know when or if that will happen.

[Archangel]

Yeah, I saw that one last month and reported it. It happens if ONLY WORD variables are used with WRITE. If you use a WRITE with a BYTE var anywhere in the program, the WRITE's with WORD vars will be ok. Or you could fix the problem in the .MAC file.



They mentioned something about creating a list of problems on thier website since the fixes won't be available untill the next Patch.
But I don't know when or if that will happen.

I fixed all the 2.6 issues by reinstalling 2.5

[Darrel Taylor]

I fixed all the 2.6 issues by reinstalling 2.5

You should have a separate installation for every version that you own.

MicroCode Studio recognizes the different versions and puts a Drop-Down box next to the "Compile" button.
You can select which version you want to compile with.
And when you want to play with 2.60 you can.

The ArrayRead/ArrayWrite statements alone make 2.60 worth it.
But there's so much more beyond that.

My installations look something like this ...
C:\PIC\
C:\PIC\PBP245\
C:\PIC\PBP246\
C:\PIC\PBP247\
C:\PIC\PBP250\
C:\PIC\PBP250c\
C:\PIC\PBP260b1\
C:\PIC\PBP260\

[Acetronics2]

The ArrayRead/ArrayWrite statements alone make 2.60 worth it.
But there's so much more beyond that.

Hi, Darrel

I lost two full days with the 2.60 Upgrade ...

Hunting bugs

Updating ALL the MPLAB existing projects ( MCS + µChip programmers = NOT so good, yeah ! ).

PLUS some program mods due to ... a "little" bigger code produced. ( I've noted ~ 1%, 12F series seem to suffer a maximum ... )

many of my program just were fitting into Prog memory of the pics !!!


Sooooo, considering ALL the new functions offered ...

The one I prefer is the " Memory usage gauge " at last accecpting to work with PBP ...
The second is, AT LAST, the ability to call PBPL from the MPLAB Project window.


This " MPLAB compatibility release " ( What it was looked for, at first ...) , to me , REALLY is far too expensive ...

Deceived ??? ... YES, for sure !!!

Alain

[Charles Linquis]

Is there anyone compiling a list of known bugs in 2.60? Like Darrel, I find the improvements worthwhile, but my "base" code is so large and uses pretty much every possible instruction (sometimes in weird ways) that I can't easily do a full regression test.

But a known bug list would help me figure out what to test first.

[Acetronics2]

Hi, Charles

+1 for the bugs list ...

LOL ( Generally, the bug list is available with the next Upgrade ... eventually patch !!! )

Alain

[rsocor01]

Ioannis,

The PBP 2.5 manual in pdf or html format can be downloaded for free from the website melabs.com. So, I thought they probably posted the new manual so people can take a look at the new goodies before buying it.

All,
Yes, mecanique or whoever writes PBP is probably working in their buglist before releasing a patch with all the fixes. In the meanwhile, to avoid new headaches I will continue using my "old" PBP 2.5.

Robert

[Archangel]

You should have a separate installation for every version that you own.

MicroCode Studio recognizes the different versions and puts a Drop-Down box next to the "Compile" button.
You can select which version you want to compile with.
And when you want to play with 2.60 you can.

The ArrayRead/ArrayWrite statements alone make 2.60 worth it.
But there's so much more beyond that.

My installations look something like this ...
C:\PIC\
C:\PIC\PBP245\
C:\PIC\PBP246\
C:\PIC\PBP247\
C:\PIC\PBP250\
C:\PIC\PBP250c\
C:\PIC\PBP260b1\
C:\PIC\PBP260\

I probably will do that, ArrayRead/ArrayWrite, was why I bought the upgrade, haven't figured out how to use the yet, the DO Loop sort of ticked me off, have to edit all my old programs, honestly i didn't know that separate installations could reside together.