Hi Carmyex,
First I have to make a remark that the error message is about two ASSEMBLER CONTROLS/DIRECTIVES ($INCLUDE and $MOD) but combined in only one error count.
No listing file generated by assembler. (Invalid $INCLUDE directive? Semi-colon after $MOD directive?)
Assembler results: 1 - Errors, 0 - Warnings
There is no $INCLUDE assembler control/directive in the code that you posted. If you missed copying some parts of your code, you can insert it in your reply. On the other hand, it is also possible that the "Invalid $INCLUDE directive?" message was just induced by the "$MOD" assembler control/directive.
The main problem that I can infer from your post is that the code is written for the MetaLink Cross Assembler but the Development / Code Generation Tools that you are using employs a different assembler. The Metalink Cross Assembler does not classify $INCLUDE and $MOD52 as part of its ASSEMBLER DIRECTIVES (e.g., ORG, EQU). Instead, $INCLUDE and $MOD52 are part of Metalink's ASSEMBLER CONTROLS. Notice that the error message used the term directive for $INCLUDE and $MOD.
No listing file generated by assembler. (Invalid $INCLUDE directive? Semi-colon after $MOD directive?)
Try replacing the line
$MOD52 ; This includes 8052 definitions for the Metalink assembler
with
; This includes 8052 definitions for the Metalink assembler
$MOD52
If the assembler still issues errors about this line, comment out the line containing the $MOD52 assembler control/directive
from
$MOD52 ; This includes 8052 definitions for the Metalink assembler
to
;$MOD52 ; This includes 8052 definitions for the Metalink assembler
Your code might be successfully assembled without the need for the $MOD52 control/directive especially if you are using a newer Development / Code Generation Tools.
Best regards,
G. Goodwin
