WikiTI - User contributions [en]

Programming under Unix-like operating systems

2007-12-31T22:57:10Z

Sigma: /* WLA DX */ ...

Here are the different tools at your disposal:

= General Overviews =

==Emulators==
* [http://lpg.ticalc.org/prj_tilem/ TilEm]
* VirtualTI through wine
* [[PindurTI]] through Wine
* [[PindurTI]] in non-interactive mode (with or without [http://kvince83.tengun.net/maxboard/viewtopic.php?t=2466 PTI frontend])

==Syntax highlighting==
Several editors have native or extensional support for editing Z80 assembly code with syntax highlighting:
* Kwrite and Kate can be made to syntax-highlight Z80 assembly with [http://www.ticalc.org/archives/files/fileinfo/391/39178.html the appropriate definition file]. The file must be placed in /usr/share/apps/katepart/syntax .
* SciTE and Emacs both have native modes for assembly code. For Emacs, one must make sure to turn on Font Lock mode as well.
* The [http://www.revsoft.org/phpBB2/viewforum.php?f=25 Z80 Assembly IDE] has simple syntax highlighting built-in.
* Users of Vim and WLA DX can use [http://sigma.unitedti.org/files/misc/z80.vim.bz2 this syntax file].

== Assembling ==

=== SPASM ===

'''Author''': Spencer Putt

'''Home Page''': [http://www.revsoft.org/phpBB2/viewforum.php?f=21 http://www.revsoft.org/phpBB2/viewforum.php?f=21]

SPASM is a portable Z80 assembler released under the GPL. Its distinguishing features are extremely fast assembly and powerful macro support. The output is only available in binary form, however with the use of [http://www.revsoft.org/phpBB2/viewforum.php?f=23 Wabbitsign], written by James Montelongo and Spencer Putt, it can easily be converted to any desired program type.

assembler foo.asm foo.bin
wabbit foo.bin foo.8xp

SPASM and Wabbitemu are included in [http://www.ticalc.org/archives/files/fileinfo/390/39009.html Z80 Assembly IDE 1.32] by burntfuse

=== tpasm ===

'''Author''': Todd Squires

'''Home page''': [http://www.sqrt.com/ http://www.sqrt.com/]

tpasm is a Free (GPL) assembler which supports the Z80 as well as the 6805, 6809, 68HC11, 6502, Sunplus, 8051, PIC, and AVR. It uses syntax very similar to ZMASM.

tpasm 1.2 does not support binary file output, but you can use ''objcopy'' (from the GNU binutils package) to convert its Intel Hex output into binary; e.g.

tpasm foo.asm -o intel foo.hex -l foo.lst
objcopy -I ihex foo.hex -O binary foo.bin

=== ASxxxx ===

'''Author''': Alan R. Baldwin

'''Home page''': [http://shop-pdp.kent.edu/ashtml/asxxxx.htm http://shop-pdp.kent.edu/ashtml/asxxxx.htm]

ASxxxx is a freeware assembler which supports the Z80 along with a large variety of other processors. It more closely resembles a modern PC assembler than a typical Z80 assembler, as it assembles each file into a relocatable object format which can then be linked with other files to produce the complete program. The linking is done by a separate program called ASlink (included with the package.)

To assemble and link a simple program you might do something like

asz80 -plogff foo.asm
aslink -u -b _CODE=0x9D95 -i foo.ihx foo.rel
objcopy -I ihex foo.ihx -O binary foo.bin

Note that the syntax is rather different from that of most Z80 assemblers. The important differences are
* Immediate values are marked with #.
* Indexed memory access is written as N(ix) rather than (ix+N).
* Constants are written differently: 0xAA, 0hAA, or $$AA for hexadecimal; 0o252, 0q252, or $&252 for octal; 0b10101010 or $%10101010 for binary.

For example,
ld hl,#str_hello
add a,3(ix)
xor #0x0f

There is also a modified version of ASxxxx distributed with the [http://sdcc.sf.net/ Small Device C Compiler]. This version is, if anything, more confusing to use due to the poorly-documented changes made by the SDCC team.

=== TASM ===

'''Author''': Thomas N. Anderson

'''Home page''': [http://home.comcast.net/~tasm/ http://home.comcast.net/~tasm/]

TASM is a shareware assembler which also supports a variety of processors.

There are several ways that you can use tasm under Linux:
* The TASM 3.1 for Linux shareware release is still in the wild. To use this you will need to enable "a.out" support in your kernel (it may be available as the module ''binfmt_aout''.) You will also need to obtain the ancient Linux libc version 4 (''not'' glibc) which can be found [http://ftp.linux.org.uk/pub/linux/libc/ here].
* You can use TASM 3.2 for Windows with [http://www.winehq.com Wine].
* You can pay the $40 and compile it yourself on the platform of your choice.

=== Brass ===
'''Author''': benryves

'''Home page''': [http://benryves.com/bin/brass/ http://benryves.com/bin/brass/]

Brass runs under Linux thanks to Mono.

=== Zasm ===
'''Author''': Steven Deprez

'''Home page''': [http://lpg.ticalc.org/prj_zasm/index.html http://lpg.ticalc.org/prj_zasm/index.html]

Zasm is an open source assembler that is almost fully compatible with Tasm and ZDS.

=== WLA DX ===
'''Author''': Ville Helin

'''Home page''': [http://www.villehelin.com/wla.html http://www.villehelin.com/wla.html]

WLA DX is another open-source (GNU GPL) cross-assembler with a primary focus on targeting video game consoles. It is a high-powered assembler with a wide variety of features such as, e.g. separate compilation, POSIX-like file I/O, and code sectioning. However it is cumbersome when assembling small projects, and semantics are unorthodox compared to other assemblers. (~ is the XOR operator, macro arguments are passed by value, etc.).

WLA DX has had an influence in the development of Brass.

=== Pasmo ===
'''Author''': Julián Albo

'''Home page''': [http://www.arrakis.es/~ninsesabe/pasmo/ http://www.arrakis.es/~ninsesabe/pasmo/]

Pasmo is another standalone Z80 cross-assembler with basic macro support, but without the ability to generate
relocatable object files. It is licensed under the GNU GPL, and exists as the package <tt>pasmo</tt> in the Debian pool.

=== z80asm ===
'''Author''': Bas Wijnen

'''Home page''': [http://savannah.nongnu.org/projects/z80asm/ http://savannah.nongnu.org/projects/z80asm/]

z80asm is a standalone Z80 cross-assembler similar in nature to Pasmo, in that it has macro support but cannot generate relocatable object files. It too is licensed under the GNU GPL (version 2 or later), and exists as the package <tt>z80asm</tt> in the Debian pool.

=== GNU as ===
'''Author''': the GNU binutils team

'''Home page''': [http://www.gnu.org/software/binutils/ http://www.gnu.org/software/binutils/]

Starting from version 2.17, the GNU assembler, part of the binutils package, is capable of cross-assembling Z80 code when configured for it at compile-time, such as with <tt>--target=z80-unknown-coff</tt>. binutils includes a powerful assembler and linker both, along with various utilities for handling object files, such as objcopy and objdump; for Z80, COFF is used for relocatable objects, with raw binary and Intel hex formats also supported. While this is probably one of the more powerful tools in the list for Z80 development, it also requires more work to start with, as the traditional way to get a cross-assembling binutils is to compile it oneself. Being a GNU package, binutils is naturally licensed under the GNU GPL (version 2 or later). Prepackaged binary versions of binutils are very common, but usually do not have cross-assembling capability.

==Sending programs to the calc==
* [http://www.ticalc.org/archives/files/fileinfo/374/37480.html TiLP-II] (requires [http://www.ticalc.org/archives/files/fileinfo/374/37479.html tilibs])
* [http://www.ticalc.org/archives/files/fileinfo/75/7588.html titranz] : commandline tool, only works for TI-83/TI-83+

= FreeBSD =
Much of the aforementioned software should compile independently without problem or with minor tweaking under FreeBSD, but it is best to utilize the ports collection whenever possible. Unfortunately, the current state of calculator-related software in the FreeBSD Ports Collection is lacking in variety.

* Development
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
|tpasm || 1.2_1 || devel/tpasm
|-
|z80asm || 1.6_1 || devel/z80asm
|-
|z80-asm || 0.1_1 || devel/z80-asm
|-
|TI-GCC || 0.96.b8 || devel/tigcc
|-
|libtifiles2 || 1.0.1 || devel/libtifiles2
|}

* Communications
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
|TiLP-II || 1.01 || comms/tilp2
|-
|libticables2 || 1.0.2 || comms/libticables2
|-
|libticalcs2 || 1.0.1 || comms/libticalcs2
|}

* Converters
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
|libticonv || 1.0.0 || converters/libticonv
|}

* Emulation
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
| TIEmu 2 || 2.08 || emulators/tiemu2
|}

= Mac OS X =
(Note that all of these assesments were made on a MacBook running 10.4.9 Intel. Mileage may vary on other versions and of course the Darwine stuff won't work on PPC.)

TiLP-II is known to compile and work properly with SilverLink and Direct USB cables with the 83+, 84+SE, and 89Ti, so there is no reason to believe it will not work with the other calculators. TI Connect X works well enough on Intel Macs even though it is not officially supported, however it seems to be more strict with the format of .8xk files than TiLP or TI Connect (Windows).

Brass works in Mono. Wabbitspasm compiles and works properly. ZDS works in Darwine.

TilEm compiles but seems to have some issues with multiple ROM versions. It is unclear to me if this is a problem with the build or TilEm itself. PindurTI is somewhat usable in Darwine: You must use the send.exe utility to send the ROM image, then it will emulate properly. However, it makes extensive use of the F-keys, including the ExposÃ© ones. Remapping the ExposÃ© keys is the only solution. TI FLASH Debugger runs in Darwine but the calculator windows are unskinned: You must either use the keyboard or click blindly in the window. The display output is fine, and other debugger windows appear to function properly. VirtualTI (2.5) should run OK after putting the ROM files somewhere Darwine knows about (I was lazy).

= Other Unixes =

This section is a stub. Please add it it.

Programming under Unix-like operating systems

2007-12-31T22:55:03Z

Sigma: /* WLA DX */ It's been resurrected.

Here are the different tools at your disposal:

= General Overviews =

==Emulators==
* [http://lpg.ticalc.org/prj_tilem/ TilEm]
* VirtualTI through wine
* [[PindurTI]] through Wine
* [[PindurTI]] in non-interactive mode (with or without [http://kvince83.tengun.net/maxboard/viewtopic.php?t=2466 PTI frontend])

==Syntax highlighting==
Several editors have native or extensional support for editing Z80 assembly code with syntax highlighting:
* Kwrite and Kate can be made to syntax-highlight Z80 assembly with [http://www.ticalc.org/archives/files/fileinfo/391/39178.html the appropriate definition file]. The file must be placed in /usr/share/apps/katepart/syntax .
* SciTE and Emacs both have native modes for assembly code. For Emacs, one must make sure to turn on Font Lock mode as well.
* The [http://www.revsoft.org/phpBB2/viewforum.php?f=25 Z80 Assembly IDE] has simple syntax highlighting built-in.
* Users of Vim and WLA DX can use [http://sigma.unitedti.org/files/misc/z80.vim.bz2 this syntax file].

== Assembling ==

=== SPASM ===

'''Author''': Spencer Putt

'''Home Page''': [http://www.revsoft.org/phpBB2/viewforum.php?f=21 http://www.revsoft.org/phpBB2/viewforum.php?f=21]

SPASM is a portable Z80 assembler released under the GPL. Its distinguishing features are extremely fast assembly and powerful macro support. The output is only available in binary form, however with the use of [http://www.revsoft.org/phpBB2/viewforum.php?f=23 Wabbitsign], written by James Montelongo and Spencer Putt, it can easily be converted to any desired program type.

assembler foo.asm foo.bin
wabbit foo.bin foo.8xp

SPASM and Wabbitemu are included in [http://www.ticalc.org/archives/files/fileinfo/390/39009.html Z80 Assembly IDE 1.32] by burntfuse

=== tpasm ===

'''Author''': Todd Squires

'''Home page''': [http://www.sqrt.com/ http://www.sqrt.com/]

tpasm is a Free (GPL) assembler which supports the Z80 as well as the 6805, 6809, 68HC11, 6502, Sunplus, 8051, PIC, and AVR. It uses syntax very similar to ZMASM.

tpasm 1.2 does not support binary file output, but you can use ''objcopy'' (from the GNU binutils package) to convert its Intel Hex output into binary; e.g.

tpasm foo.asm -o intel foo.hex -l foo.lst
objcopy -I ihex foo.hex -O binary foo.bin

=== ASxxxx ===

'''Author''': Alan R. Baldwin

'''Home page''': [http://shop-pdp.kent.edu/ashtml/asxxxx.htm http://shop-pdp.kent.edu/ashtml/asxxxx.htm]

ASxxxx is a freeware assembler which supports the Z80 along with a large variety of other processors. It more closely resembles a modern PC assembler than a typical Z80 assembler, as it assembles each file into a relocatable object format which can then be linked with other files to produce the complete program. The linking is done by a separate program called ASlink (included with the package.)

To assemble and link a simple program you might do something like

asz80 -plogff foo.asm
aslink -u -b _CODE=0x9D95 -i foo.ihx foo.rel
objcopy -I ihex foo.ihx -O binary foo.bin

Note that the syntax is rather different from that of most Z80 assemblers. The important differences are
* Immediate values are marked with #.
* Indexed memory access is written as N(ix) rather than (ix+N).
* Constants are written differently: 0xAA, 0hAA, or $$AA for hexadecimal; 0o252, 0q252, or $&252 for octal; 0b10101010 or $%10101010 for binary.

For example,
ld hl,#str_hello
add a,3(ix)
xor #0x0f

There is also a modified version of ASxxxx distributed with the [http://sdcc.sf.net/ Small Device C Compiler]. This version is, if anything, more confusing to use due to the poorly-documented changes made by the SDCC team.

=== TASM ===

'''Author''': Thomas N. Anderson

'''Home page''': [http://home.comcast.net/~tasm/ http://home.comcast.net/~tasm/]

TASM is a shareware assembler which also supports a variety of processors.

There are several ways that you can use tasm under Linux:
* The TASM 3.1 for Linux shareware release is still in the wild. To use this you will need to enable "a.out" support in your kernel (it may be available as the module ''binfmt_aout''.) You will also need to obtain the ancient Linux libc version 4 (''not'' glibc) which can be found [http://ftp.linux.org.uk/pub/linux/libc/ here].
* You can use TASM 3.2 for Windows with [http://www.winehq.com Wine].
* You can pay the $40 and compile it yourself on the platform of your choice.

=== Brass ===
'''Author''': benryves

'''Home page''': [http://benryves.com/bin/brass/ http://benryves.com/bin/brass/]

Brass runs under Linux thanks to Mono.

=== Zasm ===
'''Author''': Steven Deprez

'''Home page''': [http://lpg.ticalc.org/prj_zasm/index.html http://lpg.ticalc.org/prj_zasm/index.html]

Zasm is an open source assembler that is almost fully compatible with Tasm and ZDS.

=== WLA DX ===
'''Author''': Ville Helin

'''Home page''': [http://www.villehelin.com/wla.html]

WLA DX is another open-source (GNU GPL) cross-assembler with a primary focus on targeting video game consoles. It is a high-powered assembler with a wide variety of features such as, e.g. separate compilation, POSIX-like file I/O, and code sectioning. However it is cumbersome when assembling small projects, and semantics are unorthodox compared to other assemblers. (~ is the XOR operator, macro arguments are passed by value, etc.).

WLA DX has had an influence in the development of Brass.

=== Pasmo ===
'''Author''': Julián Albo

'''Home page''': [http://www.arrakis.es/~ninsesabe/pasmo/ http://www.arrakis.es/~ninsesabe/pasmo/]

Pasmo is another standalone Z80 cross-assembler with basic macro support, but without the ability to generate
relocatable object files. It is licensed under the GNU GPL, and exists as the package <tt>pasmo</tt> in the Debian pool.

=== z80asm ===
'''Author''': Bas Wijnen

'''Home page''': [http://savannah.nongnu.org/projects/z80asm/ http://savannah.nongnu.org/projects/z80asm/]

z80asm is a standalone Z80 cross-assembler similar in nature to Pasmo, in that it has macro support but cannot generate relocatable object files. It too is licensed under the GNU GPL (version 2 or later), and exists as the package <tt>z80asm</tt> in the Debian pool.

=== GNU as ===
'''Author''': the GNU binutils team

'''Home page''': [http://www.gnu.org/software/binutils/ http://www.gnu.org/software/binutils/]

Starting from version 2.17, the GNU assembler, part of the binutils package, is capable of cross-assembling Z80 code when configured for it at compile-time, such as with <tt>--target=z80-unknown-coff</tt>. binutils includes a powerful assembler and linker both, along with various utilities for handling object files, such as objcopy and objdump; for Z80, COFF is used for relocatable objects, with raw binary and Intel hex formats also supported. While this is probably one of the more powerful tools in the list for Z80 development, it also requires more work to start with, as the traditional way to get a cross-assembling binutils is to compile it oneself. Being a GNU package, binutils is naturally licensed under the GNU GPL (version 2 or later). Prepackaged binary versions of binutils are very common, but usually do not have cross-assembling capability.

==Sending programs to the calc==
* [http://www.ticalc.org/archives/files/fileinfo/374/37480.html TiLP-II] (requires [http://www.ticalc.org/archives/files/fileinfo/374/37479.html tilibs])
* [http://www.ticalc.org/archives/files/fileinfo/75/7588.html titranz] : commandline tool, only works for TI-83/TI-83+

= FreeBSD =
Much of the aforementioned software should compile independently without problem or with minor tweaking under FreeBSD, but it is best to utilize the ports collection whenever possible. Unfortunately, the current state of calculator-related software in the FreeBSD Ports Collection is lacking in variety.

* Development
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
|tpasm || 1.2_1 || devel/tpasm
|-
|z80asm || 1.6_1 || devel/z80asm
|-
|z80-asm || 0.1_1 || devel/z80-asm
|-
|TI-GCC || 0.96.b8 || devel/tigcc
|-
|libtifiles2 || 1.0.1 || devel/libtifiles2
|}

* Communications
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
|TiLP-II || 1.01 || comms/tilp2
|-
|libticables2 || 1.0.2 || comms/libticables2
|-
|libticalcs2 || 1.0.1 || comms/libticalcs2
|}

* Converters
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
|libticonv || 1.0.0 || converters/libticonv
|}

* Emulation
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
| TIEmu 2 || 2.08 || emulators/tiemu2
|}

= Mac OS X =
(Note that all of these assesments were made on a MacBook running 10.4.9 Intel. Mileage may vary on other versions and of course the Darwine stuff won't work on PPC.)

TiLP-II is known to compile and work properly with SilverLink and Direct USB cables with the 83+, 84+SE, and 89Ti, so there is no reason to believe it will not work with the other calculators. TI Connect X works well enough on Intel Macs even though it is not officially supported, however it seems to be more strict with the format of .8xk files than TiLP or TI Connect (Windows).

Brass works in Mono. Wabbitspasm compiles and works properly. ZDS works in Darwine.

TilEm compiles but seems to have some issues with multiple ROM versions. It is unclear to me if this is a problem with the build or TilEm itself. PindurTI is somewhat usable in Darwine: You must use the send.exe utility to send the ROM image, then it will emulate properly. However, it makes extensive use of the F-keys, including the ExposÃ© ones. Remapping the ExposÃ© keys is the only solution. TI FLASH Debugger runs in Darwine but the calculator windows are unskinned: You must either use the keyboard or click blindly in the window. The display output is fine, and other debugger windows appear to function properly. VirtualTI (2.5) should run OK after putting the ROM files somewhere Darwine knows about (I was lazy).

= Other Unixes =

This section is a stub. Please add it it.

Programming under Unix-like operating systems

2007-12-31T22:50:08Z

Sigma: /* FreeBSD */ Add z80asm

Here are the different tools at your disposal:

= General Overviews =

==Emulators==
* [http://lpg.ticalc.org/prj_tilem/ TilEm]
* VirtualTI through wine
* [[PindurTI]] through Wine
* [[PindurTI]] in non-interactive mode (with or without [http://kvince83.tengun.net/maxboard/viewtopic.php?t=2466 PTI frontend])

==Syntax highlighting==
Several editors have native or extensional support for editing Z80 assembly code with syntax highlighting:
* Kwrite and Kate can be made to syntax-highlight Z80 assembly with [http://www.ticalc.org/archives/files/fileinfo/391/39178.html the appropriate definition file]. The file must be placed in /usr/share/apps/katepart/syntax .
* SciTE and Emacs both have native modes for assembly code. For Emacs, one must make sure to turn on Font Lock mode as well.
* The [http://www.revsoft.org/phpBB2/viewforum.php?f=25 Z80 Assembly IDE] has simple syntax highlighting built-in.
* Users of Vim and WLA DX can use [http://sigma.unitedti.org/files/misc/z80.vim.bz2 this syntax file].

== Assembling ==

=== SPASM ===

'''Author''': Spencer Putt

'''Home Page''': [http://www.revsoft.org/phpBB2/viewforum.php?f=21 http://www.revsoft.org/phpBB2/viewforum.php?f=21]

SPASM is a portable Z80 assembler released under the GPL. Its distinguishing features are extremely fast assembly and powerful macro support. The output is only available in binary form, however with the use of [http://www.revsoft.org/phpBB2/viewforum.php?f=23 Wabbitsign], written by James Montelongo and Spencer Putt, it can easily be converted to any desired program type.

assembler foo.asm foo.bin
wabbit foo.bin foo.8xp

SPASM and Wabbitemu are included in [http://www.ticalc.org/archives/files/fileinfo/390/39009.html Z80 Assembly IDE 1.32] by burntfuse

=== tpasm ===

'''Author''': Todd Squires

'''Home page''': [http://www.sqrt.com/ http://www.sqrt.com/]

tpasm is a Free (GPL) assembler which supports the Z80 as well as the 6805, 6809, 68HC11, 6502, Sunplus, 8051, PIC, and AVR. It uses syntax very similar to ZMASM.

tpasm 1.2 does not support binary file output, but you can use ''objcopy'' (from the GNU binutils package) to convert its Intel Hex output into binary; e.g.

tpasm foo.asm -o intel foo.hex -l foo.lst
objcopy -I ihex foo.hex -O binary foo.bin

=== ASxxxx ===

'''Author''': Alan R. Baldwin

'''Home page''': [http://shop-pdp.kent.edu/ashtml/asxxxx.htm http://shop-pdp.kent.edu/ashtml/asxxxx.htm]

ASxxxx is a freeware assembler which supports the Z80 along with a large variety of other processors. It more closely resembles a modern PC assembler than a typical Z80 assembler, as it assembles each file into a relocatable object format which can then be linked with other files to produce the complete program. The linking is done by a separate program called ASlink (included with the package.)

To assemble and link a simple program you might do something like

asz80 -plogff foo.asm
aslink -u -b _CODE=0x9D95 -i foo.ihx foo.rel
objcopy -I ihex foo.ihx -O binary foo.bin

Note that the syntax is rather different from that of most Z80 assemblers. The important differences are
* Immediate values are marked with #.
* Indexed memory access is written as N(ix) rather than (ix+N).
* Constants are written differently: 0xAA, 0hAA, or $$AA for hexadecimal; 0o252, 0q252, or $&252 for octal; 0b10101010 or $%10101010 for binary.

For example,
ld hl,#str_hello
add a,3(ix)
xor #0x0f

There is also a modified version of ASxxxx distributed with the [http://sdcc.sf.net/ Small Device C Compiler]. This version is, if anything, more confusing to use due to the poorly-documented changes made by the SDCC team.

=== TASM ===

'''Author''': Thomas N. Anderson

'''Home page''': [http://home.comcast.net/~tasm/ http://home.comcast.net/~tasm/]

TASM is a shareware assembler which also supports a variety of processors.

There are several ways that you can use tasm under Linux:
* The TASM 3.1 for Linux shareware release is still in the wild. To use this you will need to enable "a.out" support in your kernel (it may be available as the module ''binfmt_aout''.) You will also need to obtain the ancient Linux libc version 4 (''not'' glibc) which can be found [http://ftp.linux.org.uk/pub/linux/libc/ here].
* You can use TASM 3.2 for Windows with [http://www.winehq.com Wine].
* You can pay the $40 and compile it yourself on the platform of your choice.

=== Brass ===
'''Author''': benryves

'''Home page''': [http://benryves.com/bin/brass/ http://benryves.com/bin/brass/]

Brass runs under Linux thanks to Mono.

=== Zasm ===
'''Author''': Steven Deprez

'''Home page''': [http://lpg.ticalc.org/prj_zasm/index.html http://lpg.ticalc.org/prj_zasm/index.html]

Zasm is an open source assembler that is almost fully compatible with Tasm and ZDS.

=== WLA DX ===
'''Author''': Ville Helin

'''Home page''': [http://users.tkk.fi/~vhelin/wla.html http://users.tkk.fi/~vhelin/wla.html]

WLA DX is another open-source (GNU GPL) cross-assembler with a primary focus on targeting video game consoles. It is a high-powered assembler with a wide variety of features such as, e.g. separate compilation, POSIX-like file I/O, and code sectioning. However it is cumbersome when assembling small projects, and semantics are unorthodox compared to other assemblers. (~ is the XOR operator, macro arguments are passed by value, etc.) Furthermore, development appears to have ceased since January 2006.

WLA DX has had an influence in the development of Brass.

=== Pasmo ===
'''Author''': Julián Albo

'''Home page''': [http://www.arrakis.es/~ninsesabe/pasmo/ http://www.arrakis.es/~ninsesabe/pasmo/]

Pasmo is another standalone Z80 cross-assembler with basic macro support, but without the ability to generate
relocatable object files. It is licensed under the GNU GPL, and exists as the package <tt>pasmo</tt> in the Debian pool.

=== z80asm ===
'''Author''': Bas Wijnen

'''Home page''': [http://savannah.nongnu.org/projects/z80asm/ http://savannah.nongnu.org/projects/z80asm/]

z80asm is a standalone Z80 cross-assembler similar in nature to Pasmo, in that it has macro support but cannot generate relocatable object files. It too is licensed under the GNU GPL (version 2 or later), and exists as the package <tt>z80asm</tt> in the Debian pool.

=== GNU as ===
'''Author''': the GNU binutils team

'''Home page''': [http://www.gnu.org/software/binutils/ http://www.gnu.org/software/binutils/]

Starting from version 2.17, the GNU assembler, part of the binutils package, is capable of cross-assembling Z80 code when configured for it at compile-time, such as with <tt>--target=z80-unknown-coff</tt>. binutils includes a powerful assembler and linker both, along with various utilities for handling object files, such as objcopy and objdump; for Z80, COFF is used for relocatable objects, with raw binary and Intel hex formats also supported. While this is probably one of the more powerful tools in the list for Z80 development, it also requires more work to start with, as the traditional way to get a cross-assembling binutils is to compile it oneself. Being a GNU package, binutils is naturally licensed under the GNU GPL (version 2 or later). Prepackaged binary versions of binutils are very common, but usually do not have cross-assembling capability.

==Sending programs to the calc==
* [http://www.ticalc.org/archives/files/fileinfo/374/37480.html TiLP-II] (requires [http://www.ticalc.org/archives/files/fileinfo/374/37479.html tilibs])
* [http://www.ticalc.org/archives/files/fileinfo/75/7588.html titranz] : commandline tool, only works for TI-83/TI-83+

= FreeBSD =
Much of the aforementioned software should compile independently without problem or with minor tweaking under FreeBSD, but it is best to utilize the ports collection whenever possible. Unfortunately, the current state of calculator-related software in the FreeBSD Ports Collection is lacking in variety.

* Development
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
|tpasm || 1.2_1 || devel/tpasm
|-
|z80asm || 1.6_1 || devel/z80asm
|-
|z80-asm || 0.1_1 || devel/z80-asm
|-
|TI-GCC || 0.96.b8 || devel/tigcc
|-
|libtifiles2 || 1.0.1 || devel/libtifiles2
|}

* Communications
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
|TiLP-II || 1.01 || comms/tilp2
|-
|libticables2 || 1.0.2 || comms/libticables2
|-
|libticalcs2 || 1.0.1 || comms/libticalcs2
|}

* Converters
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
|libticonv || 1.0.0 || converters/libticonv
|}

* Emulation
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
| TIEmu 2 || 2.08 || emulators/tiemu2
|}

= Mac OS X =
(Note that all of these assesments were made on a MacBook running 10.4.9 Intel. Mileage may vary on other versions and of course the Darwine stuff won't work on PPC.)

TiLP-II is known to compile and work properly with SilverLink and Direct USB cables with the 83+, 84+SE, and 89Ti, so there is no reason to believe it will not work with the other calculators. TI Connect X works well enough on Intel Macs even though it is not officially supported, however it seems to be more strict with the format of .8xk files than TiLP or TI Connect (Windows).

Brass works in Mono. Wabbitspasm compiles and works properly. ZDS works in Darwine.

TilEm compiles but seems to have some issues with multiple ROM versions. It is unclear to me if this is a problem with the build or TilEm itself. PindurTI is somewhat usable in Darwine: You must use the send.exe utility to send the ROM image, then it will emulate properly. However, it makes extensive use of the F-keys, including the ExposÃ© ones. Remapping the ExposÃ© keys is the only solution. TI FLASH Debugger runs in Darwine but the calculator windows are unskinned: You must either use the keyboard or click blindly in the window. The display output is fine, and other debugger windows appear to function properly. VirtualTI (2.5) should run OK after putting the ROM files somewhere Darwine knows about (I was lazy).

= Other Unixes =

This section is a stub. Please add it it.

Programming under Unix-like operating systems

2006-08-06T10:10:39Z

Sigma: Other Unixes placeholder

Here are the different tools at your disposal:

= General Overviews =

==Emulators==
* TilEm [http://lpg.ticalc.org/prj_tilem/]
* VTI (with Wine)

==Syntax highlighting==
Several editors have native or extensional support for editing Z80 assembly code with syntax highlighting:
* Kwrite and Kate can be made to syntax-highlight Z80 assembly with [http://guillaume.h.ifrance.com/ti83/z80assembler.xml the appropriate definition file]. The file can be placed in /usr/share/apps/katepart/syntax to install it.
* SciTE and Emacs both have native modes for assembly code. For Emacs, one must make sure to turn on Font Lock mode as well.
* The [http://www.revsoft.org/phpBB2/viewforum.php?f=25 Z80 Assembly IDE] has simple syntax highlighting built-in.
* Users of Vim and WLA DX can use [http://sigma.unitedti.org/files/misc/z80.vim.bz2 this syntax file].

== Assembling ==

=== SPASM ===

'''Author''': Spencer Putt

'''Home Page''': [http://www.revsoft.org/phpBB2/viewforum.php?f=21 http://www.revsoft.org/phpBB2/viewforum.php?f=21]

SPASM is a portable Z80 assembler released under the GPL. Its distinguishing features are extremely fast assembly and powerful macro support. The output is only available in binary form, however with the use of [http://www.revsoft.org/phpBB2/viewforum.php?f=23 Wabbitsign], written by James Montelongo and Spencer Putt, it can easily be converted to any desired program type.

assembler foo.asm foo.bin
wabbit foo.bin foo.8xp

=== tpasm ===

'''Author''': Todd Squires

'''Home page''': [http://www.sqrt.com/ http://www.sqrt.com/]

tpasm is a Free (GPL) assembler which supports the Z80 as well as the 6805, 6809, 68HC11, 6502, Sunplus, 8051, PIC, and AVR. It uses syntax very similar to ZMASM.

tpasm 1.2 does not support binary file output, but you can use ''objcopy'' (from the GNU binutils package) to convert its Intel Hex output into binary; e.g.

tpasm foo.asm -o intel foo.hex -l foo.lst
objcopy -I ihex foo.hex -O binary foo.bin

=== ASxxxx ===

'''Author''': Alan R. Baldwin

'''Home page''': [http://shop-pdp.kent.edu/ashtml/asxxxx.htm http://shop-pdp.kent.edu/ashtml/asxxxx.htm]

ASxxxx is a freeware assembler which supports the Z80 along with a large variety of other processors. It more closely resembles a modern PC assembler than a typical Z80 assembler, as it assembles each file into a relocatable object format which can then be linked with other files to produce the complete program. The linking is done by a separate program called ASlink (included with the package.)

To assemble and link a simple program you might do something like

asz80 -plogff foo.asm
aslink -u -b _CODE=0x9D95 -i foo.ihx foo.rel
objcopy -I ihex foo.ihx -O binary foo.bin

Note that the syntax is rather different from that of most Z80 assemblers. The important differences are
* Immediate values are marked with #.
* Indexed memory access is written as N(ix) rather than (ix+N).
* Constants are written differently: 0xAA, 0hAA, or $$AA for hexadecimal; 0o252, 0q252, or $&252 for octal; 0b10101010 or $%10101010 for binary.

For example,
ld hl,#str_hello
add a,3(ix)
xor #0x0f

There is also a modified version of ASxxxx distributed with the [http://sdcc.sf.net/ Small Device C Compiler]. This version is, if anything, more confusing to use due to the poorly-documented changes made by the SDCC team.

=== TASM ===

'''Author''': Thomas N. Anderson

'''Home page''': [http://home.comcast.net/~tasm/ http://home.comcast.net/~tasm/]

TASM is a shareware assembler which also supports a variety of processors.

There are several ways that you can use tasm under Linux:
* The TASM 3.1 for Linux shareware release is still in the wild. To use this you will need to enable "a.out" support in your kernel (it may be available as the module ''binfmt_aout''.) You will also need to obtain the ancient Linux libc version 4 (''not'' glibc) which can be found [http://ftp.linux.org.uk/pub/linux/libc/ here].
* You can use TASM 3.2 for Windows with [http://www.winehq.com Wine].
* You can pay the $40 and compile it yourself on the platform of your choice.

=== Brass ===
'''Author''': benryves

'''Home page''': [http://benryves.com/bin/brass/ http://benryves.com/bin/brass/]

Brass runs under Linux thanks to Mono.

=== WLA DX ===
'''Author''': Ville Helin

'''Home page''': [http://users.tkk.fi/~vhelin/wla.html http://users.tkk.fi/~vhelin/wla.html]

WLA DX is another open-source (GNU GPL) cross-assembler with a primary focus on targeting video game consoles. It is a high-powered assembler with a wide variety of features such as, e.g. separate compilation, POSIX-like file I/O, and code sectioning. However it is cumbersome when assembling small projects, and semantics are unorthodox compared to other assemblers. (~ is the XOR operator, macro arguments are passed by value, etc.) Furthermore, development appears to have ceased since January 2006.

WLA DX has had an influence in the development of Brass.

=== Pasmo ===
'''Author''': Julián Albo

'''Home page''': [http://www.arrakis.es/~ninsesabe/pasmo/ http://www.arrakis.es/~ninsesabe/pasmo/]

Pasmo is another standalone Z80 cross-assembler with basic macro support, but without the ability to generate
relocatable object files. It is licensed under the GNU GPL, and exists as the package <tt>pasmo</tt> in the Debian pool.

=== z80asm ===
'''Author''': Bas Wijnen

'''Home page''': [http://savannah.nongnu.org/projects/z80asm/ http://savannah.nongnu.org/projects/z80asm/]

z80asm is a standalone Z80 cross-assembler similar in nature to Pasmo, in that it has macro support but cannot generate relocatable object files. It too is licensed under the GNU GPL (version 2 or later), and exists as the package <tt>z80asm</tt> in the Debian pool.

=== GNU as ===
'''Author''': the GNU binutils team

'''Home page''': [http://www.gnu.org/software/binutils/ http://www.gnu.org/software/binutils/]

Starting from version 2.17, the GNU assembler, part of the binutils package, is capable of cross-assembling Z80 code when configured for it at compile-time, such as with <tt>--target=z80-unknown-coff</tt>. binutils includes a powerful assembler and linker both, along with various utilities for handling object files, such as objcopy and objdump; for Z80, COFF is used for relocatable objects, with raw binary and Intel hex formats also supported. While this is probably one of the more powerful tools in the list for Z80 development, it also requires more work to start with, as the traditional way to get a cross-assembling binutils is to compile it oneself. Being a GNU package, binutils is naturally licensed under the GNU GPL (version 2 or later). Prepackaged binary versions of binutils are very common, but usually do not have cross-assembling capability.

==Sending programs to the calc==
* TILP
* titranz : commandline tool, only works for TI-83/TI-83+

= FreeBSD =
Much of the aforementioned software should compile independently without problem or with minor tweaking under FreeBSD, but it is best to utilize the ports collection whenever possible. Unfortunately, the current state of calculator-related software in the FreeBSD Ports Collection is lacking in variety.

* Development
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
|tpasm || 1.2_1 || /devel/tpasm
|-
|z80asm || 0.1_1 || /devel/z80-asm
|-
|TI-GCC || 0.96.b6_1 || /devel/tigcc
|-
|libticalcs || 4.5.9_1 || /devel/libticalcs
|-
|libtifiles || 0.6.5_1 || /devel/libtifiles
|}

* Communications
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
|TiLP || 6.79_1 || /comms/tilp
|-
|libticables || 3.9.7_1 || /comms/libticables
|}

* Emulation
{| width="75%" class="wikitable" style="margin: 1em auto 1em auto"
|- align="left"
!Port !! Current Version !! Location
|-
| TIEmu 2 || 2.04 || /emulators/tiemu2
|}

= Other Unixes =

{{Sectstub}}

Programming under Linux

2006-08-06T10:02:20Z

Sigma: Programming under Linux moved to Programming under Unix-like operating systems: No longer just about Linux

#redirect [[Programming under Unix-like operating systems]]

Programming under Unix-like operating systems

2006-08-06T10:02:16Z

Sigma: Programming under Linux moved to Programming under Unix-like operating systems

Programming under Unix-like operating systems

2006-08-06T09:59:33Z

Sigma: FreeBSD

Programming under Unix-like operating systems

2006-07-23T01:46:06Z

Sigma: Information regarding WLA DX

Here are the different tools at your disposal:

==Emulators==
* TilEm [http://lpg.ticalc.org/prj_tilem/]
* VTI (with Wine)

==Syntax coloring==
* there is a file that enables syntax highlighting for z80 asm for Kwrite and Kate [http://guillaume.h.ifrance.com/ti83/z80assembler.xml here]. You have to put it in /usr/share/apps/katepart/syntax.
* some editors have an "assembler" syntax coloring that fits quite well (like scite).
* Z80 Assembly IDE (Latest version and forums are [http://www.revsoft.org/phpBB2/viewforum.php?f=25 here]) has simple syntax coloring.
* there exists a [http://sigma.unitedti.org/files/misc/z80.vim.bz2 syntax file] for users of Vim and WLA DX.

== Assembling ==

=== SPASM ===

'''Author''': Spencer Putt

'''Home Page''': [http://www.revsoft.org/phpBB2/viewforum.php?f=21 http://www.revsoft.org/phpBB2/viewforum.php?f=21]

SPASM is a portable Z80 assembler released under the GPL. Its distinguishing features are extremely fast assembly and powerful macro support. The output is only available in binary form, however with the use of [http://www.revsoft.org/phpBB2/viewforum.php?f=23 Wabbitsign], written by James Montelongo and Spencer Putt, it can easily be converted to any desired program type.

assembler foo.asm foo.bin
wabbit foo.bin foo.8xp

=== tpasm ===

'''Author''': Todd Squires

'''Home page''': [http://www.sqrt.com/ http://www.sqrt.com/]

tpasm is a Free (GPL) assembler which supports the Z80 as well as the 6805, 6809, 68HC11, 6502, Sunplus, 8051, PIC, and AVR. It uses syntax very similar to ZMASM.

tpasm 1.2 does not support binary file output, but you can use ''objcopy'' (from the GNU binutils package) to convert its Intel Hex output into binary; e.g.

tpasm foo.asm -o intel foo.hex -l foo.lst
objcopy -I ihex foo.hex -O binary foo.bin

=== ASxxxx ===

'''Author''': Alan R. Baldwin

'''Home page''': [http://shop-pdp.kent.edu/ashtml/asxxxx.htm http://shop-pdp.kent.edu/ashtml/asxxxx.htm]

ASxxxx is a freeware assembler which supports the Z80 along with a large variety of other processors. It more closely resembles a modern PC assembler than a typical Z80 assembler, as it assembles each file into a relocatable object format which can then be linked with other files to produce the complete program. The linking is done by a separate program called ASlink (included with the package.)

To assemble and link a simple program you might do something like

asz80 -plogff foo.asm
aslink -u -b _CODE=0x9D95 -i foo.ihx foo.rel
objcopy -I ihex foo.ihx -O binary foo.bin

Note that the syntax is rather different from that of most Z80 assemblers. The important differences are
* Immediate values are marked with #.
* Indexed memory access is written as N(ix) rather than (ix+N).
* Constants are written differently: 0xAA, 0hAA, or $$AA for hexadecimal; 0o252, 0q252, or $&252 for octal; 0b10101010 or $%10101010 for binary.

For example,
ld hl,#str_hello
add a,3(ix)
xor #0x0f

There is also a modified version of ASxxxx distributed with the [http://sdcc.sf.net/ Small Device C Compiler]. This version is, if anything, more confusing to use due to the poorly-documented changes made by the SDCC team.

=== TASM ===

'''Author''': Thomas N. Anderson

'''Home page''': [http://home.comcast.net/~tasm/ http://home.comcast.net/~tasm/]

TASM is a shareware assembler which also supports a variety of processors.

There are several ways that you can use tasm under Linux:
* The TASM 3.1 for Linux shareware release is still in the wild. To use this you will need to enable "a.out" support in your kernel (it may be available as the module ''binfmt_aout''.) You will also need to obtain the ancient Linux libc version 4 (''not'' glibc) which can be found [http://ftp.linux.org.uk/pub/linux/libc/ here].
* You can use TASM 3.2 for Windows with [http://www.winehq.com Wine].
* You can pay the $40 and compile it yourself on the platform of your choice.

=== Brass ===
'''Author''': benryves

'''Home page''' [http://benryves.com/bin/brass/ http://benryves.com/bin/brass/]

Brass runs under Linux thanks to Mono.

=== WLA DX ===
'''Author''': Ville Helin

'''Home page''' [http://users.tkk.fi/~vhelin/wla.html http://users.tkk.fi/~vhelin/wla.html]

WLA DX is another open-source (GNU GPL) cross-assembler with a primary focus on targeting video game consoles. It is a high-powered assembler with a wide variety of features such as, e.g. separate compilation, POSIX-like file I/O, and code sectioning. However it is cumbersome when assembling small projects, and semantics are unorthodox compared to other assemblers. (~ is the XOR operator, macro arguments are passed by value, etc.) Furthermore, development appears to have ceased since January 2006.

WLA DX has had an influence in the development of Brass.

==Sending programs to the calc==
* TILP
* titranz : commandline tool, only works for TI-83/TI-83+

Talk:83Plus:Ports:05

2005-07-18T23:25:01Z

Sigma:

I'm not sure how I feel about calling this "RAM Paging port", because all of 05,06, and 07 can be used to page in RAM. Personally I think that if we designate 0000-3FFF as bank0, 4000-7FFF as bank1, 8000-BFFF as bank2, and C000-FFFF as bank3 it will be the clearest. Then we can say port 5 controls bank3, port 6 controls bank1, and port 7 controls bank2. --[[User:Dan Englender|Dan Englender]] 09:46, 28 Mar 2005 (PST)

:Well, does it even make sense to assign a bank number to 0000h~3FFFh, since that's permanently set as ROM Page 0? Also another option would be to just call them by the address block they effect (or at least the first address)? Eg, bankC000, bank4000, bank8000? --[[User:Aquanight|Aquanight]] 15:47, 30 Mar 2005 (PST)

::I've heard them be called the 0000, 4000, 8000, and C000 banks before, so that would seem to be a good choice. I would go with this one...and at least these names can't result in any possible confusion at all. Simple and elegent. --[[User:JasonM|JasonM]] right now

I don't see why not to assign a bacnk number to 0000-3FFF. Just because the data in there isn't changing doesn't mean it's not useful to talk about it. Memory is logically split into these four different segments, so it's useful to have names for all of them. --[[User:Dan Englender|Dan Englender]] 08:32, 31 Mar 2005 (PST)

----

Should it be pointed out somewhere that only when the port is 0 (RAM page 0 selected) that execution is forbidden above address C000h? --[[User:Aquanight|Aquanight]] 15:10, 2 May 2005 (PDT)
:Isn't all execution prevented on ram page 0 regardless of where it is? --[[User:AndyJ|AndyJ]] 15:13, 2 May 2005 (PDT)
::Yes, but for people that might be semi-new to assembly it might be a good idea to point out *somewhere* that the execution limit is tied to the RAM page, and not the logical memory. Putting it here would seem to make the most sense :) . That or maybe somewhere in 83Plus:OS or something? --[[User:Aquanight|Aquanight]] 23:08, 3 May 2005 (PDT)
:::Well, it's a hardware thing, not an OS thing, so no it doesn't go there. It would go here. :) Someone fix that sometime, it's way too late for me to. :P --[[User:AndyJ|AndyJ]] 23:09, 3 May 2005 (PDT)

----

Added info about TI-83 Plus. Didn't know exactly how to separate BE with higher models given how radically different the behaviour of the port is, so I did what seemed logical and marked the page as non-standard. Also, the table could be better. [[User:Sigma|Sigma]] 16:25, 18 Jul 2005 (PDT)

83Plus:Ports:05

2005-07-18T23:22:01Z

Sigma: Added TI-83 Plus Info

[[Category:83Plus:Ports:By_Address|05 - RAM Page]] [[Category:83Plus:Ports:By_Name|RAM Page]] [[Category:83Plus:Ports:By_Name|83Plus:Ports:By_Name]]

{{wikify}}

== Synopsis (TI-83 Plus S.E. and TI-84 Plus Family) ==
'''Port Number:''' 05h

'''Function:''' RAM Paging Port

This port can be used to control what RAM page is paged into the C000h-FFFFh memory bank. Note that it can only page RAM pages, not flash pages.

=== Read Values ===
Returns the current RAM pages.

=== Write Values ===
Sets the current RAM page, by giving a value in 00h-07h, inclusive. When you work with the other paging ports, RAM pages are given in 80h-87h, but this port does not need bit 7 to be set. You cannot set the upper four bits.

== Synopsis (TI-83 Plus) ==
'''Port Number:''' 05h

'''Function:''' Port 16h Configuration Port

This port configures which memory pages are locked or unlocked (i.e. whether or not the PC register is allowed to point within the page) by port 16h. Only bits 0..2 are considered, the rest have no effect.

=== Read Values ===
Nothing of value.

=== Write Values ===
Writing a set bit to 16h protects the page; writing a clear bit unprotects the page.

<table align="center" border="1" cellpadding="1" style="text-align: center">
<tr>
<th colspan=3>Port 05h Bit</th>
<th colspan=8>Port 16h Bit</th>
</tr>
<tr>
<th>2</th>
<th>1</th>
<th>0</th>
<th>7</th>
<th>6</th>
<th>5</th>
<th>4</th>
<th>3</th>
<th>2</th>
<th>1</th>
<th>0</th>
</tr>
<tr>
<td>0</td>
<td>0</td>
<td>0</td>
<td>ROM 0F</td>
<td>ROM 0E</td>
<td>ROM 0D</td>
<td>ROM 0C</td>
<td>ROM 0B</td>
<td>ROM 0A</td>
<td>ROM 09</td>
<td>ROM 08</td>
</tr>
<tr>
<td>0</td>
<td>0</td>
<td>1</td>
<td>ROM 17</td>
<td>ROM 16</td>
<td>ROM 15</td>
<td>ROM 14</td>
<td>ROM 13</td>
<td>ROM 12</td>
<td>ROM 11</td>
<td>ROM 10</td>
</tr>
<tr>
<td>0</td>
<td>1</td>
<td>0</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>ROM 1B</td>
<td>ROM 1A</td>
<td>ROM 19</td>
<td>ROM 18</td>
</tr>
<tr>
<td>1</td>
<td>1</td>
<td>1</td>
<td>X</td>
<td>X</td>
<td>RAM 01</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>RAM 00</td>
</tr>
</table>

== Comments ==
At least on my TI-84+, if you output a value with bit 3 set, reading from the port will return a value with bit 3 set. This would imply that you can use RAM pages 08h-0Fh, but these RAM pages do not exist--this bit is simply ignored (only bits 0-2 actually determine what RAM page is active.)

== Credits and Contributions ==
* '''Michael Vincent:''' Initial documentation.
* '''Tijl Coosemans (sp? and correct mundane name?):''' Documenting TI-83 Plus functionality [http://www.kalimero.be/83phwinfo.txt here].

83Plus:Ports:00

2005-05-27T22:12:28Z

Sigma: Got rid of first person

[[Category:83Plus:Ports:By_Address|00 - Link]] [[Category:83Plus:Ports:By_Name|Link]]
== Synopsis ==
'''Port Number:''' 00h

'''Function:''' Link

This port controls the calculator's serial link port (the standard link port present on the 83+, 83+ SE, 84+ and 84+ SE - do not confuse this with the 84+/84+SE's USB link port).

=== Read Values ===
* Bit 0 and 1: The low 2 bits indicate the state of the link port's two lines. A 1 bit indicates a high line, and a 0 bit indicates a low line. When idle (no transfer in progress, no cable plugged in, etc), both lines are usually high (1). When a cable is connected on both ends, a line reads high if and only if both ends have set the line high. The line will read low if either calculator sets it low.
* Bit 5 and 6: Bits 5 and 6 indicate which lines are pulled low by the calculator (unlike bits 0 and 1 they are not influenced by the other calculator). A 1 bit indicates your calculator is holding the line low. A 0 bit indicates your calculator is not holding the line low. (When both calculators have a 0 bit here, the corresponding line will read 1.) In other words, these bits reflect bits 0 and 1 from the most recent write to this port.
* Bit 2: Unknown.

=== Write Values ===
* Bit 0 and 1: The low 2 bits indicate what state the lines should be put into. A 1 bit will pull the line low. A 0 bit will stop holding the line low (allowing it to go high if the other calculator is not holding it low).
* Bit 2: The complete meaning of this bit is unknown. What is known is that any change of this bit causes both lines to be released, writing with this bit set causes bit 2 to read 1, and the next write causes it to read 0 and both lines are released.
<br>

== Comments ==

=== Bit 2 ===
As mentioned bit 2's effect is unknown. An example of it's behavior follows:
<nowiki>Start, read 03.
Write 02, read 01.
Write 07, read 07.
Write 07, read 03.
Write 07, read 07.
Write 00, read 03.
Write 09, read 07.
Write 01, read 03.</nowiki>

=== Ti-OS interference ===
One thing to keep in mind when writing link port related software is that the Ti-OS checks for silent transfers in the background. When two calculators are connected and one pulls a line low, the other calculator will respond by pulling the other line low to acknowledge that it has received a bit. This phenomenon is known to cause severe headaches for programmers who attempt to write synchronization routines :). It's unclear if this is only when the other calculator is in the homescreen, or if it is part of the default interrupt routine at $0038.

=== Data transfer ===
Transferring an entire byte requires you to implement some form of protocol. Examples include TI's official linking protocol, and [http://www.ticalc.org/archives/files/fileinfo/277/27718.html Michael Vincent's TachyonLink protocol].

Other useful information on linking in general:
* [http://www.ticalc.org/archives/files/fileinfo/247/24750.html TI Link Protocol & File Format Guide]<br>
* [http://www.ticalc.org/archives/files/fileinfo/294/29418.html Ti-83 Link Port Tutorial]
* [http://www.ticalc.org/archives/files/fileinfo/242/24244.html All about the Ti-86 link port]

== Example ==

=== Sending/Setting ===
<pre>ld a,0 ; Set both lines high
out (0),a

ld a,2 ; Set tip high, ring low
out (0),a

ld a,1 ; Set tip low, ring high
out (0),a

ld a,3 ; Set both low
out (0),a</pre>

=== Receiving/Reading ===
<pre>in a,(0) ; Get the link port value

bit 0,a ; Check tip
jr z,tip_low
jr nz,tip_high

bit 1,a ; Check ring
jr z,ring_low
jr nz,ring_high</pre>

Talk:Contributing

2005-04-28T21:30:25Z

Sigma:

Should romcalls be put into only the most specific category, or should they appear in the parent category as well?--[[User:Dwedit|Dwedit]] 13:28, 28 Mar 2005 (PST)

----

They should be placed into both. We want a list of *all* bcalls/romcalls, but it's also nice to be able to browse by more specific type. So, for example, you would have something like this (pasted from the template) -

<nowiki>[[Category:83Plus:BCALLs:By Name|ProveTheRiemannHypothesis]]</nowiki>

and also

<nowiki>[[Category:83Plus:BCALLs:By Name|Utility|ProveTheRiemannHypothesis]]</nowiki>

And then a third category listing for the by address listing.
--[[User:Dan Englender|Dan Englender]] 14:22, 28 Mar 2005 (PST)

----

That'd be <nowiki>[[Category:83Plus:BCALLs:By Name:Utility|ProveTheRiemannHypothesis]]</nowiki>... *runs off to check the template*

--[[User:AndyJ|AndyJ]] 15:56, 28 Mar 2005 (PST)

----
Ick, I did goof that up... I fixed it. --[[User:AndyJ|AndyJ]] 15:57, 28 Mar 2005 (PST)

----
Would it be a good idea to use this nomenclature when talking about the calculator's memory?
*"page" - 256 bytes of memory, usu. in the address range ??00..??FF.
*"(memory) slot" - A division of logical memory used for memory banks (the TI-83 has four slots).
*"(memory) bank" - An amount of physical memory that can be mapped in/out of logical memory through a memory slot.

There is also no standard for how code should be formatted. There are three articles in Z80 Routines, and all of them use a different assembler's syntax (bub_font: ZMASM, fastcopy: TASM, and itoa (arguably the finest of them all :-): WLA).
--[[User:Sigma|Sigma]] 14:30, 28 Apr 2005 (PDT)

Z80 Routines:Other:DispA

2005-04-03T23:22:19Z

Sigma:

[[Category:Z80 Routines:Other|itoa]]
[[Category:Z80 Routines|itoa]]
<nowiki>
; ITOA
; --------------------------------------------------------------
; Converts a signed integer value to a zero-terminated ASCII
; string representative of that value (using radix 10).
; --------------------------------------------------------------
; INPUTS:
; HL Value to convert (two's complement integer).
; DE Base address of string destination. (pointer).
; --------------------------------------------------------------
; OUTPUTS:
; None
; --------------------------------------------------------------
; REGISTERS/MEMORY DESTROYED
; AF HL
; --------------------------------------------------------------

itoa:
push de
push bc

; Detect sign of HL.
bit 7, h
jr z, _DoConvert

; HL is negative. Output '-' to string and negate HL.
ld a, '-'
ld (de), a
inc de

; Negate HL (using two's complement)
xor a
sub l
ld l, a
ld a, 0 ; Note that XOR A or SUB A would disturb CF
sbc a, h
ld h, a

; Convert HL to digit characters
_DoConvert:
ld b, 0 ; B will count character length of number
- ld a, 10
call DivHLByA ; HL = HL / A, A = remainder
push af
inc b
ld a, h
or l
jr nz, -

; Retrieve digits from stack
- pop af
or $30
ld (de), a
inc de
djnz -

; Terminate string with NULL
xor a
ld (de), a

pop bc
pop de
ret
</nowiki>

===Comments===
*This routine uses the common [[Wikipedia:Numeral_systems#Change_of_radix|positive-integer radix conversion algorithm]] of repeatedly dividing a value by the desired radix (base case: the value is zero) and saving the remainders of each division.
*As this algorithm gives the digits in reverse order, they are pushed onto the hardware stack so that subsequently popping them yields the correct order.
*Note that the output string will not be fixed-width.

Z80 Routines:Other:DispA

2005-04-03T22:59:38Z

Sigma:

[[Category:Z80 Routines:Other|itoa]]
[[Category:Z80 Routines|itoa]]
<nowiki>
; ITOA
; --------------------------------------------------------------
; Converts a signed integer value to a zero-terminated ASCII
; string representative of that value (using radix 10).
; --------------------------------------------------------------
; INPUTS:
; HL Value to convert (two's complement integer).
; DE Base address of string destination. (pointer).
; --------------------------------------------------------------
; OUTPUTS:
; None
; --------------------------------------------------------------
; REGISTERS/MEMORY DESTROYED
; AF HL
; --------------------------------------------------------------

itoa:
push de
push bc

; Detect sign of HL.
bit 7, h
jr z, _DoConvert

; HL is negative. Output '-' to string and negate HL.
ld a, '-'
ld (de), a
inc de

; Negate HL (using two's complement)
xor a
sub l
ld l, a
ld a, 0 ; Note that XOR A or SUB A would disturb CF
sbc a, h
ld h, a

; Convert HL to digit characters
_DoConvert:
ld b, 0 ; B will count character length of number
- ld a, 10
call DivHLByA ; HL = HL / A, A = remainder
push af
inc b
ld a, h
or l
jr nz, -

; Retrieve digits from stack
- pop af
or $30
ld (de), a
inc de
djnz -

; Terminate string with NULL
xor a
ld (de), a

pop bc
pop de
ret

</nowiki>

===Comments===
This routine uses the common radix conversion algorithm of repeatedly dividing a value by the desired radix (base case: the value is zero) and saving the remainders of each division.

Z80 Routines:Other:DispA

2005-04-03T22:55:41Z

Sigma: