Thanks for a very nice compiler. I installed it yesterday and have some observations and a problem/question. First the problem. I am compiling with GCBasic, then using MPASM to assemble and link (to use the simulator). After some errors fixed by ignoring case, I have to turn off abort on errors to get it to assemble. Here is what I get for every demo code I try so far:
Executing: "C:\PIC\Microchip\MPASM Suite\MPAsmWin.exe" /q /p16F877A "compiled.asm" /l"compiled.lst" /e"compiled.err" /c-
Message[302] C:\PIC\GCBASIC\COMPILED.ASM 54 : Register in operand not in bank 0. Ensure that bank bits are correct.
Message[302] C:\PIC\GCBASIC\COMPILED.ASM 380 : Register in operand not in bank 0. Ensure that bank bits are correct.
Message[302] C:\PIC\GCBASIC\COMPILED.ASM 384 : Register in operand not in bank 0. Ensure that bank bits are correct.
Message[302] C:\PIC\GCBASIC\COMPILED.ASM 385 : Register in operand not in bank 0. Ensure that bank bits are correct.
Message[302] C:\PIC\GCBASIC\COMPILED.ASM 386 : Register in operand not in bank 0. Ensure that bank bits are correct.
Message[302] C:\PIC\GCBASIC\COMPILED.ASM 387 : Register in operand not in bank 0. Ensure that bank bits are correct.
Loaded C:\PIC\GCBASIC\compiled.COD.
BUILD SUCCEEDED: Wed Feb 07 18:46:48 2007
It won't succeed if I don't ignore it, and although I haven't burned it, and I'm new to the simulator, it seems to be fine in simulation. Why this error? GCBasic's .asm file seems to have something MPASM doesn't like.
Now the comments. Using Crimson with the key files is great. I initially had problems with it compiling and remembered I had turned off 8.3 support (XPsp1) long ago. You can get around that and use real names if you put the arguments line in Crimson preferences in quotes. No need to use 8.3 for anything...
There definitely needs to be more tutorial, and I'd be willing to write one, once I figure things out myself. I'm new to PICs and to the MP IDE, but I could keep track of what I trip over or find difficult... Maybe point me to where I could get myself up to speed quickly (as many places as possible) so I don't write a tutorial that's all wrong. ;)
Anyway, I hope you let me know what MPASM is trying to say about the compiled code and thanks.
Skip
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Those are just messages that MPASM always generates, regardless of whether the bank bits are set correctly or not. It is generally safe to ignore any messages (error number 3xx), unless the program is not working properly on the PIC.
The page about setting up Crimson Editor was not changed when support for non-8.3 filenames was added to GCBASIC. This will be dealt with in a few days time when I release the next version of GCBASIC.
If you could prepare a tutorial, then it would certainly be most welcome. Of course, there is no obligation. Also, Russ has been working on a list of things that can trip up beginners - I'll post this online soon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for a very nice compiler. I installed it yesterday and have some observations and a problem/question. First the problem. I am compiling with GCBasic, then using MPASM to assemble and link (to use the simulator). After some errors fixed by ignoring case, I have to turn off abort on errors to get it to assemble. Here is what I get for every demo code I try so far:
Executing: "C:\PIC\Microchip\MPASM Suite\MPAsmWin.exe" /q /p16F877A "compiled.asm" /l"compiled.lst" /e"compiled.err" /c-
Message[302] C:\PIC\GCBASIC\COMPILED.ASM 54 : Register in operand not in bank 0. Ensure that bank bits are correct.
Message[302] C:\PIC\GCBASIC\COMPILED.ASM 380 : Register in operand not in bank 0. Ensure that bank bits are correct.
Message[302] C:\PIC\GCBASIC\COMPILED.ASM 384 : Register in operand not in bank 0. Ensure that bank bits are correct.
Message[302] C:\PIC\GCBASIC\COMPILED.ASM 385 : Register in operand not in bank 0. Ensure that bank bits are correct.
Message[302] C:\PIC\GCBASIC\COMPILED.ASM 386 : Register in operand not in bank 0. Ensure that bank bits are correct.
Message[302] C:\PIC\GCBASIC\COMPILED.ASM 387 : Register in operand not in bank 0. Ensure that bank bits are correct.
Loaded C:\PIC\GCBASIC\compiled.COD.
BUILD SUCCEEDED: Wed Feb 07 18:46:48 2007
It won't succeed if I don't ignore it, and although I haven't burned it, and I'm new to the simulator, it seems to be fine in simulation. Why this error? GCBasic's .asm file seems to have something MPASM doesn't like.
Now the comments. Using Crimson with the key files is great. I initially had problems with it compiling and remembered I had turned off 8.3 support (XPsp1) long ago. You can get around that and use real names if you put the arguments line in Crimson preferences in quotes. No need to use 8.3 for anything...
There definitely needs to be more tutorial, and I'd be willing to write one, once I figure things out myself. I'm new to PICs and to the MP IDE, but I could keep track of what I trip over or find difficult... Maybe point me to where I could get myself up to speed quickly (as many places as possible) so I don't write a tutorial that's all wrong. ;)
Anyway, I hope you let me know what MPASM is trying to say about the compiled code and thanks.
Skip
Those are just messages that MPASM always generates, regardless of whether the bank bits are set correctly or not. It is generally safe to ignore any messages (error number 3xx), unless the program is not working properly on the PIC.
The page about setting up Crimson Editor was not changed when support for non-8.3 filenames was added to GCBASIC. This will be dealt with in a few days time when I release the next version of GCBASIC.
If you could prepare a tutorial, then it would certainly be most welcome. Of course, there is no obligation. Also, Russ has been working on a list of things that can trip up beginners - I'll post this online soon.