Program compiles and writes but can't run

[jellis00]

Joe S.,
Interestingly, when I copied this code int a Workspace project I created in MPLAB with PICkit2 set as programmer and PICBASIC Pro set as language, it compiles without any errors and will program into the PIC16F690 via the PICkit2 programming interface. It work as advertised this way.
However, if I copy the same code into MCS and try to compile it (with the PIC16F690.incl either normal or edited per you instructions) it creates all of the same 113 and 118 errors about not licking the symbols or overwriting....the original problem I observed.
I wanted to use the MCS/PICkit2 programming environment, but if I can't get it to compile the programs I will just have to use the MPLAB environment setup to operate with PICkit2. The reason I wanted to use MCS is because of its context help feature on PICBASIC syntax. I guess I can still write programs in MCS and then copy them into a Workspace on MPLAB for programming, but this is extra steps I wanted to avoid.

[jellis00]

Joe S.,
You didn't answer my one question in an earlier email regarding your instructions "The other MAIN reason is not having selected the correct PIC in Microcode Studio...." Since this may be causing the unrecognized symobl error, can you please tell me how to make the PIC selection in MCS? I looked thru MCS and couldn't see how to do that.

[Archangel]

Joe S.,
Interestingly, when I copied this code int a Workspace project I created in MPLAB with PICkit2 set as programmer and PICBASIC Pro set as language, it compiles without any errors and will program into the PIC16F690 via the PICkit2 programming interface. It work as advertised this way.
However, if I copy the same code into MCS and try to compile it (with the PIC16F690.incl either normal or edited per you instructions) it creates all of the same 113 and 118 errors about not licking the symbols or overwriting....the original problem I observed.
I wanted to use the MCS/PICkit2 programming environment, but if I can't get it to compile the programs I will just have to use the MPLAB environment setup to operate with PICkit2. The reason I wanted to use MCS is because of its context help feature on PICBASIC syntax. I guess I can still write programs in MCS and then copy them into a Workspace on MPLAB for programming, but this is extra steps I wanted to avoid.

It is funny, the program never failed to compile and load from MCS through PICKit2. That said, it did say cancelled at the bottom, until I cut and pasted it into a new page in MCS and saved it as another name, it then compiled and said success. You and I might both need to reinstall MCS. The other code example I gave you . . . Did it work for you in MCS ?

[jellis00]

The other code example I gave you . . . Did it work for you in MCS ?

Joe S., No, neither of the code sets would compile in MCS.

However, I think MACKTRAP led me to the solution. Once I did turn on the toolbar and set the device to PIC16F690 I was able to compile and program from MCS via PICkit2 for the code sets Joe S. provided as well as my other code samples I could not get to run.

Thanks so much to both of you for helping me resolve this problem.

[mackrackit]

MACKTRAP

??????

I have heard worse.