WikiTI - User contributions [en]

Calculator Documentation

2007-01-09T07:45:08Z

Jib: Link cables

== TI-83 (Regular) ==

* [[:Category:83:ROMCalls:By_Name|ROMCalls (System Entrypoints)]]
* [[:Category:83:Flags:By_Name|Flags]]
* [[:Category:83:OS_Information|General OS Documentation]]
* [[:Category:83:Ports:By_Address|Ports]]
* [[:Category:83:RAM:By_Name|RAM Areas]]

== TI-83 Plus Family ==

* [[:Category:83Plus:BCALLs:By_Name|B_CALLs (System Entrypoints)]]
* [[:Category:83Plus:Flags:By_Name|Flags]]
* [[:Category:83Plus:OS_Information|General OS Documentation]]
* [[:Category:83Plus:Hooks:By_Name|Hooks]]
* [[:Category:83Plus:Ports:By_Address|Ports]]
* [[:Category:83Plus:RAM:By_Name|RAM Areas]]
* [[:Category:83Plus:Software|Software Documentation]]
* [[:Category:83Plus:Basic|TI-83+ Basic]]

== M68K Family ==

* [[:Category:68k:Ports:By_Address|Ports]]

== Z80 programming ==

* [[:Category:Z80_Routines|Z80 Routines]]
* [[Z80 Instruction Set]]
* [[Good programming practices]]
* [[Programming under Unix-like operating systems]]

== Software ==

* [[:Category:Emulators|Emulators]]
* [[83Plus:OS:TIOS Alternatives|TIOS Alternatives]]
* [[Experiments]]

== Linking ==
* [[Link cables]]

== TI Community ==

* [[History of the TI Z80 community]]
* [[:Category:Teams|Programming Teams]]
* [[TI websites]]

== Contributing ==

Please read our page on [[Contributing]] before you start contributing to WikiTI.

Link cables

2007-01-09T07:36:43Z

Jib:

== USB cables ==

=== Direct USB cable ===

[http://wikiti.denglend.net/stuff/DirectUSB.jpg Image of Direct USB cable]

Supported calculators:
* TI-84+
* TI-84+ Silver Edition
* TI-89 Titanium

Supported software:
* TI-Connect

Connectors:
* PC end: USB A plug
* Calc end: USB mini-B plug

=== Silver link ===

[http://wikiti.denglend.net/stuff/SilverLink.jpg Image of Silver link cable]

Supported calculators:
* All

Supported software:
* TI-Connect
* TiLP

Connectors:
* PC end: USB A plug
* Calc end: 2.5mm stereo socket

== Serial cables ==

=== Black serial link ===

[http://wikiti.denglend.net/stuff/BlackSerial.jpg Image of Black serial link cable]

Supported calculators:
* All

Supported software:
* TI-Connect
* TiLP
* TI-Graph Link

Connectors:
* PC end: Serial port plug
* Calc end: 2.5mm stereo socket

=== Grey serial link ===

[http://wikiti.denglend.net/stuff/GreySerial.jpg Image of Grey serial link cable]

Supported calculators:
* All

Supported software:
* TI-Connect
* TiLP
* TI-Graph Link

Connectors:
* PC end: Serial port plug
* Calc end: 2.5mm stereo socket

83Plus:BCALLs:8033

2006-11-06T10:04:43Z

Jib:

[[Category:83Plus:BCALLs:By Name:Utterly Useless|WowWhatAnIncrediblyUsefulBCall]] [[Category:83Plus:BCALLs:By Name|WowWhatAnIncrediblyUsefulBCall]] [[Category:83Plus:BCALLs:By Address|8033-803F - WowWhatAnIncrediblyUsefulBCall]]
== Synopsis ==
'''Completely Unofficial Name:''' WowWhatAnIncrediblyUsefulBCall(2/3/4/5/6)

'''BCALL Addresses:''' 50E6,8033,8036,8039,803C,803F

They attempt and fail to prove the Riemann Hypothesis.

=== Inputs ===
''None''

=== Outputs ===
''None''

=== Destroys ===
''None''

== Comments ==
Complete code for these B_CALLs:
<nowiki>ret</nowiki>

Speculation is on BCALL 50E6 being related to BCALLs [[83Plus:BCALLs:50E3|50E3]] and [[83Plus:BCALLs:50E9|50E9]] but functionality was removed.

83Plus:BCALLs:50E6

2006-11-06T06:01:17Z

Jib:

#REDIRECT [[83Plus:BCALLs:8033]]

83Plus:BCALLs:8033

2006-11-06T06:00:47Z

Jib:

Talk:Calculator Documentation

2006-11-05T20:35:15Z

Jib:

I changed some headings and moved stuff around a bit. I think it's more logical this way, but I don't mind if you change it back. [[User:Jib|Jib]] 02:37, 5 November 2006 (PST)
: The only thing that bugs me about it is that there's a "software" heading that includes both PC software (emulators) and calculator software (TIOS Alternatives), not to mention that software documentation is listed under a different heading. What do you think about:
Z80 Calculators
TI-83
Programming
Ports
RAM Areas
B_CALLs
etc
Software
Calculator Software
Emulators
Linking Software
TIOS Alternatives
TI-83 Plus Family
Programming
etc...
Software
etc...
General Z80 Info
Instruction Set
etc.

68k Calculators
TI-89/92+
Programming
etc.
Software
etc.
TI-92
etc.
General 68k Info
Instruction Set
etc.

TI Community
History
Programming Teams
etc.

For example, in that organization, the TI-83 Emulators page would basically just be a list of the emulators compatible with the 83, each of which would have their own separate page. So the VTI page might be linked from the TI-83 emulators page, the TI-85 emulators page, the TI-89 emulators page, etc. I like this organization because it makes it clear what calculators everything is applicable to, and it decreases the number of top-level categories. But maybe it's too complicated or has too many levels. Thoughts? --[[User:Dan Englender|Dan Englender]] 09:11, 5 November 2006 (PST)
:Yeah, it seems like a good idea to me. [[User:Jib|Jib]] 12:35, 5 November 2006 (PST)

Talk:TI websites

2006-11-05T10:48:42Z

Jib:

Someone should add some more sites (I don't know very many), and write short descriptions for the sites we add. [[User:Jib|Jib]] 02:48, 5 November 2006 (PST)

TI websites

2006-11-05T10:46:48Z

Jib:

* [http://education.ti.com Official TI calculator site]
* [http://www.ticalc.org ticalc.org]

Calculator Documentation

2006-11-05T10:42:58Z

Jib: "TI websites" link

== TI-83 (Regular) ==

* [[:Category:83:ROMCalls:By_Name|ROMCalls (System Entrypoints)]]
* [[:Category:83:Flags:By_Name|Flags]]
* [[:Category:83:OS_Information|General OS Documentation]]
* [[:Category:83:Ports:By_Address|Ports]]
* [[:Category:83:RAM:By_Name|RAM Areas]]

== TI-83 Plus Family ==

* [[:Category:83Plus:BCALLs:By_Name|B_CALLs (System Entrypoints)]]
* [[:Category:83Plus:Flags:By_Name|Flags]]
* [[:Category:83Plus:OS_Information|General OS Documentation]]
* [[:Category:83Plus:Hooks:By_Name|Hooks]]
* [[:Category:83Plus:Ports:By_Address|Ports]]
* [[:Category:83Plus:RAM:By_Name|RAM Areas]]
* [[:Category:83Plus:Software|Software Documentation]]
* [[:Category:83Plus:Basic|TI-83+ Basic]]

== M68K Family ==

* [[:Category:68k:Ports:By_Address|Ports]]

== Z80 programming ==

* [[:Category:Z80_Routines|Z80 Routines]]
* [[Z80 Instruction Set]]
* [[Good programming practices]]
* [[Programming under Unix-like operating systems]]

== Software ==

* [[:Category:Emulators|Emulators]]
* [[83Plus:OS:TIOS Alternatives|TIOS Alternatives]]
* [[Experiments]]

== TI Community ==

* [[History of the TI Z80 community]]
* [[:Category:Teams|Programming Teams]]
* [[TI websites]]

== Contributing ==

Please read our page on [[Contributing]] before you start contributing to WikiTI.

Calculator Documentation

2006-11-05T10:39:52Z

Jib:

== TI-83 (Regular) ==

* [[:Category:83:ROMCalls:By_Name|ROMCalls (System Entrypoints)]]
* [[:Category:83:Flags:By_Name|Flags]]
* [[:Category:83:OS_Information|General OS Documentation]]
* [[:Category:83:Ports:By_Address|Ports]]
* [[:Category:83:RAM:By_Name|RAM Areas]]

== TI-83 Plus Family ==

* [[:Category:83Plus:BCALLs:By_Name|B_CALLs (System Entrypoints)]]
* [[:Category:83Plus:Flags:By_Name|Flags]]
* [[:Category:83Plus:OS_Information|General OS Documentation]]
* [[:Category:83Plus:Hooks:By_Name|Hooks]]
* [[:Category:83Plus:Ports:By_Address|Ports]]
* [[:Category:83Plus:RAM:By_Name|RAM Areas]]
* [[:Category:83Plus:Software|Software Documentation]]
* [[:Category:83Plus:Basic|TI-83+ Basic]]

== M68K Family ==

* [[:Category:68k:Ports:By_Address|Ports]]

== Z80 programming ==

* [[:Category:Z80_Routines|Z80 Routines]]
* [[Z80 Instruction Set]]
* [[Good programming practices]]
* [[Programming under Unix-like operating systems]]

== Software ==

* [[:Category:Emulators|Emulators]]
* [[83Plus:OS:TIOS Alternatives|TIOS Alternatives]]
* [[Experiments]]

== TI Community ==

* [[History of the TI Z80 community]]
* [[:Category:Teams|Programming Teams]]

== Contributing ==

Please read our page on [[Contributing]] before you start contributing to WikiTI.

Talk:Programming under Unix-like operating systems

2006-11-05T10:39:11Z

Jib:

== Z80 gcc? ==
If GNU as can do z80, does that mean gcc can do z80 also? [[User:Jib|Jib]] 02:39, 5 November 2006 (PST)

Talk:Calculator Documentation

2006-11-05T10:37:52Z

Jib:

I changed some headings and moved stuff around a bit. I think it's more logical this way, but I don't mind if you change it back. [[User:Jib|Jib]] 02:37, 5 November 2006 (PST)

Calculator Documentation

2006-11-05T10:33:52Z

Jib: moved stuff around

== TI-83 (Regular) ==

* [[:Category:83:ROMCalls:By_Name|ROMCalls (System Entrypoints)]]
* [[:Category:83:Flags:By_Name|Flags]]
* [[:Category:83:OS_Information|General OS Documentation]]
* [[:Category:83:Ports:By_Address|Ports]]
* [[:Category:83:RAM:By_Name|RAM Areas]]

== TI-83 Plus Family ==

* [[:Category:83Plus:BCALLs:By_Name|B_CALLs (System Entrypoints)]]
* [[:Category:83Plus:Flags:By_Name|Flags]]
* [[:Category:83Plus:OS_Information|General OS Documentation]]
* [[:Category:83Plus:Hooks:By_Name|Hooks]]
* [[:Category:83Plus:Ports:By_Address|Ports]]
* [[:Category:83Plus:RAM:By_Name|RAM Areas]]
* [[:Category:83Plus:Software|Software Documentation]]
* [[:Category:83Plus:Basic|TI-83+ Basic]]

== M68K Family ==

* [[:Category:68k:Ports:By_Address|Ports]]

== Z80 programming ==

* [[:Category:Z80_Routines|Z80 Routines]]
* [[Z80 Instruction Set]]
* [[Good programming practices]]
* [[Programming under Unix-like operating systems]]

== Software ==

* [[:Category:Emulators|Emulators]]
* [[83Plus:OS:TIOS Alternatives|TIOS Alternatives]]
* [[Experiments]]

== Ti Community ==

* [[History of the TI Z80 community]]
* [[:Category:Teams|Programming Teams]]

== Contributing ==

Please read our page on [[Contributing]] before you start contributing to WikiTI.

Talk:83Plus:OS:TIOS Alternatives

2006-11-05T10:18:37Z

Jib:

== Nostalgy ==
Well, I was on the team for that, and as far as I knew it died. I've not touched my parts of the code for about two years now. I'd be willing to take it back up if it's going to go anywhere, but... I just haven't touched it in so long I'd probably want to start over, especially since I've learned some things since I started working on it. [[User:AndyJ|Andy Janata]] 10:31, 27 March 2006 (PST)

== Vera = exokernel? ==

In regards to Vera: ''this architecture is very similar to that of an exokernel operating system''. Having briefly read up on Vera, it doesn't seem to me to be an exokernel. Even in its current form the operating system seems to do more than securely export hardware resources. However, I'm not intimately familiar with the project, so I'm leaving some time for someone to correct me before I change the text. --[[User:Dan Englender|Dan Englender]] 12:25, 27 March 2006 (PST)
:Vera seems to have died in her cradle... Anyway, the idea is to provide a filesystem (possibly integrated with memory management), a plugin system that would enable user code to extend the assembly interface, user program execution (naturally) and maybe a common link protocol and a customisable ISR at $0038. Everything above that, including the UI and maths capabilities is not an integral part of the system. [[User:CoBB|CoBB]] 13:09, 27 March 2006 (PST)
::Yeah, but providing a file system and memory management is beyond exokernel. Plus it doesn't seem to grant access to and revoke hardware resources. I would say it's more microkernelish than exokernelish, although probably provides more OS support than even a microkernel. --[[User:Dan Englender|Dan Englender]] 13:29, 27 March 2006 (PST)
:I based my text there on the comment left on the Vera wiki [http://brazucs.unitedti.org/vera/wiki/index.php/Talk:Core_Design_Principle discussion page] about their supposed "Core Design Principle". I'm not sure the traditional OS categories work very well for TI-83+ calculators in the first place. I have no particular attachment to that categorization, at any rate, so remove or alter it if you think it's inaccurate. --[[User:Premchai21|Premchai21]] 19:12, 27 March 2006 (PST)
:An exokernel's job is to securely multiplex and control access to hardware resources. On a system with no memory protection, it is impossible to secure hardware resources while still allowing the user to run arbitrary code. I think discussing what type of kernel a calc OS uses is rather meaningless, because most of the distinction between kernels is the amount of code in userspace vs. kernel space, and on the calculator there is not any separation of memory spaces between user and kernel. [[User:Jib|Jib]] 02:08, 5 November 2006 (PST)

== Thoughts on OS viability ==

Well, I've been thinking myself about creating an OS for the calc. I've been discussing it with friends who are more "in the know" than I as well. In this time, I have come to realize the limitations of the z80 processor. It is now my firm belief that replacing the TI-OS simply isn't viable or worth it.

The z80 processor does NOT have a protected mode. *ANY* piece of software running on it has direct control over the hardware. There is absolutely NO workaround for this. A malicious piece of software, or just a severely glitchy piece of software, could completely fubar the calc and there isn't a damn thing you can do about it. [[User:Toksyuryel|Toksyuryel]] 12:53, 10 July 2006 (PDT)

:Actually, the worst-case scenario is you are left with a calculator with no OS on it, but the boot page will still always be there and you'll be able to load an OS back on it. It would be very hard to permanently damage the calculator from software (blue lines excluded); you can always pre-empt the installed OS with the boot code when you insert a battery while holding DEL. [[User:AndyJ|Andy Janata]] 14:45, 11 July 2006 (PDT)

:Since someone told me this might be a bit too technical, I'll rephrase: You can _always_ put TI-OS back on a calculator, no matter what a previous OS or other piece of software may do to the calculator. There is only one real way to break the calculator from software, and that is to overpower the LCD. [[User:AndyJ|Andy Janata]] 20:09, 11 July 2006 (PDT)

:Also, the z80 itself may not have protections, but the calculator's hardware implements a few. There are ROM read/write protections, and ROM and RAM execution protections. These can be used to your advantage when writing an OS. It's certainly true that you can crash the calculator from any program, but you could do that from early PCs too, and that didn't stop people from writing operating systems. As for "fubaring" the calculator, without too much trouble you could design an OS to be more secure than TIOS, and fubarity isn't particularly common in TIOS. Obviously designing an operating system which implements all modern systems concepts is out of the question, but there's no reason why you couldn't replace TI-OS with a very functional alternative operating system. --[[User:Dan Englender|Dan Englender]] 20:13, 11 July 2006 (PDT)

::The fact that there is no way to prevent a program from wiping the Flash is a serious problem, imho. It is no fun at all having to re-send the OS when something like that happens. And the blue lines thing? Totally unacceptable. Access to the hardware on such a level should be restricted and explicitly controlled. Unfortunately on the z80 this is not possible. These are the kinds of protections I look for when I consider an OS, but these things are not possible on the z80. I do understand that old PCs used to have the same problems, but we aren't living in those days anymore. It has been brought to my attention however that the m68k does have something of a protected mode, so I may get myself an 89/92 and fiddle with it. I am sorry that I cannot share your optimisim, but I strive for the highest quality and when such is physically impossible I look elsewhere. [[User:Toksyuryel|Toksyuryel]] 02:18, 13 July 2006 (PDT)

=== High-level language based OS ===

Neither the m68k nor the Z80 has any built-in ability to do memory protection or hardware access control. The only way to prevent the user from writing arbitrary data to the hardware is to prevent the user from running arbitrary code. One possible way this could work is to have the OS only programmable in high-level languages, a bit like what the TI-OS was like before it was hacked to run ASM.

Of course, if you actually implemented something like what I described, you would make it faster, smaller and more powerful than TI-BASIC. If the system had a sufficiently well-designed high-level language, you could do almost anything that ASM can do, but more easily and without the risks to the hardware.

An OS that runs entirely on a high-level language is harder to design, though, because you have to decide what functionality of the hardware will be exposed to the user in what way, so that the user is able to do as much useful stuff as possible without being able to screw up the system.

[[User:Jib|Jib]] 02:18, 5 November 2006 (PST)

Talk:83Plus:OS:TIOS Alternatives

2006-11-05T10:08:48Z

Jib:

Teams:Revsoft

2006-11-05T10:01:21Z

Jib:

{{stub}}

== Revolution Software ==
* [http://www.revsoft.org Revolution Software]
* [http://www.revsoft.org/phpBB2/ Forum]
* IRC channel: #revsoft on EFnet

[[Category:Teams|Revsoft]]

83Plus:Basic:Graphics:Pause

2006-11-05T09:53:28Z

Jib:

[[Category:83Plus:Basic:Graphics|Pause]]

== Synopsis ==
'''Token size:''' 1 byte

'''Syntax:''' Pause [string]

Waits for the Enter key to be pressed, optionally displaying a string first.

== Outputs: ==

The program will print the string, if present, then stop until the user presses the Enter key.

== Comments ==

Using Pause to display a string is the equivalent of:
:Disp [string]
:Pause

The only difference (besides saving a byte or two) is that values too long to be shown on one line can be scrolled if displayed with Pause, but not if displayed with Disp. For more information about displaying strings, see [[83Plus:Basic:Graphics:Disp|Disp]].

Emulators:TiEmu

2006-11-05T07:08:15Z

Jib:

{{stub}}

TiEmu is the major emulator for the m68k series. It supports all the 68k calcs.

[http://lpg.ticalc.org/prj_tiemu/ http://lpg.ticalc.org/prj_tiemu/] TiEmu homepage

Category:Emulators

2006-11-05T07:05:38Z

Jib:

A software emulator allows computer programs to run on a platform (computer architecture and/or operating system) other than the one for which they were originally written. Unlike a simulation, which only attempts to reproduce a program's behavior, an emulation attempts to precisely model the state of the device being emulated.

[http://www.wikipedia.org Source: wikipedia]

==Advantages==
Why using an emulator instead of the ''real'' calculator? There are several reasons for this:
* When crashing, you can recover the emulator with the ease of one/two-clicks.
* Sending files is a matter of drag'n'droping the file.
* Test on different calcs.
* Access to powerfull debuging tools.
* Ability to take screenshots.

==TI Emulators==
There are four major emulators available for the z80 series of calcs.
* [[Emulators:PindurTI|PindurTI]] (also known as PTI)
* [[Emulators:Virtual TI|Virtual TI]] (also known as VTI)
* [[Emulators:TilEm|TilEm]]
* TI Flash Debugger

[[Emulators:PindurTI|PindurTI]] is the latest addition to emulators and has the most accurate emulation of all emulators available. It is however only for Windows at the moment. Linux users can use [[Emulators:TilEm|TilEm]]. [[Emulators:Virtual TI|Virtual TI]] is the oldest and most used emulator at the moment. It has however a lot problems because of incorrect emulation.

The major emulator for the m68k series is [[Emulators:TiEmu|TiEmu]], which supports all the 68k calcs.

83Plus:RAM:9824

2006-11-05T06:57:03Z

Jib:

[[Category:83Plus:RAM:By_Name|FPS]] [[Category:83Plus:RAM:By_Address|9824 - FPS]]
== Synopsis ==
'''Official Name:''' FPS

'''Memory Address:''' 9842h

'''Length:''' 2 bytes.

This is a pointer to the next free byte above the top of the Floating Point Stack, which is at the bottom end of free RAM.

== Comments ==
The Floating Point Stack is used by many BCALLs for temporary storage of floating point values.

68k:Ports:600012

2006-11-05T06:32:09Z

Jib:

[[Category:68k:Ports:By Address|600012]] [[Category:68k:Ports:By Name|LCD logical height]]

== LCD logical height ==

* Bits 7-0: LCD logical height = (256-n)

The LCD logical height is the number of row syncs (RS) per frame sync (FS). If the LCD logical height is less, the screen will appear darker, because each line is visited more often.

68k:Ports:600013

2006-11-05T06:31:29Z

Jib:

[[Category:68k:Ports:By Address|600013]] [[Category:68k:Ports:By Name|LCD logical width]]

== LCD logical width ==

* Bits 5-0: LCD logical width = 2*(64-n) bytes, or 16*(64-n) pixels

68k:Ports:600012

2006-11-05T06:30:00Z

Jib:

[[Category:68k:Ports:By Address|600012]] [[Category:68k:Ports:By Name|LCD logical height]]

* Bits 7-0: LCD logical height = (256-n)

If the LCD logical height is less, the screen will appear darker, because each line is visited more often.

68k:Ports:60000F

2006-11-05T06:28:35Z

Jib:

[[Category:68k:Ports:By Address|60000F]] [[Category:68k:Ports:By Name|Link Data]]

== Link Data ==

* Writing a byte to this port writes it to the link transmit buffer.
* Reading a byte from this port reads from the link receive buffer.

68k:Ports:60000E

2006-11-05T06:26:23Z

Jib:

[[Category:68k:Ports:By Address|60000E]] [[Category:68k:Ports:By Name|Link Direct Access]]

== Direct link port access ==

[[68k:Ports:60000C]]:6 should be set before using this port

* Bit 3: D1 status (1=low)
* Bit 2: D0 status (1=low)
* Bit 1: Pull down D1
* Bit 0: Pull down D0

68k:Ports:60000D

2006-11-05T06:13:31Z

Jib:

[[Category:68k:Ports:By Address|60000D]] [[Category:68k:Ports:By Name|Link status]]

== Link status (interrupt reason) ==

According to [http://tict.ticalc.org/docs/J89hw.txt J89hw.txt] you have to read [[68k:Ports:60000C|60000C]] to begin acknowledging a link interrupt. Other documents don't seem to mention this though.

* Bit 7: Error (write 0xE0 then 0x8D to [[68k:Ports:60000C|60000C]] to acknowledge)
* Bit 6: Transmit buffer empty (write another byte or clear [[68k:Ports:60000C|60000C]]:1 to acknowledge)
* Bit 5: Received byte (read the byte to acknowledge)
* Bit 4: Interrupt pending (Always 1 in interrupt handler)
* Bit 3: Autostart
* Bit 2: (?) External activity
* Bit 1: (?)
* Bit 0: (?)

68k:Ports:60000D

2006-11-05T06:13:11Z

Jib:

[[Category:68k:Ports:By Address|60000D]] [[Category:68k:Ports:By Name|Link status]]

== Link status (interrupt reason) ==

According to [[http://tict.ticalc.org/docs/J89hw.txt J89hw.txt]] you have to read [[68k:Ports:60000C|60000C]] to begin acknowledging a link interrupt. Other documents don't seem to mention this though.

* Bit 7: Error (write 0xE0 then 0x8D to [[68k:Ports:60000C|60000C]] to acknowledge)
* Bit 6: Transmit buffer empty (write another byte or clear [[68k:Ports:60000C|60000C]]:1 to acknowledge)
* Bit 5: Received byte (read the byte to acknowledge)
* Bit 4: Interrupt pending (Always 1 in interrupt handler)
* Bit 3: Autostart
* Bit 2: (?) External activity
* Bit 1: (?)
* Bit 0: (?)

68k:Ports:60000D

2006-11-05T06:12:37Z

Jib:

[[Category:68k:Ports:By Address|60000D]] [[Category:68k:Ports:By Name|Link status]]

== Link status (interrupt reason) ==

According to [[68k:Documents:J89hw.txt|J89hw.txt]] you have to read [[68k:Ports:60000C|60000C]] to begin acknowledging a link interrupt. Other documents don't seem to mention this though.

* Bit 7: Error (write 0xE0 then 0x8D to [[68k:Ports:60000C|60000C]] to acknowledge)
* Bit 6: Transmit buffer empty (write another byte or clear [[68k:Ports:60000C|60000C]]:1 to acknowledge)
* Bit 5: Received byte (read the byte to acknowledge)
* Bit 4: Interrupt pending (Always 1 in interrupt handler)
* Bit 3: Autostart
* Bit 2: (?) External activity
* Bit 1: (?)
* Bit 0: (?)

68k:Ports:60000D

2006-11-05T06:12:21Z

Jib:

[[Category:68k:Ports:By Address|60000D]] [[Category:68k:Ports:By Name|Link status]]

== Link status (interrupt reason) ==

According to [[68k:Documents:J89hw.txt]] you have to read [[68k:Ports:60000C|60000C]] to begin acknowledging a link interrupt. Other documents don't seem to mention this though.

* Bit 7: Error (write 0xE0 then 0x8D to [[68k:Ports:60000C|60000C]] to acknowledge)
* Bit 6: Transmit buffer empty (write another byte or clear [[68k:Ports:60000C|60000C]]:1 to acknowledge)
* Bit 5: Received byte (read the byte to acknowledge)
* Bit 4: Interrupt pending (Always 1 in interrupt handler)
* Bit 3: Autostart
* Bit 2: (?) External activity
* Bit 1: (?)
* Bit 0: (?)

68k:Ports:60000C

2006-11-05T05:57:47Z

Jib:

[[Category:68k:Ports:By Address|60000C]] [[Category:68k:Ports:By Name|Link control]]

== Link control ==

* Bit 7: Autostart enable (should be set if [[68k:Ports:600005|600005]]:3 is set)
* Bit 6: Disable byte sender / receiver (also disables interrupts)
* Bit 5: Link timeout disable
* Bit 4: -
* Bit 3: Trigger auto-int 4 on link error
* Bit 2: Trigger auto-int 4 on link activity
* Bit 1: Trigger auto-int 4 when transmit buffer empty
* Bit 0: Trigger auto-int 4 when byte in receive buffer

68k:Ports:60000C

2006-11-05T05:56:27Z

Jib:

[[Category:68k:Ports:By Address|60000C]] [[Category:68k:Ports:By Name|Link control]]

* Bit 7: Autostart enable (should be set if [[68k:Ports:600005|600005]]:3 is set)
* Bit 6: Disable byte sender / receiver (also disables interrupts)
* Bit 5: Link timeout disable
* Bit 4: -
* Bit 3: Trigger auto-int 4 on link error
* Bit 2: Trigger auto-int 4 on link activity
* Bit 1: Trigger auto-int 4 when transmit buffer empty
* Bit 0: Trigger auto-int 4 when byte in receive buffer

68k:Ports:600001

2006-11-05T05:47:31Z

Jib:

[[Category:68k:Ports:By Address|600001]] [[Category:68k:Ports:By Name|Stack overflow protection / RAM size]]

* Bit 2: Interleave RAM. 1 = 128KB RAM, 0 = 256KB RAM
* Bit 0: 1 = Auto-int 7 generated for writes to 0x000000-0x00011F and 0xE00000-0xFFFFFF

Talk:68k:Ports:600000

2006-11-05T05:46:01Z

Jib:

I wonder whether bit 7 is set to 0 or 1 on the TI-92. If the port works the same way on the 92 as it is described here, then I would expect bit 7 to be set. [[User:Jib|Jib]] 21:46, 4 November 2006 (PST)

Talk:83Plus:BCALLs:4CBD

2006-11-05T05:24:07Z

Jib:

I propose that all the BCALLs that just go to a ret (this one and the WowWhatAnIncrediblyUsefulBCalls) should all redirect to a generic "the BCALL you linked to does absolutely nothing" page... Help consolidate.
--[[User:AndyJ|AndyJ]] 10:50, 24 Apr 2005 (PDT)
: Should this just be a redirect to WowWhatAnIncrediblyUsefulBCall? [[User:Jib|Jib]] 21:24, 4 November 2006 (PST)

Sandbox

2006-06-25T22:09:16Z

Jib:

a+bi

Ï‡Â²cdf(

Ï‡Â²pdf(

Ï‡Â²-Text(

â–ºDec

â–ºDMS

e

e^(

â–ºEff(

Equâ–ºString(

ï¿½

yay sandbox

68k:Ports:600010

2006-06-11T08:30:07Z

Jib:

[[Category:68k:Ports:By Address|600010]] [[Category:68k:Ports:By Name|HW1 LCD address]]

Bits 15-0: HW1 LCD frame buffer address, divided by 8. This address is read at the beginning of every frame.

This port has no function on HW2 or HW3.

68k:Ports:600012

2006-06-08T08:55:12Z

Jib:

[[Category:68k:Ports:By Address|600012]] [[Category:68k:Ports:By Name|LCD logical size]]

* Bits 13-8: LCD logical width = (64-n)*2 bytes ((64-n)*16 pixels)
* Bits 7-0: LCD logical height = (256-n)

If the LCD logical height is less, the screen will appear darker, because each line is visited more often.

This port can be written to one byte at a time without disturbing the other byte.

68k:Ports:600010

2006-06-08T08:41:25Z

Jib:

68k:Ports:600005

2006-06-05T03:53:48Z

Jib:

[[Category:68k:Ports:By Address|600005]] [[Category:68k:Ports:By Name|Power down]]

Turns off the CPU clock. The value outputted to the port specifies which conditions will cause the clock to restart.

* Bit 4: Auto-int 5 (programmable timer, see [[68k:Ports:600017|600017]])
* Bit 3: Auto-int 4 (link port)
* Bit 2: Auto-int 3 (USB port on Titanium, OSC2/2^19 on HW2)
* Bit 1: Auto-int 2 (keyboard)
* Bit 0: Auto-int 1 (OSC2/2^11)

Auto-int 6 (ON key) always wakes the CPU. Auto-int 6 must be acknowledged before writing to this port. (see [[68k:Ports:60001A|60001A]])

68k:Ports:600003

2006-06-05T03:24:39Z

Jib:

[[Category:68k:Ports:By Address|600003]] [[Category:68k:Ports:By Name|Bus Wait States]]

* Bit 6-4: Bus wait states (=7-n) for non-RAM accesses
* Bit 2-0: Bus wait states (=7-n) for RAM accesses

The TI-89 hardware needs no wait states.

68k:Ports:600000

2006-06-05T03:20:13Z

Jib:

[[Category:68k:Ports:By Address|600000]] [[Category:68k:Ports:By Name|Battery Voltage / 92 LCD contrast]]

This port controls I/O from pins 99 and 100 on the ASIC. It's used to check battery voltage on all calcs, and to control LCD contrast on the TI-92.

* Bit 7: Pin 100 output enable (keep =0)
* Bit 6: Pin 99 output enable (keep =0)
* Bit 5: Data to pin 100 (TI-92: used for LSB of LCD contrast)
* Bit 4: Data to pin 99 (not used)
* Bit 3: Data from pin 100 (not used)
* Bit 2: Data from pin 99 (1 if batt. voltage is above trigger level (see [[68k:Ports:600018|600018]])

68k:Ports:600001

2006-06-05T03:19:09Z

Jib:

[[Category:68k:Ports:By Address|600001]] [[Category:68k:Ports:By Name|Stack overflow protection / RAM size]]

* Bit 2: 1 = 128KB RAM, 0 = 256KB RAM
* Bit 0: 1 = Auto-int 7 generated for writes to 0x0-0x011F and 0xE00000-0xFFFFFF

68k:Ports:600001

2006-06-05T03:18:17Z

Jib:

[[Category:68k:Ports:By Address|600001]] [[Category:68k:Ports:By Name|Stack overflow protection / RAM size]]

{|
|-
| Bit 2: || 1 = 128KB RAM, 0 = 256KB RAM
|-
| Bit 0: || 1 = Auto-int 7 generated for writes to 0x0-0x011F and 0xE00000-0xFFFFFF
|}

68k:Ports:600001

2006-06-05T03:18:02Z

Jib:

[[Category:68k:Ports:By Address|600001]] [[Category:68k:Ports:By Name|Stack overflow protection / RAM size]]

{|
|-
| Bit 2 || 1 = 128KB RAM, 0 = 256KB RAM
|-
| Bit 0 || 1 = Auto-int 7 generated for writes to 0x0-0x011F and 0xE00000-0xFFFFFF
|}

68k:Ports:600000

2006-06-05T03:13:29Z

Jib:

[[Category:68k:Ports:By Address|600000]] [[Category:68k:Ports:By Name|Battery Voltage]]

This port controls I/O from pins 99 and 100 on the ASIC. It's used to check battery voltage on all calcs, and to control LCD contrast on the TI-92.

{|
|-
| Bit 7 || Pin 100 output enable (keep =0)
|-
| Bit 6 || Pin 99 output enable (keep =0)
|-
| Bit 5 || Data to pin 100 (TI-92: used for LSB of LCD contrast)
|-
| Bit 4 || Data to pin 99 (not used)
|-
| Bit 3 || Data from pin 100 (not used)
|-
| Bit 2 || Data from pin 99 (1 if batt. voltage is above trigger level (see [[68k:Ports:600018|600018]])
|-
| Bits 1-0 || not used
|}

Category:68k:Ports

2006-06-05T03:08:23Z

Jib:

[[Category:68k|Ports]]
Please read our page on [[Contributing]] before editing these pages!

Category:68k

2006-06-05T03:07:48Z

Jib:

[[Category:Calculator Documentation]]

This category contains documentation for the 68k family of TI calculators. (89, 89 Titanium, 92, 92+, Voyage 200)

Category:68k:Ports

2006-06-05T03:05:58Z

Jib:

[[Category:68k]]

Please read our page on [[Contributing]] before editing these pages!

Category:68k:Ports:By Address

2006-06-05T03:05:30Z

Jib:

[[Category:68k:Ports|Ports by Address/Number]]

See also [[:Category:68k:Ports:By Name|list of ports by name]].

Please read our page on [[Contributing]] before editing these pages!

Category:68k:Ports:By Address

2006-06-05T03:05:13Z

Jib:

[[Category:68k:Ports:By Address|Ports by Address/Number]]

See also [[:Category:68k:Ports:By Name|list of ports by name]].

Please read our page on [[Contributing]] before editing these pages!