Hi all, I am a total virgin at this. I have installed GCBasic and Crimson Editor and set it up as out lined in "Getting Started with GCBasic."
It seems to work as I am able to generate a "compiled.asm" file with the correct data in it. In order to load this to a PIC I must have a .hex file. How do I generate This?
Also, the highlighter does not work for GCBasic, but others work fine. I have the correct .key and .spc files in the crimson directory. Any ideas
Thank you in advance, Ed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not an expert in gcbasic, but if all is correctly instaled and configure you should have the .hex file generated.. if you haven't it, perhaps you need install mpasm, gpasm, or use the built-in assembler...
I'm not sure about how to do in windows, but there must be a config file: gcbasic.ini or a "sample gcbasic.ini", there you can set the assembler you are using, the lines involved are like this (this are mine):
'Assembler to use
'MPASM settings
'Filename, is relative to GCBASIC directory unless a full path is given
Nobody/Anonymous (nobody), you were correct. There is a MAKEBAT that had the wrong path to the gpasm file. I changed the path on installation. It now works ok and the .hex file appeared.
Thank you very much, Ed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For the Crimson Editor highlight to work in the automatic mode you have to start putting extensions onto your file names. This, even tho the command code file is set up, but Crimson doesn't look that far! So make a copy of one of the extension files, and rename it say .gbc. Forget what happens next, maybe edit a couple of lines to point to the gbc code file, if in doubt Google it, because that's how I found out. Next time you make a file blinkLED.gcb and you are good to go, or edit with the extension on a existing file. After a couple try's, and it was back to the old ways for me.
Kent
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all, I am a total virgin at this. I have installed GCBasic and Crimson Editor and set it up as out lined in "Getting Started with GCBasic."
It seems to work as I am able to generate a "compiled.asm" file with the correct data in it. In order to load this to a PIC I must have a .hex file. How do I generate This?
Also, the highlighter does not work for GCBasic, but others work fine. I have the correct .key and .spc files in the crimson directory. Any ideas
Thank you in advance, Ed.
I'm not an expert in gcbasic, but if all is correctly instaled and configure you should have the .hex file generated.. if you haven't it, perhaps you need install mpasm, gpasm, or use the built-in assembler...
I'm not sure about how to do in windows, but there must be a config file: gcbasic.ini or a "sample gcbasic.ini", there you can set the assembler you are using, the lines involved are like this (this are mine):
'Assembler to use
'MPASM settings
'Filename, is relative to GCBASIC directory unless a full path is given
Assembler = gpasm
'Parameters
AssemblerParams = --hex-format inhx32 --radix DEC --warning 0 --ignore-case --force-list "%FileName%"
'GCASM settings
'Assembler = GCASM
'No params needed for GCASM
If you want to use buil-in assembler, just coment all theese line except this:
Assembler = GCASM
Have a look to any "readme" or file that looks to have information...
Greetings
Nobody/Anonymous (nobody), you were correct. There is a MAKEBAT that had the wrong path to the gpasm file. I changed the path on installation. It now works ok and the .hex file appeared.
Thank you very much, Ed.
For the Crimson Editor highlight to work in the automatic mode you have to start putting extensions onto your file names. This, even tho the command code file is set up, but Crimson doesn't look that far! So make a copy of one of the extension files, and rename it say .gbc. Forget what happens next, maybe edit a couple of lines to point to the gbc code file, if in doubt Google it, because that's how I found out. Next time you make a file blinkLED.gcb and you are good to go, or edit with the extension on a existing file. After a couple try's, and it was back to the old ways for me.
Kent