Announcement

Collapse

Forum etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


"PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

Custom 4K ROM for Big Tandy computers like the Model II

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Custom 4K ROM for Big Tandy computers like the Model II

    Hi,

    As I am working on the 512K RAM board for the model II I also needed a way to test it.

    For that reason I did build a 4K ROM board that connects to the original ROM socket using a flat cable.
    Working on the custom ROM made the RAM board development come to a temporary halt.
    The ROM board has room for 2 ROMs (2716 or 2732). So the original ROM can be used without too much trouble. Just change a jumper and reset the system.
    I used a ZIF socket for the second ROM, making inserting a new EPROM very easy.
    By bringing the already present address select for the 2nd 2K to the board, I am able to use a 4K chip. I showed to board to some people at TA18.
    By now, BigTMon as the latest content for my ROM is called, includes RAM bank test, keyboard scan code test, RAM display and edit, full port scan and serial port communication.
    It will also display a message when the Model II has no RAM memory available.
    Using the serial port to hook up another Tandy computer (Model 102), I can run the monitor program without a Model II keyboard connected. Useful when some keys on your keyboard no longer work.
    Also the Model II can now be used as a basic serial terminal by using the new ROM.
    Attached is a picture of the board hanging on the back of my Model II and a picture showing the Model II, Model 102 combination (with the keyboard DIN connector not connected)
    The board:
    Screen shot: .
    The code for BigTMon is written in Z80 assembler and assembled using ZMAC. Testing is performed using the TRS80GP emulator and on my Model II.
    The screen shot shows that my machine is currently equipped with 2x 64K RAM board and a HD controller (present in bank 14 and 15). A HD controller has incomplete bank decoding, hence it shows up twice.
    Until now the new ROM board has only been installed in a Model II, not yet in a 12, 16 or 6000.
    One of the things I learned using the monitor was that you cannot map memory bank 0 to the upper 32K of RAM. When you try, there will be no RAM active in that location.
    You can only map banks 1 to 15 in the upper 32K of address space.
    When carefully reading the technical manual of the model 16 it becomes clear why this is the case. By mapping bank 0 to the upper 32K, this address space becomes available as the window to the memory for the 68000.
    I had not yet taken that into account in my first 512K board design.
    One of the tests I'm considering to incorporate is testing for presence of a working video card.
    This leads to the following question; will the monitor get damaged when the Model II is powered up without a video card (or with a defective card), resulting in no video signal being generated?
    Does anybody have experience with that?

    Thanks,
    LaserVision

    #2
    LaserVision, it appears that the image attachments are broken.

    This is an awesome project. Am I to understand that you have full serial terminal support now built into the ROM so we out run a headless Model II/16?

    I look forward to seeing this in action at Tandy Assembly 2019!
    Pete
    http://pski.net

    Comment


      #3
      Originally posted by LaserVision View Post
      One of the tests I'm considering to incorporate is testing for presence of a working video card.
      This leads to the following question; will the monitor get damaged when the Model II is powered up without a video card (or with a defective card), resulting in no video signal being generated?
      Does anybody have experience with that?
      I looked at the Model II technical bulletins here: https://github.com/pski/model2archiv...Searchable.pdf

      II:025 suggests damage will occur. At least in the case of a VDG board (the one with the 6845 on it) that is not initialized by the Z-80.

      An optimist might suppose that with no VDG board installed there may not be a problem. That would be a sensible design and one might guess that a video board not being driven will just do nothing.

      On the other hand, I can't remember where I saw it (the technical reference manual, maybe), but there was some advice to the technician to be careful when working on the machine. If upon power-up you hear the CRT whine heavily you have about 3 seconds to shut it off before damage occurs. That may have been in the context of repairs specific to the VDG board or just general advice; I don't quite recall.

      Maybe other service bulletins or repair guides imply what happens without a VDG board.

      Comment


        #4
        To be safe, I suggest unplugging the CRT analog board card edge connector if you plan to run without a VDG as the CRT does have a minimum sync requirements. A defective VDG could certainly damage the CRT if the sync signals are out of spec.
        Pete
        http://pski.net

        Comment


          #5
          A new try for the picturesModel II - Model 102 Serial combi.jpgBoard at back of Model II.JPG

          Comment


            #6
            Pete,
            Unplugging the CRT analog board is an excellent suggestion.
            I would indeed feel much better with the CRT without power when performing tests.

            LaserVision

            Comment


              #7
              Originally posted by LaserVision View Post
              Pete,
              Unplugging the CRT analog board is an excellent suggestion.
              I would indeed feel much better with the CRT without power when performing tests.

              LaserVision
              What can I do to get one of these boards?
              Pete
              http://pski.net

              Comment


                #8
                Originally posted by pski View Post
                What can I do to get one of these boards?
                Whatever it is, I'll do it twice.

                Comment


                  #9
                  Hi guys,

                  Good to hear there is some interest.
                  Would you opt for a bare board plus programmed GAL (for decoding) and assemble the board yourself based on the provided schematic?
                  Or would you prefer a completely assembled and tested board, including BigTMon in EPROM, flat cable (at desired length) and ZIF socket?

                  Of course I'll bring complete boards to TA19, but that is still some months to go /

                  Comment


                    #10
                    I’d prefer the completely assembled option. I have enough projects sitting around yet to be built!
                    Pete
                    http://pski.net

                    Comment


                      #11
                      @Ruud
                      Nice project you started, I want to take part of it.
                      I want to go for the PCB only, I have most of the components available.
                      And of course the BigTmon data, GAL data and the BOM list, if you want to supply this data.

                      Comment


                        #12
                        Fully assembled and tested for me.

                        It would be perfect if BigTMon could download and run code from the RS-232 similar to what the Model 4P can do. Actually, it doesn't have to be that fancy. Just having a command to put bytes into memory and one to execute would be enough to bootstrap.

                        But I'm sure I could manage to write and burn my own code if need be.

                        Comment


                          #13
                          I would personally like the bare board option. Depending on which GAL and EPROM, I can program those myself.
                          --
                          Thus spake Tandy Xenix System III version 3.2: "Bughlt: Sckmud Shut her down Scotty, she's sucking mud again!"

                          Comment


                            #14
                            Hi Guys,

                            I took the suggestion of loading bytes to the Model II and implemented it (together with dumping data from the Model II).
                            This is done through the RS-232 link.
                            Attached pictures show the text file which is uploaded by the Model 100.
                            After uploading (Start memory location 2000h, Length 0022h bytes) the file, execution starts at 2000h.
                            The example displays a string on screen and is preceded by char 1, which translates into a CLS.
                            At the end, the code performs a RST 10h, which I use to get a char from keyboard or RS232. Then jumps into the monitor.
                            Source in HEX.jpg

                            HelloMessage.jpg

                            DumpingMem.jpg

                            DumpOnM100.jpg

                            The last 2 pictures show dumping of memory (in Hex format) to the serial port and the result on the M100. This format can be reused when loading files upto the Model II.
                            The reverse text is the progress during dumping. It is not fast at 1200 baud, but performs the job.

                            Regards,
                            Laservision

                            Comment


                              #15
                              That's fantastic! Well done.

                              Comment

                              Working...
                              X