FREQOUT compiler error on USB Pic

[skimask]

But now when i use FREQOUT command in my USB script i get this error:
"Warning[202] \PBP\PBPPIC18.LIB 1239: argument out of range. least significant bits used."

Generally, it means you're trying to stuff a WORD variable into a BYTE register.

[mindthomas]

Generally, it means you're trying to stuff a WORD variable into a BYTE register.

Ohh, but why? The code line is this:

FREQOUT buzzer,1000,2000	'Freq=262 Hz

[Bruce]

Open your pbppic18.lib and scroll down to line number 1239. Where you see addlw (sintable) change it to addlw low(sintable)

[Dave]

Bruce, What version of PBP do you have there? I just checked my latest version w/patch and find no instance of this.

Dave Purola,
N8NTA

[Bruce]

Hi Dave,

I have the latest version + I keep all older versions for tech support. v2.47 is the version
I noticed the low missing in. It works even without the mod, but always returns the warning.

[mindthomas]

Open your pbppic18.lib and scroll down to line number 1239. Where you see addlw (sintable) change it to addlw low(sintable)

Thanks.. It worked, and how did you know that?

Another thing, how can i put two bytes together, because i need to select the FREQUENCE with USB, but i can only go up to 255, so how can i make so i can send a higher value?

[skimask]

Thanks.. It worked, and how did you know that?

Another thing, how can i put two bytes together, because i need to select the FREQUENCE with USB, but i can only go up to 255, so how can i make so i can send a higher value?

Word, highbyte, lowbyte, byte1, byte0, and so on...
It's all in the book...

[mindthomas]

Word, highbyte, lowbyte, byte1, byte0, and so on...
It's all in the book...

Ya, but when i need to send it over USB?

[skimask]

Ya, but when i need to send it over USB?

Same thing applies going either sending or receiving...

variableword var word
variable_highbyte var byte
variable_lowbyte var byte

variableword = (variable_highbyte * 256) + variable_lowbyte
variable_lowbyte = variableword.lowbyte
variable_highbyte = variableword.highbyte

[mindthomas]

Open your pbppic18.lib and scroll down to line number 1239. Where you see addlw (sintable) change it to addlw low(sintable)

How did you know that i should do that?
Just want to know if it happends again.

[skimask]

How did you know that i should do that?
Just want to know if it happends again.

If you've got MCS setup to dump out a .lst file with all the options turned on (usually fairly HUGE files), you can usually scroll thru it or search it for the phrase 'ERROR', then using a bit of deductive logic, can usually trace that back to your original problem...whether it be a problem with the typist, an include file, a macro, whatever.

[Bruce]

How did you know that i should do that?

The warning message tells you where the problem is. Warning[202] \PBP\PBPPIC18.LIB 1239

I looked in the library at the line # indicated by the warning message. In v2.50a there was no problem. In v2.47 this was missing, so it's a simple fix to get rid of the warning.

It also helps if you know assembler...;o]

[skimask]

The warning message tells you where the problem is. Warning[202] \PBP\PBPPIC18.LIB 1239

Ya know, I never made the correlation between the 'PBPPIC18.LIB' and the '1239' in the error messages. I always did it the hard way described above.
Thanks for the tidbit...

[mindthomas]

The warning message tells you where the problem is. Warning[202] \PBP\PBPPIC18.LIB 1239

I looked in the library at the line # indicated by the warning message. In v2.50a there was no problem. In v2.47 this was missing, so it's a simple fix to get rid of the warning.

It also helps if you know assembler...;o]

Ohh, it's because i have PBP 2.46!