Jump to content

tf_hh

+AtariAge Subscriber
  • Content Count

    1,049
  • Joined

  • Last visited

Community Reputation

1,456 Excellent

9 Followers

About tf_hh

  • Rank
    Stargunner
  • Birthday 10/11/1970

Profile Information

  • Gender
    Male
  • Location
    Germany
  • Interests
    Microelectronics, Atari 8-Bit Hardware, Atari 16-Bit Hardware, ATMEL Microprocessors

Recent Profile Visitors

16,838 profile views
  1. Sure, but I never seen one. I have had some 1064 with cardboard boxes in my hand, but there never was any paper with it. When I´m remembering right, on the back side were some "instructions" how to attach it to the 600XL in several languages. Maybe one owner of the 1064 complete-in-box may sent a picture here.
  2. User docs? Didn´t know about any. But... when there´s something, what may be printed on it more than "Plug the 1064 into your computer´s parallel connector and you´re done"?
  3. Using standard CAS and RAS signals attached to the PBI. RAS is always active (for internal and external DRAM), because it´s needed for DRAM refresh. CAS (the CAS signal at the PBI) is latched using the 74LS32 and the 74LS375. As long A14 and A15 are low, the CAS transistions are only mapped to the internal DRAM. External CAS signal remains high. The simple reason why Atari design it this way: There was no possibility to "turn off" the internal DRAM without disabling the whole DRAM circuitry (like modern expansions do this with setting EXTSEL to low). So Atari can´t make another way to integrate the external expansion w/o modding the 600XL.
  4. I would suggest not to focus on PBI device or - design. The 1064 uses RAS and CAS lines, IMHO these signals are only attached to the PBI to support the 1064. Later XE machines haven´t these signals at the ECI. And, the first XL O.S. version (rev. 1) found in early 600XL machines hasn´t any PBI support as we know it from today. So if you have an O.S. ROM with the marking CO62024 instead the well-known CO61598, no PBI device like the KMK-IDE or MSC or the BlackBox won´t run, because this O.S. hasn´t the PBI protocol built in. You could make run / use the 1064 completely. Remove the 74LS32 chip and make a bridge between pin 8 and 10. The disables the "CAS16K" generation, so CAS (at the PBI) is enabled for all adresses to the PBI, and not only for adresses from $4000 up. Of course you must remove existing DRAM chips from the 600XL mainboard 🙂
  5. Why ever, but Atari did design it this way. When the 1064 is plugged to the 600XL, only the "last" 48 KByte ($4000-$FFFF) are mapped external. The first 16 KByte are always used internal. Easy test: Remove the both internal DRAM Chips - your 600XL won´t start 🙂 The internal wires are only needed to expand the multiplex address space from 16K to 64K. The inputs for the highest addresslines A14 and A15 are fixed to ground at the 600XL mainboard, so only A0...A13 is used, which means 16K address space. So the wires just add the missing both address lines and the 3rd one will enable generation of "CAS" for the whole 64 KB address space - by default it´s internal limited to 16K, too.
  6. The switch enables/disables the color generation. So if you set the switch to "no color", a multi-norm TV will switch to "PAL". If color enabled, it will switch to "SECAM". SECAM Atari computers always have no RF modulator.
  7. When there´s some demand, it´s no problem the create an external version of the 576 KB expansion for a good price. But Steve has to make the case
  8. The PM V2 document showed two 10 uF caps in line of L-Audio Analog and R-Audio Analog. Are these caps now on the PM V3 PCB installed or it´s useful to add them? If so, they should be shown in this picture.
  9. That is correct. Yellow = White and Red = Brown 🙂 Sorry, I didn´t found the time to update the manuals. The old cable is EOL 😞
  10. All Speedy versions work fine with the 2797, no issues known.
  11. Just to be sure, the following order must be used: 1. Power-On the 1050 without mechanics attached (for easier access). Also remove the Speedy or similar 2. While powered on, set a jumper between TP8 and TP9 3. Check pin 16 If the jumper was placed before power is switched on, the FDC doesn´t enter the test mode correct. Check pin 37 of FDC and pin 13 of the RIOT (6532) about continuity, these both pins are directly connected. Test (in standard usage mode, with standard ROM or with Speedy) the pin 37 of the FDC. Start DOS, give a single-density format command. Pin 37 of the FDC must be high. If a medium/enhanced density or double density (only with Speedy) format is sent, the pin 37 must be go to low. If not and continuity to 6532 is given, replace RIOT, then FDC itself.
  12. Sorry, wasn´t online some days here. Interesting find with the "gap" in the power trace, but it seems to be standard for this board revision: This is the same 65XEN mainboard and it also have this gap. I checked it against the schematics and reason is the seperation of +5V from standard to the 4050 buffer and video amp stage. There´s a coil between to filter the 5 volts. I´m pretty sure the developer saw the wrong routing after the final production mask was made and scratch these gap by hand from the mask. However, IMHO the first problem is the power switch itself regarding your posts here. I´ve often have had bad power switches. So exchange them first or solder for test a permanent bridge and plug/unplug the power. Now the black screen behaviour should be constant. The board you have is a PAL mainboard with PAL chips on it. You didn´t set your location in your profile, so if you´re living in NTSC areas, a black screen is normal. More typical is a red/brownish screen (PAL) or greenish (NTSC) when the computer has memory failures. Black scren - when T.V. norm is capatible - is more something around bad CPU, bad ROM, bad DRAM logic.
  13. Believe it or not, but I´ve thought about such a solution in 2017 already. But... under the bottom line it´s useless from my experience after dozens repaired 1050: 1. The major parts (digital interface) are in sockets and easy to change for a test 2. In all my years I have only ONE time a defect TTL chip (74s series) in a 1050 So mostly not running 1050s have problems in any analogue circuit. Often power (electrolytic caps, diodes or 78xx voltage regulators), SIO problems (defect 3086 transistor array or 6532 RIOT) or starting, but impossible to read/write disk failures based on problems in the analogue amplifier circuitry or the drive mechanic itself. A "1050 Sys-Check" could only detect some simple digital faults and maybe SIO defects, but all other stuff must be checked with an oscilloscope, or replaced "brute force" (change all). Even when some nice measurement breakout-boards (Arduino stuff for example) exists, such a testing tool would be check only 10-15% of all typical faults found "in the wild"... that´s not economic.
  14. Yes and no 😊 Yes to the first question: Sys-Check can substitute the 64 main memory of your bad XE machine. But, this is not made for permanent use, just for testing purposes. So no the 2nd question. If Sys-Check is set to substitute the main memory, then extended memory expansion doesn´t work and also attached cartridges will not be recognized. The reason is simple: Sys-Check must claim the system´s buss completely to let the machine ignore the faulty RAM. But, as Sys-Check beeing an external device, it can´t grab and re-route the internal signals from/to MMU, where cartridges are connected to. BTW, running a system with faulty RAM can have a lot of side-effects. Mostly these defect RAMs have influence to the databuss, and when you´re running the machine for a longer time, spurious hang-ups or restarts may happen. So it´s better you fix that.
  15. Works, I can confirm that.
×
×
  • Create New...