Announcement

Collapse

Forum Rules and 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.


Rule 1: 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.


Rule 2: 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.



Rule 3: 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.


Rule 4: "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.

Rule 5: 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

Unique S-100 computer (Z-80/Vector Graphic/Micropolis)

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

    I don't think you can put the serial port at address 4/5 (short of board hacks). The serial port is always at offset 2/3 from the base address which, in turn, is a multiple of four. Strap the board for I/O address zero which put the serial port at 2/3. The monitor PROM should initialize the 8251 at 2/3. Then you can play with it using the "I"N and "O"UT monitor commands.

    For example,

    Type "O"UT 02 31 and you should see a "1" show up on the terminal.

    Type a "1" on the terminal keyboard and then do an "I"N 02 and you should see a 31

    Mike

    Comment


      Originally posted by deramp5113 View Post
      Your board is jumpered at I/O address 4. That puts the serial port at I/O address 6/7 which is not supported by the monitor PROM or PC2FLOP. Move the A2 jumper back to pin 8 (A2 not) and that will put the serial port at I/O address 2/3 which is supported by PC2FLOP. Note this is still not the port address supported by the External Comm command which is typically I/O address 4/5.

      Mike
      Ok so I moved the A2 jumper to pin 8 and after reinstalling the board, the keyboard does not work. (Or at least it seems to think every keypress is an ESC?) Keyboard operates normally if Bit Streamer is not installed. After putting the jumper back to how it was originally, the keyboard works again. Any ideas what's happening?

      BTW I built an Arduino-based 2102 SRAM tester. Out of the 64 chips, I did have 1 bad one so I have a few on order. I've posted it on GitHub in hopes it may help others https://github.com/nullvalue1/Arduin...02-SRAM-Tester

      Comment


        Yeah, the keyboard port is at 0/1. Oh well. Let me see if there is an easy way to swap the parallel and serial ports on the bitstreamer so the serial port is at 4/5 and the parallel is at 6/7.

        Mike

        Comment


          Actually, this will be easier...
          With the board strapped at 4, the serial port is at 6/7. See if the same tests mentioned above work at 6/7:

          Type "O"UT 06 31 and you should see a "1" show up on the terminal.
          Type a "1" on the terminal keyboard and then do an "I"N 06 and you should see a 31.

          The version 4.1 monitor inits an 8251 at 6/7, so your 4.0 monitor probably does as well. If not, we can use a few OUT commands and init the 8251 manually.

          Mike

          Comment


            Both the 4.0 and 4.1 monitors actually contain a minimal terminal program (E command) that makes this sort of troubleshooting a little easier (at least it helped me sort out the com ports on the Bitstreamer II and ZCB

            Comment


              Originally posted by MikeS View Post
              Both the 4.0 and 4.1 monitors actually contain a minimal terminal program (E command) that makes this sort of troubleshooting a little easier (at least it helped me sort out the com ports on the Bitstreamer II and ZCB
              The E command did not work for him because it uses the serial port at I/O address 4/5 and there is not an easy way to put the serial port on the Bitstreamer-I card at address 4/5.

              Mike

              Comment


                Originally posted by deramp5113 View Post
                Actually, this will be easier...
                Type "O"UT 06 31 and you should see a "1" show up on the terminal.
                Type a "1" on the terminal keyboard and then do an "I"N 06 and you should see a 31.
                Ok this looks like progress.. "O" 06 31 does produce a "1" on the terminal! However after typing the "1" on the terminal, and an "I" 06, I only get "00".. So I'm able to transmit but not receive at the moment. Terminal settings are baud: 300, data: 8 bit, parity: none, stop: 1 bit, flow: none. I tested the terminal/cable is transmitting fine by talking to a modem. Should I run some continuity tests on the the S100 side or could this be software related?
                Last edited by nullvalue; April 28, 2020, 08:47 AM.

                Comment


                  We have to know more about what you're using for a terminal and the data cable in order to determine where the problem may be.

                  If you are using an actual terminal, it is quite possible the terminal is not transmitting if it's not seeing a handshake line it requires. Or are you using a PC and terminal emulator? How is your data cable wired from end to end?

                  Mike

                  Comment


                    Using a PC w/ TeraTerm with a USB to Serial converter. DB9 to DB25 cable. Tested the same adapter & cable by plugging in an external modem and am able to read/write to it - so I don't think the problem is on the terminal end or with the cable.
                    Last edited by nullvalue; April 28, 2020, 10:42 AM.

                    Comment


                      I was also able to verify the ribbon cable bringing the signal from the DB25 port to the 24-pin DIP socket works for all pins/lines.

                      Comment


                        That is why I am asking about a terminal versus a PC. Since a modem provides all handshake lines, it's quite possible that a terminal works fine with a modem but that same terminal may not work with a computer that is not asserting the required handshake lines on the required pins. I have seen you refer to it as a "terminal" in these recent posts, so I needed to know what your terminal actually is.

                        Since your terminal is a PC running Teraterm, and Teraterm is happy in three-wire mode, we can rule out an improperly driven or wired handshake line as the issue for data not reaching the Bitstreamer. That information helps. I'd now use a scope to probe the data-in path from the DB-25 connector, through the ribbon cable, DIP socket, jumpers, receiver, and to the 8251 in order to pinpoint where reception fails.

                        Mike

                        Comment


                          I've had very inconsistent results with USB serial adapters at 110 and 300 baud. I'd set the Bitstreamer to 9600 baud.

                          Mike

                          Comment


                            At the S100 end, should I be following DB25 pin 2 or 3? I always get the 2 confused.

                            Comment


                              Well, crap. Not sure what just happened but I busted something. Just was hooking up the scope to the Bit Streamer. Put the ground lead on the negative side of a cap, tapped the probe to the positive side and the screen went to random characters. Now the machine won't boot to the monitor anymore. Just uninitialized garbage screen. Same results with or without the Bit Streamer. There was no pop/smoke or anything like that. I know I didn't touch anything else on accident. Ugh what have I done...

                              Edit: retraced my steps... There's a via just above the negative end of the cap - that via runs to +5. My alligator clip must have shorted the two. Have just the Flash Writer, 12K PROM/RAM, and Z80 CPU boards installed. All regulators check out. What else can I check?
                              Last edited by nullvalue; April 28, 2020, 05:34 PM.

                              Comment


                                Look on the schematic for the cap you attached to so you can determine what shorted to what. Is the negative side of that cap actually ground or is it possibly a negative supply? I've done that before with an older scope for which the probe ground is a hard ground and shorted out the negative supply.

                                Mike

                                Comment

                                Working...
                                X