The CONFIG command is new. Search the PBP3 subforum for details and your manual.
Robert
The CONFIG command is new. Search the PBP3 subforum for details and your manual.
Robert
Robert,
Are you referring to the #CONFIG marker to specify an assembly language block as mentioned in the migration notes? I've read through the migration notes reasonably thoroughly and I can't recall it mentioning "config" being used for anything else? To me, the error doesn't appear to be pointing any fingers at "Config" directly, but more to an omission in one of the support files?
Regards,
Troy
I don't have 3.0 yet, I'm only going by the message you posted. Most of the migration problems come from changing the CONFIGs.
Your best bet is to post your code. Help those with the answers to help you.
Robert
Demon,
Here's an example:
Code:Define OSC 24 ANSEL = 0 'All ports digital ANSELH = 0 'All ports digital TRISC.3 = 0 pause 100 loop1: DTMFout PortC.3,[0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15] Goto loop1
As you can see, very simple example with no calls to assembler or anything complex. The simple sample programs provided with PBP3 also produces the same error too.
Thanks,
Troy
BTW: This is the screen grab I get when I click on the Error Message:
Troy
Define must be in CAPS for it to work. i.e. #DEFINE OSC 24
The editor that came with PBP3 -- Microcode Studio MCSX (the apparent successor to MCS) -- appears to automatically adjust/correct the "DEFINE" to lowercase. I'm assuming this is intentional??? Nevertheless, it's not the cause of the compiling error as the error still appears even if I remove that entire line from the code.
Regards,
Troy
Bookmarks