2018-09-28 22:06:35 +00:00
|
|
|
; Copyright 2018 David Schmidt. All Rights Reserved.
|
|
|
|
|
; See the LICENSE.txt file for distribution terms (Apache 2.0).
|
|
|
|
|
;
|
|
|
|
|
; Source: SOS programmer's guide
|
Optionally treat BRKs as two-byte instructions
Early data sheets listed BRK as one byte, but RTI after a BRK skips
the following byte, effectively making BRK a 2-byte instruction.
Sometimes, such as when diassembling Apple /// SOS code, it's handy
to treat it that way explicitly.
This change makes two-byte BRKs optional, controlled by a checkbox
in the project settings. In the system definitions it defaults to
true for Apple ///, false for all others.
ACME doesn't allow BRK to have an arg, and cc65 only allows it for
65816 code (?), so it's emitted as a hex blob for those assemblers.
Anyone wishing to target those assemblers should stick to 1-byte mode.
Extension scripts have to switch between formatting one byte of
inline data and formatting an instruction with a one-byte operand.
A helper function has been added to the plugin Util class.
To get some regression test coverage, 2022-extension-scripts has
been configured to use two-byte BRK.
Also, added/corrected some SOS constants.
See also issue #44.
2019-10-09 21:55:56 +00:00
|
|
|
; SOS Reference Manual, Volume 2 (Apple 1982)
|
2018-09-28 22:06:35 +00:00
|
|
|
|
Optionally treat BRKs as two-byte instructions
Early data sheets listed BRK as one byte, but RTI after a BRK skips
the following byte, effectively making BRK a 2-byte instruction.
Sometimes, such as when diassembling Apple /// SOS code, it's handy
to treat it that way explicitly.
This change makes two-byte BRKs optional, controlled by a checkbox
in the project settings. In the system definitions it defaults to
true for Apple ///, false for all others.
ACME doesn't allow BRK to have an arg, and cc65 only allows it for
65816 code (?), so it's emitted as a hex blob for those assemblers.
Anyone wishing to target those assemblers should stick to 1-byte mode.
Extension scripts have to switch between formatting one byte of
inline data and formatting an instruction with a one-byte operand.
A helper function has been added to the plugin Util class.
To get some regression test coverage, 2022-extension-scripts has
been configured to use two-byte BRK.
Also, added/corrected some SOS constants.
See also issue #44.
2019-10-09 21:55:56 +00:00
|
|
|
*SYNOPSIS Apple /// Sophisticated Operating System constants.
|
2018-09-28 22:06:35 +00:00
|
|
|
|
|
|
|
|
; SOS MLI function codes.
|
|
|
|
|
*TAG SOS-MLI-Functions
|
|
|
|
|
|
2018-09-28 23:43:33 +00:00
|
|
|
SOS_REQUEST_SEG = $40
|
|
|
|
|
SOS_FIND_SEG = $41
|
|
|
|
|
SOS_CHANGE_SEG = $42
|
|
|
|
|
SOS_GET_SEG_INFO = $43
|
|
|
|
|
SOS_GET_SEG_NUM = $44
|
|
|
|
|
SOS_RELEASE_SEG = $45
|
2018-09-28 22:06:35 +00:00
|
|
|
|
Optionally treat BRKs as two-byte instructions
Early data sheets listed BRK as one byte, but RTI after a BRK skips
the following byte, effectively making BRK a 2-byte instruction.
Sometimes, such as when diassembling Apple /// SOS code, it's handy
to treat it that way explicitly.
This change makes two-byte BRKs optional, controlled by a checkbox
in the project settings. In the system definitions it defaults to
true for Apple ///, false for all others.
ACME doesn't allow BRK to have an arg, and cc65 only allows it for
65816 code (?), so it's emitted as a hex blob for those assemblers.
Anyone wishing to target those assemblers should stick to 1-byte mode.
Extension scripts have to switch between formatting one byte of
inline data and formatting an instruction with a one-byte operand.
A helper function has been added to the plugin Util class.
To get some regression test coverage, 2022-extension-scripts has
been configured to use two-byte BRK.
Also, added/corrected some SOS constants.
See also issue #44.
2019-10-09 21:55:56 +00:00
|
|
|
SOS_SET_FENCE = $60
|
|
|
|
|
SOS_GET_FENCE = $61
|
|
|
|
|
SOS_SET_TIME = $62
|
|
|
|
|
SOS_GET_TIME = $63
|
|
|
|
|
SOS_GET_ANALOG = $64
|
|
|
|
|
; SOS ref: "TERMINATE"
|
|
|
|
|
; SOS ref: "No errors are possible. This is an excellent call for beginners."
|
2018-09-28 23:43:33 +00:00
|
|
|
SOS_QUIT = $65
|
2018-09-28 22:06:35 +00:00
|
|
|
|
2018-09-28 23:43:33 +00:00
|
|
|
SOS_READBLOCK = $80
|
|
|
|
|
SOS_WRITEBLOCK = $81
|
|
|
|
|
SOS_D_STATUS = $82
|
|
|
|
|
SOS_D_CONTROL = $83
|
|
|
|
|
SOS_GET_DEV_NUM = $84
|
|
|
|
|
SOS_D_INFO = $85
|
2018-09-28 22:06:35 +00:00
|
|
|
|
2018-09-28 23:43:33 +00:00
|
|
|
SOS_CREATE = $C0
|
|
|
|
|
SOS_DESTROY = $C1
|
|
|
|
|
SOS_RENAME = $C2
|
|
|
|
|
SOS_SET_FILE_INFO = $C3
|
|
|
|
|
SOS_GET_FILE_INFO = $C4
|
|
|
|
|
SOS_VOLUME = $C5
|
|
|
|
|
SOS_SET_PREFIX = $C6
|
|
|
|
|
SOS_GET_PREFIX = $C7
|
|
|
|
|
SOS_OPEN = $C8
|
|
|
|
|
SOS_NEWLINE = $C9
|
Optionally treat BRKs as two-byte instructions
Early data sheets listed BRK as one byte, but RTI after a BRK skips
the following byte, effectively making BRK a 2-byte instruction.
Sometimes, such as when diassembling Apple /// SOS code, it's handy
to treat it that way explicitly.
This change makes two-byte BRKs optional, controlled by a checkbox
in the project settings. In the system definitions it defaults to
true for Apple ///, false for all others.
ACME doesn't allow BRK to have an arg, and cc65 only allows it for
65816 code (?), so it's emitted as a hex blob for those assemblers.
Anyone wishing to target those assemblers should stick to 1-byte mode.
Extension scripts have to switch between formatting one byte of
inline data and formatting an instruction with a one-byte operand.
A helper function has been added to the plugin Util class.
To get some regression test coverage, 2022-extension-scripts has
been configured to use two-byte BRK.
Also, added/corrected some SOS constants.
See also issue #44.
2019-10-09 21:55:56 +00:00
|
|
|
; SOS ref: "READ"
|
2018-09-28 23:43:33 +00:00
|
|
|
SOS_READFILE = $CA
|
Optionally treat BRKs as two-byte instructions
Early data sheets listed BRK as one byte, but RTI after a BRK skips
the following byte, effectively making BRK a 2-byte instruction.
Sometimes, such as when diassembling Apple /// SOS code, it's handy
to treat it that way explicitly.
This change makes two-byte BRKs optional, controlled by a checkbox
in the project settings. In the system definitions it defaults to
true for Apple ///, false for all others.
ACME doesn't allow BRK to have an arg, and cc65 only allows it for
65816 code (?), so it's emitted as a hex blob for those assemblers.
Anyone wishing to target those assemblers should stick to 1-byte mode.
Extension scripts have to switch between formatting one byte of
inline data and formatting an instruction with a one-byte operand.
A helper function has been added to the plugin Util class.
To get some regression test coverage, 2022-extension-scripts has
been configured to use two-byte BRK.
Also, added/corrected some SOS constants.
See also issue #44.
2019-10-09 21:55:56 +00:00
|
|
|
; SOS ref: "WRITE"
|
2018-09-28 23:43:33 +00:00
|
|
|
SOS_WRITEFILE = $CB
|
|
|
|
|
SOS_CLOSE = $CC
|
|
|
|
|
SOS_FLUSH = $CD
|
|
|
|
|
SOS_SET_MARK = $CE
|
|
|
|
|
SOS_GET_MARK = $CF
|
|
|
|
|
SOS_SET_EOF = $D0
|
|
|
|
|
SOS_GET_EOF = $D1
|
|
|
|
|
SOS_SET_LEVEL = $D2
|
|
|
|
|
SOS_GET_LEVEL = $D3
|
