Using ATMEL AVRASM2 to link and generate the HEX file is a great way to be assured that the ASM generated by GCBASIC is valid. The resulting HEX should be no different from the HEX generated by GCASM but the extra quality check is worth the extra milliseconds in the compilation process.
The other reason for using the ASM is to load into ATMEL AS6/AS7 to debug program. To make this all work. Install AS6 from the FILES TAB in this forum.
However, if you want to use AVRASM2 for the extra quality check and then use the HEX in OshenSoft Simulator IDE you will need the LST to be created by AVRASM2. I have shown below the change you may need to make to your USE.INI file to instruct AVRASM2 to generate a HEX and a LST file.
This configuration for AVRASM2, shown above, will be the default setting from build 1377. I am thinking producing the LST is always needed. The configuration prior to this build did not produce an LST.
Enjoy
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Using ATMEL AVRASM2 to link and generate the HEX file is a great way to be assured that the ASM generated by GCBASIC is valid. The resulting HEX should be no different from the HEX generated by GCASM but the extra quality check is worth the extra milliseconds in the compilation process.
The other reason for using the ASM is to load into ATMEL AS6/AS7 to debug program. To make this all work. Install AS6 from the FILES TAB in this forum.
However, if you want to use AVRASM2 for the extra quality check and then use the HEX in OshenSoft Simulator IDE you will need the LST to be created by AVRASM2. I have shown below the change you may need to make to your USE.INI file to instruct AVRASM2 to generate a HEX and a LST file.
This configuration for AVRASM2, shown above, will be the default setting from build 1377. I am thinking producing the LST is always needed. The configuration prior to this build did not produce an LST.
Enjoy