Thread View: net.micro.atari
5 messages
5 total messages
Started by jhs
Mon, 27 Jan 1986 23:22
16-bit upgrade for the 800XL, 130XE, etc.
Author: jhs
Date: Mon, 27 Jan 1986 23:22
Date: Mon, 27 Jan 1986 23:22
16 lines
1397 bytes
1397 bytes
Has anybody out there noted the news about the 65816 16-bit upgrade chip for the 6502? If what I read was correct, this will be a plug-in replacement for the 6502 which will extend the instruction set to handle a lot of 16-bit operations, sort of a la the 6800 or 8088 families. It is rumored that Apple is considering using this to upgrade their model II series, and it has occurred to me that it would be neat to drop one in my Atari 800XL. If it is truly upward compatible at the machine code level, that would open up a new world of enhanced performance and flexibility, such as (I speculate) 16-bit relative addressing, no more scrounging for zero-page addresses, etc. Any comments from the truly knowledgeable? -John Sangster jhs at mitre-bedford.arpa
Re: 16-bit upgrade for the 800XL, 130XE, etc.
Author: info-atari
Date: Tue, 28 Jan 1986 14:55
Date: Tue, 28 Jan 1986 14:55
8 lines
1051 bytes
1051 bytes
The 65816 book will soon be published by Brady. The author is David Eyes. If you really want one badly, give them a call, you might be able to bum a review copy if it is not yet on the shelves. Western Design Center did the design. Unfortunately their app-notes and other documentation are (last I looked) inadequte. The chip, on the other hand, is very real and very fast.
Re: 16-bit upgrade for the 800XL, 130XE, etc.
Author: Dan Fleysher
Date: Tue, 28 Jan 1986 15:02
Date: Tue, 28 Jan 1986 15:02
27 lines
2100 bytes
2100 bytes
re: dropping a 65816 into your Atari 800XL in place of the 6502, to upgrade it to 16 bits: Note that ANTIC (the screen display chip) is also an 8 bitter, so you would have to confine your display RAM to within 64K addresses. That's a real bummer - because one of the real advantages of lots of memory would be to have several alternate screens in memory at once and switch between them for animation, etc. Also, having usable RAM above the display area violates Atari 8-bit software architecture, which always puts the display area at the top of available RAM - the extra memory would not be usable by most 8 bitter programs (but you could make RAM disk(s) out of it). Then there's the problem that none of the existing memory decoding handles more than 8 bits. Also, you'd have to find a place to put the additional memory chips without destroying the RF shield - a packaging nightmare. Sounds like an awful lot of work to me, and when you finished up you would still not be able to run ST programs because of instruction set differences between the 65816 and ANTIC and their ST equivalents. Unless you want the experience of tearing apart your 8-bitter and learning something, I think you'd be further ahead to buy a new ST. (Of course, those of us who use our 8 bitters for word processing, game playing and bulletin-board-calling don't really need 16 bits anyway...) Dan -----------------------------------
Re: 16-bit upgrade for the 800XL, 130XE, etc.
Author: Vicious Oyster
Date: Wed, 29 Jan 1986 19:03
Date: Wed, 29 Jan 1986 19:03
41 lines
2791 bytes
2791 bytes
In an article, Fleysher.wbst@XEROX.COM (Dan Fleysher) writes:
>re: dropping a 65816 into your Atari 800XL in place of the 6502, to
>upgrade it to 16 bits: Note that ANTIC (the screen display chip) is
>also an 8 bitter, so you would have to confine your display RAM to
>within 64K addresses....
>having usable RAM above the display area violates Atari 8-bit software
>architecture, which always puts the display area at the top of available
>RAM - the extra memory would not be usable by most 8 bitter programs
>(but you could make RAM disk(s) out of it).
>
Unless I'm mistaken, that's merely a convention. The display memory
can be anywhere (subject of course, to the usual alignment restrictions).
>Also, you'd have to find a place to put the
>additional memory chips without destroying the RF shield - a packaging
>nightmare.
Granted, a problem; but there are a *lot* of 800XL's out there with 256K
and 512K already.
>Sounds like an awful lot of work to me, and when you finished up you
>would still not be able to run ST programs because of instruction set
>differences between the 65816 and ANTIC and their ST equivalents.
>Unless you want the experience of tearing apart your 8-bitter and
>learning something, I think you'd be further ahead to buy a new ST. (Of
>course, those of us who use our 8 bitters for word processing, game
>playing and bulletin-board-calling don't really need 16 bits anyway...)
I think you missed the point. The chip would be faster if only you
take into consideration the fact that it could do memory transfers and
arithmetic in 16 bits. I once attempted to alter the public domain
Small-C compiler to generate 6502 code, and I gave up when I got sick of
all the high-byte/low-byte garbage-- the compiler would have turned out
twice as big and twice as slow.
And who wants to run ST programs, anyway? (:-)
- Joel ({allegra,ihnp4,seismo}!uwvax!uwmacc!oyster)
P.S. I'd like to change my "split the group" vote from a no to a yes, just
so the obnoxious amiga/mac/ham-radio cross(and mis)-postings go away.
Re: Oyster Babble
Author: Rob DeMillo
Date: Thu, 30 Jan 1986 18:51
Date: Thu, 30 Jan 1986 18:51
17 lines
1138 bytes
1138 bytes
> And who wants to run ST programs, anyway? (:-)
>
> - Joel ({allegra,ihnp4,seismo}!uwvax!uwmacc!oyster)
This is what you get when you live in the water... ;-)
--
--- Rob DeMillo
Madison Academic Computer Center
...seismo!uwvax!uwmacc!demillo
"...I suppose you find the concept of a
robot with an artificial leg amusing?"
-- Marvin, the Paranoid Android
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads