Darrel's latest 16 bit averaging routine?

[jellis00]

Are you getting ... ?

Symbol not previously defined (WRITE)

No, I am getting the following error on attempts to compile:
"Error[111] c:\program files\mechanique\mcs\test_average.mac 296 : Missing symbol"

Could this be due to the bug in PICBASIC Pro version 2.6 which is the version I am using?

[Darrel Taylor]

Using the code from post #1 with PBP 2.60, the only error I get is ...
Symbol not previously defined (WRITE)

If I add the line ...
DEFINE WRITE_USED 1

Then it compiles without error.

To find where the problem is, open the
c:\program files\mechanique\mcs\test_average.LST file with notepad.

Search for error[111].
The line immediately following the error should indicate where the problem is.
<br>

[Acetronics2]

Hi, Darrel

Without opening files, but the manual ... should make it too !

( range var ??? )

did I miss something here ???

BTW: MPLAB does not show any errors ...

Alain

[jellis00]

Using the code from post #1 with PBP 2.60, the only error I get is ...
Symbol not previously defined (WRITE)

If I add the line ...
DEFINE WRITE_USED 1

Then it compiles without error.

Adding the DEFINE WRITE_USED 1 statement to my code eliminated the error I was seeing and it appears the compile was declared "Successful", but I still get this additional error after making that correction:
"Error[108] : Illegal character (1)" which points in the .lst file to a LIST statement in the assembly listing. I don't know what this error is trying to tell me, and it must not be a fatal error because it still compiled and assembled. Can you tell me what this error is telling me to fix?

[jellis00]

Adding the DEFINE WRITE_USED 1 statement to my code eliminated the error I was seeing and it appears the compile was declared "Successful", but I still get this additional error after making that correction:
"Error[108] : Illegal character (1)" which points in the .lst file to a LIST statement in the assembly listing.

I notice now that although it appeared the file compiled, it did not assemble correctly because I see that the .hex file details didn't update the time stamp of the file after the compile. Therefore, the Error[108] was fatal to the creation of a new .hex file. Any ideas why this might be happening?

It appears to me that most of these problems are due to the WRITE bug in 2.6, which is driving me crazy because none of my write statement I typically insert in my code for test purposes are actually writing values to EEPROOM...even with the DEFINE WRITE_USED 1 statement included.

[Darrel Taylor]

Apparently, you have modified the code from what was in post #1.

First off, don't worry about the WRITE bug in 2.60.
It is a very minor issue that only happens if you ONLY have WORD variables in your WRITE statements.

If you also write from a BYTE variable anywhere in your program, then the problem goes away. It's not normal for people to only write from words, so I think the error slipped thru.

If you do have WRITE's with BYTE's, then the DEFINE WRITE_USED 1 will generate the err[108] that you now see. Which is why I say that the program is not the same as before.

If you are now using BYTE's in your WRITE's, delete the DEFINE, and compile again.

If you get the old error[111] back, please send me the .LST file to darrel att pbpgroup.com.
<br>

[jellis00]

Thanks, Darrell! I finally understand the symptoms and true workarounds of the WRITE WORD bug. I had only WORD variables being written in the first version, hence the ERROR[111]. Then, you were right..I inserted a WRITE Byte statement without removing the DEFINE ...hence the ERROR[108]. Now I have a superfolous WRITE Byte statement just to avoid the bug, and have removed the DEFINE statement and everything works. Thanks again.

Any word as to when their will be a patch for the v2.6 WRITE bug? I work with a lot of WORD variables, and would like to see it soon so I don't have to insert a superfolous WRITE byte statement.

[Darrel Taylor]

Thanks, Darrell! I finally understand the symptoms and true workarounds of the WRITE WORD bug.

Excellent!

Any word as to when their will be a patch for the v2.6 WRITE bug?

I know there is a patch in the works, but I do not know when it will be.

Keep an eye on this page for news on the issues.
http://melabs.com/support/pbpissues.htm