As many times as this DEFINE in particular gets brought up you'd think MeLabs would at least give you an error during compile if the two defines XXX don't match. Seems like it should generate some kind of error.
As many times as this DEFINE in particular gets brought up you'd think MeLabs would at least give you an error during compile if the two defines XXX don't match. Seems like it should generate some kind of error.
You can DEFINE anything you want for use with your assembly language routines.
PBP has no way to know if you are using 'osc' in your routines, or if you didn't capitalize 'OSC' for PBP.
It is unfortunately up to you to get it right.
DT
Never good to rely on lowest common denominator. That reliance means this thread will be recreated many more times.
Henrik was right in his original post on this.
It just occurred to me ***DUH*** that just because the editor automatically makes "define" into lower case, doesn't mean the OSC is supposed to be lower case as well.
With MicroCode Studio the only syntax that works is "define OSC 8"
Nice to have the 8mhz clock running for more fun experiments.
BTW:
I just got a couple 18F2550 chips.
Looking forward to playing with them!!! :-]
Bookmarks