Re: ASCII: 6502 internal organization

Eli the Bearded <*@eli.users.panix.com> writes:

> In alt.ascii-art, Daniel  <[email protected]> wrote:
>> I am creating a set of facts about the 6502 processor and created a
>> diagram of the internal organization of the chip taken from a
>> programming book. How do you like it? Recommend any changes?
>> 
>> For the reference image go to page 42 in the linked pdf.
>> 
>> Doc: gopher://gcpp.world/9/phlog/docs/Programming_the_6502.pdf
>
> I'm not really a gopher user, but are there gopher clients that can
> display PDFs? I'm guessing if I pointed lynx at that it would just
> give me the option to download the file, and I'd have to view it
> separately.

Sorry for the inconvenience. It didn't occur to me that fellow usenet
users wouldn't have familiarity with gopher.

>> Here's the art: gopher://gcpp.world/1/phlog/6502Org
>
> That works in lynx. Some of the labels are missing. PCL / PCH are
> Program Counter Low / High, right? Where low and high are not low and
> high water marks (to show a range of memory), but low and high bit parts
> for holding an address larger than a bus width, correct? And A0 to A15
> are address lines, again unlabeled.

The key labels for PCL/CH are on the second page, you'd have to scroll down
to see it. I was thinking about moving them to the middle, below the
drawing so that it fits on one page. I was afraid that you wouldn't see
them.

The labels are identical with what the book had. 

Ultimately, what this is going to end up doing is comparing the 6502
processor with the 65C02 that'll be used on the upcoming Commander X16
project. Currently, I'm researching that processor as well.

> On a pure ASCII art level, I think I'd move the MUXes further to the
> right and give them longer lines, so instead of
>
>         KEY:          |  |      |       |      |             |
>                       |  |      |       |      :-------------:  .___.
>        X,Y: INDEX     |  |      |       |                    |->|   |
>             REGISTERS |  |      |       :--------------------|->|MUX|->AL
>                       |  :------|----------------------------|->|___|A0-7
>        S: STACK       |         |                            |
>
> Have, say:
>
>         KEY:          |  |      |       |      |             |
>                       |  |      |       |      :-------------:    .___.
>        X,Y: INDEX     |  |      |       |                    |--->|   |
>             REGISTERS |  |      |       :--------------------|--->|MUX|->AL
>                       |  :------|----------------------------|--->|___|A0-7
>        S: STACK       |         |                            |

I'll see if I have room to widen it. Gopher's really designed for 67
columns and I'm really close. I may able to tweak the drawing.

>
> Just so that they don't look so mashed together. In the same "not mashed
> together" way, maybe move the whole KEY section below the diagram?

I'll see if I can redesign the key to fit on one page vs two.

> Elijah
> ------
> any reason for only posting a gopher URL instead of the art?

By the time it occured to me to ask an opinion, the page was already
formatted for gopher output. Also, I use tmux with a multiple screen
split. Copy&paste goes across different screens making it difficult to
paste these drawings into another window. I'd have to paste one line at
a time. So I provided the link to save time.

Next time I create something I'll ask before formatting.

-- 
Daniel
Visit me at: gopher://gcpp.world