Search the Community
Showing results for tags 'tk-ii'.
Found 5 results
-
I have a 1200XL that I did the 28 pin ROM socket change to so that I could go with an 800XL OS and Built-in Basic. I used the procedure at the top of the following topic, and it worked first time out of the gate. However I didn't have any of the 27C64 (8 Kbyte) EPROMS in my stock for burning the Basic, and I also didn't have a 27C128 (16 Kbyte) for the OS, so I substituted two 27C256 (32 Kbyte) ones instead and burned the OS and the Basic into the last bank of each. Since the additional pins above the original 24 pin sockets will be higher address select pins on the 27C256 chips, which in the case of U13 (the new single OS chip) and U12 (the new built-in Basic chip) appeared to be appropriately pulled high so as to select the upper bank in both cases, and the larger EPROMS worked when plugged straight in, no pins needed to be bent out of the socket. So after running a few tests, all looked quite fine, and I now had myself an 800XL (minus the PBI) in a 1200 case. The main reason I did this was so I could use my already modified HSIO 800XL OS code to access the SDrive addition in the 1200XL at a much faster pace. Well I got to thinking, wouldn't it be nice to use that extra ROM memory for two 16K OS ROMS and four 8K language ROMS (or a game or two) like I did on the 576NUC+. And being as how i already have a TK-II installed in the 1200XL, maybe I could work up a variation of the NUC TK-II firmware and utilize those extra ROM memory slots. What would it take? If I wanted it to work in a similar way to the NUC, then perhaps I could do the slot selection in a very similar way, only with a twist. Unlike the NUC, I would have the option of having either the HSIO OS or the Stock OS with each and every Slot. HOT KEYS SELECTION ALT+~ = HSIO OS ONLY CTRL+ALT+~ = Stock OS ONLY ALT+1-ALT+4 = HSIO OS + Language Slot 1-4 ALT+5-ALT+8 = Stock OS + Language Slot 1-4 Now power control would not be a part of the equation in this case, so I need a way to force a cold start whenever a new OS and/or language is selected. So I remember Bob Woolley's FREEZER circuit based on an XOR with the RD5 line and a momentary push button switch with the output going to GTIA PIN 11. Basically I would put the TK-II in charge of coordinating this, but essentially it would change what I'll call the ROM Banking that determines which OS and which Language will get addressed from the EPROMS, and every time that was to change it would perform that cold start function followed by system Reset to reinitialize the system with the new ROM configuration (the 576NUC+ cycles power instead). So to make all this happen I need 5 free and clear PIC I/O pins. Well I got that, and here's what that will look like... The ROM Banking bits B0-B1 will be connected to the EPROM address inputs A13 and A14 for U12 (4-in-one language ROM). B2 will be connected to A14 on U13 (2-in-one OS ROM). Both EPROMS will be identical 27C256 types, with the address Bank select bits stored in the non-volatile EEPROM within the PIC chip. R5 (RD5) is being used as an input to see if there is a Cart present. GT (GTIA pin 11) will see the output of a software XOR of RD5 and a Cold Reset (FREEZER) command, thus changing the Cart status byte prior to pulling the Reset line low. Unlike the original FREEZER based on the 74LS86, this one will be precisely timed and coordinated by the PIC chip and should always work reliably each and every time. AU (AUX) an extra presently unassigned I/O bit - could be used for a keyboard controlled SWAP or some other application. The bulk of the NUC TK-II firmware is already set up for most of what i need, but will require some tweaking to get it to work in this new application. From the user's point of view changing Operating Systems and/or Languages will be pretty effortless in practice, very much like it's presently done on the 576NUC+. Since the PIC will store the last known ROM settings, this means that the PS/2 keyboard can simply be used to create the desired setup and then unplugged if no longer needed. Next time the system is powered on irrelevant of whether a PS/2 keyboard is plugged in, the previous ROM settings will be restored.
-
So this will be a thru-hole based Dual Pokey board that incorporates a U-Switch type function and a Dual PS/2 Keyboard based on the TransKey-II (TK-II) hardware/firmware. It'll be pretty close to the same size as Lotharek's Stereo Board, except all the connectors will be on the lower end of the board close to the original Pokey chip, as opposed to the upper end like on Lotharek's board. This will allow better clearance in an XEGS, where the cartridge port resides. This is fully compatible with the U1MB BIOS Stereo detection and enable/disable via the U1MB /MO port. Here is the tested circuit... All of the parts get soldered in place, thus the need for the ICSP PIC programming port connections on J2. Most all of the components, other than connectors J1-J3 will reside inside the footprint of the two 40 pin Pokey sockets, and need to be of a low profile so as to allow the Pokey chips to be fully seated. This design specification has now been locked in and tested on real hardware. So the next job will be to lay out a PCB, and then have a few sample boards made for final testing. I will not be selling these boards, but just like the other TK-II boards I previously designed, they will be uploaded to OSH Park for purchasing by anyone who is interested. This is a DIY project, but hopefully someone will step up to make boards for those that do not possess the necessary skills to do so. Time line for this project is approximately one month, with boards being available on OSH Park soon after. The PIC MCU firmware is the same as used on the existing TK-II product line, and will also be in-circuit programmable with the JOY2PIC Atari-to-PIC programmer. Latest Firmware Download is available here: ataribits.weebly.com/design This should be a nice addition to the Stereo Board collection - Michael
-
How many mods has someone actually squeezed into a 600XL? I love the small size, but realistically I know there is limited real estate inside. It would be great to have everything: U1MB, VBXE, stereo pokey board, u-switch, TK-II or AKI, Rapidus, and I'd have to do the 64k and a/v mods. Is it doable or do I need to play it safe with a larger model?
-
Hi All, A little background. I have a U1M, SIDE2 combo going in an 800XL. I recently assembled a TK-II Stereo board without the PS/2 keyboard interface. I don't know if I have found a bug in FJCs firmware for SIDE2 (ver3.02), or U1M (ver3.02), or both or not at all. with the TK-II stereo board. Or if it is an issue with the TK-II board, or my 800XL. Here is what I can duplicate. With the A4 line connected to the TK-II board, the computer will boot, other times it won't. I'll just get a black screen. I have the Stereo option enabled in U1M. If I disconnect the A4 line from the board and turn it on, it'll boot constantly. When I boot it up and then connect the A4 line while it's on (probably not safe) and select a game, like Yoomp!, it'll say stereo not detected. I press reset, and it'll then detect stereo. If I power cycle the computer, SIDE2 Loader comes back up and the keyboard will not respond. Pressing Help and Reset, and go into the U1M setup, keyboard will respond, and I disable stereo mode and save, the keyboard will work again. -
TK-III Proposed Product Specifications May 2nd, 2016 (revised May 10th, 2016) Michael St. Pierre This will be the third generation TransKey product, with the focus to create a better mouse experience and also expand into other communication possibilities. The goal is to continue to have full hardware transparency, or in other words, not require any software drivers to support most features. This will be an internal upgrade only, similar to the TK-II-PIGGYBACK version. Keyboard Support Protocol: PS/2 (because its way easier than USB) Standard Features: Mimic existing TK-II Feature Set Improvements: Bring Atari Keyboard Compatibility up to 99.9% Mouse Support (See Newly Added Features) TK-II Mouse Arrow Key Emulation will be dropped Newly Added Features ST Mouse Emulation utilizing standard PS/2 Mouse Hardware Protocol: PS/2 Translated to simulated X/Y encoder (ST mouse look a like) fed to joystick port Left & Right buttons to mimic same ST mouse actions Middle button (when in mouse mode) = reserved - TBD Scroll Wheel (when in mouse mode) = reserved - TBD Trak-Ball Mode (via mouse emulation) Emulate 'trackball mode' for CX-22 and early production CX-80 Emulate 'joystick mode' for non Trac-Ball games and applications Note: late model CX-80 'trackball mode' was the same as an ST Mouse so will automatically work with TK-III's PS/2-to-ST mouse emulation Paddle Mode (via mouse emulation) PS/2 mouse scroll wheel emulates paddle controller pot PS/2 mouse left or right button = paddle trigger button Touch Pad Mode (via mouse emulation) Emulate CX-77 Touch Pad Emulate 'The Rat' Joystick Mode (via keyboard emulation) Option to use keyboard NumPad arrow and diagonal keys as joystick input RS232 Terminal Mode (driver-less version) Connection: Via built-in UART, level translation circuit, and D-Sub 9 pin male COM Port connection, 3 wire interface Baudrates: 2400, 9600, 19.2K Data Config: 1 start bit - 8 data bits - 2 stop bits - no parity Transmit mode is toggled (default = normal keyboard) Manual key presses will transmit ASCII equivalents via RS232 Received ASCII characters will send matching POKEY key presses (emulation) Incoming data will be fully buffered to match POKEY’s slower speed XON/XOFF software handshake for incoming flow control (keyboard has priority) Optional CTRL+SHIFT incoming data append feature (stealth mode) Parallel-to-Serial RS232 Transmission Mode (requires software driver, supercedes all other joystick/mouse related use when enabled) Making PortA an output, and then loading 8-Bit parallel data, initiates RS232 transmission when this feature is enabled See 'RS232 Terminal Mode' for hardware capabilities and connection specs Atari CX85 Hardware Support (no driver required) This would be a driver-less implementation of the CX85 numeric numpad hardware produced by Atari Keyboard Controlled Multi-Purpose Output One general purpose keyboard controlled switchable output Configurability Paddle, Joystick, Mouse, CX85 hardware and/or emulation will be swappable independently between joystick ports 1&2. The configuration will be stored in non-volatile EEPROM Project Timeline: Development to begin June 2016, and be completed by March 2017 (Best case scenario, but we all know how that goes. So don't hold your breath) Project Ownership: All materials and plans to be distributed within the Public Domain (this will be a DIY product or may be produced and sold by others for profit) Just to be clear, this will be an entirely new branch of the TransKey product line, and will not share either hardware or software with the previous versions (exception: some code will be migrated from TK-II, and the TK-II-INTFC board will be compatible). I reserve the right to change any and all specifications as proposed in this document. - Michael St. Pierre
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord