Troubleshooting - Revision history

Mizapf at 19:41, 25 May 2021

2021-05-25T19:41:53Z

← Older revision		Revision as of 19:41, 25 May 2021
Line 64:		Line 64:
	Second digit: Error type		Second digit: Error type

	{\| class="plain"		{\| width="80%" class="plain"
	! Code		! width="5%" \| Code
	! Meaning		! width="15%" \| Meaning
			! width="75%" \| Explanation
	\|-		\|-
	\| 0		\| 0
	\| Device not found. The specified device could not be found in the system. This may happen when you spelled the device name wrong (like DKS1) or when you wrote it in lowercase*.		\| Device not found
			\| The specified device could not be found in the system. This may happen when you spelled the device name wrong (like DKS1) or when you wrote it in lowercase.
	\|-		\|-
	\| 1		\| 1
			\|
	\|		\|
	\|-		\|-
	\| 2		\| 2
			\|
	\|		\|
	\|-		\|-
	\| 3		\| 3
			\|
	\|		\|
	\|-		\|-
	\| 4		\| 4
			\|
	\|		\|
	\|-		\|-
	\| 5		\| 5
			\|
	\|		\|
	\|-		\|-
	\| 6		\| 6
	\| Device or media error. The drive may be defect, the floppy disk scratched, the cables ~~may be~~ broken. Also, the floppy disk may require to be reformatted or replaced.		\| Device or media error
			\| The drive may be defect, the floppy disk scratched, the cables broken. Also, the floppy disk may require to be reformatted or replaced. This error is not caused by an improper use of the command but has physical origin.
	\|-		\|-
	\| 7		\| 7
	\|		\| File error
			\| The specified device was found, but not the file. Maybe the file name was misspelled or written in the wrong case.
	\|}		\|}

	*The lowercase issue is a particularly attractive trap for new users. The TI systems define everything in uppercase (with depressed Alpha Lock), the lowercase letters are mostly used for text display. Also, the lowercase letters are shown as small capitals. In doubt, write DSK1 with Shift held down.		The lowercase issue is a particularly attractive trap for new users. The TI systems define everything in uppercase (with depressed Alpha Lock), the lowercase letters are mostly used for text display. Also, the lowercase letters are shown as small capitals. In doubt, write DSK1 with Shift held down.

Mizapf at 19:30, 25 May 2021

2021-05-25T19:30:56Z

← Older revision		Revision as of 19:30, 25 May 2021
Line 27:		Line 27:

	The image shows the bit numbers on the circuits. Note that Texas Instruments uses a big-endian bit order, i.e. bit 0 is the most significant bit (2<sup>7</sup>), and bit 7 is the least significant bit (2<sup>0</sup>). Accordingly, if your failure symptom is Mask 11011111, this means bit 2 is stuck at 0.		The image shows the bit numbers on the circuits. Note that Texas Instruments uses a big-endian bit order, i.e. bit 0 is the most significant bit (2<sup>7</sup>), and bit 7 is the least significant bit (2<sup>0</sup>). Accordingly, if your failure symptom is Mask 11011111, this means bit 2 is stuck at 0.

			== Disk-related issues ==

			=== TI BASIC error codes ===

			Error codes are two-digit codes like

			I/O ERROR 56

			First digit: Command which failed

			{\| class="plain"
			! 0
			! 1
			! 2
			! 3
			! 4
			! 5
			! 6
			! 7
			! 8
			! 9
			\|-
			\| OPEN
			\| CLOSE
			\| INPUT
			\| PRINT
			\|
			\| OLD
			\| SAVE
			\|
			\|
			\|
			\|}

			Second digit: Error type

			{\| class="plain"
			! Code
			! Meaning
			\|-
			\| 0
			\| Device not found. The specified device could not be found in the system. This may happen when you spelled the device name wrong (like DKS1) or when you wrote it in lowercase*.
			\|-
			\| 1
			\|
			\|-
			\| 2
			\|
			\|-
			\| 3
			\|
			\|-
			\| 4
			\|
			\|-
			\| 5
			\|
			\|-
			\| 6
			\| Device or media error. The drive may be defect, the floppy disk scratched, the cables may be broken. Also, the floppy disk may require to be reformatted or replaced.
			\|-
			\| 7
			\|
			\|}

			*The lowercase issue is a particularly attractive trap for new users. The TI systems define everything in uppercase (with depressed Alpha Lock), the lowercase letters are mostly used for text display. Also, the lowercase letters are shown as small capitals. In doubt, write DSK1 with Shift held down.


			=== Extended Basic error codes ===

			=== Controller error codes ===

			These are the error codes from the PHP1240 Disk Controller Card (the original TI disk controller). They are usually only seen during operations of the Disk Manager cartridge.

			{\| class="plain"
			! width="33%" \| Operation
			! width="15%" \| Code
			! Meaning
			\|-
			\| Various operations
			\| style="text-align:center" \| 06
			\| Device error, like track 0 not reached, no READY signal
			\|-
			\| Read Sector
			\| style="text-align:center" \| 07
			\| Invalid sector number
			\|-
			\| Seek
			\| style="text-align:center" \| 11
			\| Wrong track ID in header
			\|-
			\| rowspan="4" \| Read Address (also during Read Sector)
			\| style="text-align:center" \| 06
			\| Wrong side in header
			\|-
			\| style="text-align:center" \| 21
			\| Sector header not found
			\|-
			\| style="text-align:center" \| 22
			\| CRC error in sector header
			\|-
			\| style="text-align:center" \| 23
			\| Byte buffer overflow (failure to fetch byte on time)
			\|-
			\| rowspan="4" \| Write Sector
			\| style="text-align:center" \| 28
			\| Compare error (data)
			\|-
			\| style="text-align:center" \| 31
			\| Sector header not found
			\|-
			\| style="text-align:center" \| 33
			\| Byte buffer underflow (failure to deliver byte on time)
			\|-
			\| style="text-align:center" \| 34
			\| Write protection
			\|}

Mizapf at 11:54, 17 July 2016

2016-07-17T11:54:41Z

← Older revision		Revision as of 11:54, 17 July 2016
Line 21:		Line 21:
	Image:Vram_fe.png \| Mask 11111110		Image:Vram_fe.png \| Mask 11111110
	</gallery>		</gallery>

			If you found your screen output in this gallery, you will have to replace the failing video RAM circuit on the board. The video RAM is on the left side:

			[[File:Vram.jpg]]

			The image shows the bit numbers on the circuits. Note that Texas Instruments uses a big-endian bit order, i.e. bit 0 is the most significant bit (2<sup>7</sup>), and bit 7 is the least significant bit (2<sup>0</sup>). Accordingly, if your failure symptom is Mask 11011111, this means bit 2 is stuck at 0.

Mizapf at 21:51, 7 August 2015

2015-08-07T21:51:04Z

@@ Line 2: / Line 2: @@
 We will discuss some trobleshooting strategies on these pages.
 == Video issues ==
 Sometimes you can find weird screen outputs on real TI consoles, some of them shown on Ebay. In most cases the problem is a defect RAM circuit. The video memory is implemented by 8 circuits of TMS4116 (16K x 1); that is, each circuit hold exactly one bit of each byte.

Mizapf at 21:34, 7 August 2015

2015-08-07T21:34:30Z

← Older revision		Revision as of 21:34, 7 August 2015
Line 3:		Line 3:
	We will discuss some trobleshooting strategies on these pages.		We will discuss some trobleshooting strategies on these pages.

	~~LATER~~
			== Video issues ==

			Sometimes you can find weird screen outputs on real TI consoles, some of them shown on Ebay. In most cases the problem is a defect RAM circuit. The video memory is implemented by 8 circuits of TMS4116 (16K x 1); that is, each circuit hold exactly one bit of each byte.

Mizapf: Protected "Troubleshooting" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

2014-11-09T13:48:45Z

Protected "Troubleshooting" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

← Older revision	Revision as of 13:48, 9 November 2014
(No difference)

Mizapf: Created page with "So your good old TI does not feel good recently? Or you have bought a console or expansion on the Internet and wonder whether something is wrong, or whether you just don't use it..."

2014-11-09T13:48:15Z

Created page with "So your good old TI does not feel good recently? Or you have bought a console or expansion on the Internet and wonder whether something is wrong, or whether you just don't use it..."

New page

So your good old TI does not feel good recently? Or you have bought a console or expansion on the Internet and wonder whether something is wrong, or whether you just don't use it correctly?

We will discuss some trobleshooting strategies on these pages.

LATER