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

BIOS upgrade in IBM 5160 doesn't work. Help needed!

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

    BIOS upgrade in IBM 5160 doesn't work. Help needed!

    Hi!

    I have an IBM 5160 with the 64-256k motherboard and the 11/08/82 BIOS.
    Original BIOS ROMs are labeled U18=1501512, U19=6359116.

    I wish to upgrade BIOS to the 05/09/86 version, but I don't own a programmer so I asked for help in a facebook group and a kind person helped me out.

    So I got the files in BIOS_5160_09MAY86.zip from minuszerodegrees programmed into 2 identical Nec D27C256D-25 EPROMS, but unfortunately they don't work With them installed the motherboard is dead, no beeps, monitor is powered down (LCD on VGA-card), and no blinking lights on the keyboard (i use a model M with AT/XT protocol support that blinks while detecting the XT protocol).

    So I asked the guy if he's sure about the programming, if he verified the writes, and such, and he is sure they are correct. I have no reason to doubt him, but if course, I can't verify the EPROMS myself.

    * Could it be a problem with the C in choosing 27c256? I read that they need 6V, do I have that? Should I check anything with multimeter?
    * Or are they to slow? -25 ? I read somewhere that -20 is required.
    * Could it be that the 16-bit VGA-card I'm using only accepts the 11/08/82 BIOS?
    * I also read on one site that shorting pin 1 and 28 is needed, but that was not for the IBM XT.

    I can return the EPROMS and ask for them to be verified again, but I'd like that to be my last resort, and I want to exclude if there's anything else I'm doing wrong first.

    Any help greatly appreciated!
    /Måns

    #2
    Originally posted by mrmanse View Post
    * Could it be a problem with the C in choosing 27c256?
    No, 27C256 chips will be fine

    * Or are they to slow? -25 ? I read somewhere that -20 is required.
    No, 250ns or faster will be fine.

    * Could it be that the 16-bit VGA-card I'm using only accepts the 11/08/82 BIOS?
    No, If the 16-bit vga card is working with the 11/08/82 bios it should work with the latest bios.

    I can return the EPROMS and ask for them to be verified again, but I'd like that to be my last resort, and I want to exclude if there's anything else I'm doing wrong first.
    Pull the new bios roms and make sure no pins are bent under (easy done)and you got the right chip in the right socket, If all OK, Put the original roms back in and make sure the the machine boots and works as it should.

    If the machine boots fine with the original roms back in then it looks like the new roms haven't been programmed properly or you got faulty ROM/'s ( I assume the guy didn't test the roms in an XT before he sent them to you ?).

    Comment


      #3
      Originally posted by Malc View Post
      Pull the new bios roms and make sure no pins are bent under (easy done)and you got the right chip in the right socket, If all OK, Put the original roms back in and make sure the the machine boots and works as it should.

      If the machine boots fine with the original roms back in then it looks like the new roms haven't been programmed properly or you got faulty ROM/'s ( I assume the guy didn't test the roms in an XT before he sent them to you ?).
      Thanks for the reply!

      Check the pins - check!
      Right chip in the right socket - check! (I actually also tried a switch, but it didn't work either)
      Chips correctly oriented - check!
      Original chips back and computer works - check!

      Ok, I'll talk to him about a return. And you assume correctly, to my knowledge didn't test them on a 5160.

      /Måns

      Comment


        #4
        Originally posted by mrmanse View Post
        * Or are they to slow? -25 ? I read somewhere that -20 is required.
        As Malc wrote, -25 is okay for the IBM 5160. From the'Revised Edition (April 1983)' and 'Revised Edition (March 1986)' editions of the technical reference: "The ROM is packaged in 28-pin modules and has an access time and a cycle time of 250 ns each."

        Originally posted by mrmanse View Post
        * Could it be that the 16-bit VGA-card I'm using only accepts the 11/08/82 BIOS?
        Try the Minimum Diagnostic Configuration procedure at [here]. If you hear the beeps, the BIOS is running.

        Originally posted by mrmanse View Post
        * I also read on one site that shorting pin 1 and 28 is needed, but that was not for the IBM XT.
        No pin shorting required. If pin shorting was required, I would have added a note to that effect in BIOS_5160_09MAY86.zip

        Comment


          #5
          Here is a wacky thought:

          According to http://www.minuszerodegrees.net/5160..._revisions.htm
          In the 11/08/82 BIOS revision, chip U19 contains part of cassette BASIC and thus is not critical to operation of the computer (only cassette BASIC is lost).
          For that reason, if the POST discovers that U19 has failed, the POST will display "F6000 ROM" and allow booting to continue.

          This is not the case for the later BIOS revisions, because in those, U19 also contains part of the BIOS. If U19 fails in those, the motherboard will appear 'dead'.
          Soooo, perhaps try putting the original U18 back in place with either of the burned eproms in U19. If that is correct, and the eproms aren't physically defective, then you should be able to boot, and then dump the contents of the ROM with debug.

          Comment


            #6
            I downloaded BIOS_5160_09MAY86.zip from www.minuszerodegrees.net, then burned the included ROM images to a couple of 27C256 chips. As expected, using those chips to upgrade the factory-fitted ROMs on my 5160 motherboard of type 64-256KB was successful.

            Comment


              #7
              @mrmanse: If you want to verify the ROMs yourself before you send them back, and you have a network card with a boot ROM socket, you can always put one of the chips into that, boot it up in the same or another PC, then dump the contents of the boot ROM to check it yourself.

              Comment


                #8
                Originally posted by SomeGuy View Post
                ...then you should be able to boot, and then dump the contents of the ROM with debug.
                Originally posted by Malvineous View Post
                @mrmanse: If you want to verify the ROMs yourself before you send them back, and you have a network card with a boot ROM socket, you can always put one of the chips into that, boot it up in the same or another PC, then dump the contents of the boot ROM to check it yourself.
                Thanks everybody for responses! The above is something I thought of it myself but couldn't figure out how to do it, nor google it. I do have a network card that is verified working on the very same computer, an 3com Etherlink II (3c503). So I could put each of the BIOS ROMS in the boot rom socket and read it? that would be great! How?

                Comment


                  #9
                  There is a guide on how to dump bios ROMs here: http://www.mess.org/dumping/dump_bios_using_debug
                  Unless I am horribly mistaken, the U19 rom is from F0000 to F7FFF.

                  But the hard part for most people is getting the files to a different computer for comparison. If that is a problem for you, then you probably just want to view the output on you screen.

                  For example, plop your original U18 in place with one of the burned eproms in U19, and in DEBUG type:
                  d f000:0000
                  and keep entering "d" until you reach f000:8000 (where the other ROM begins).

                  You don't need to compare every byte, but look at the start, middle, end, etc. If the ROMs are damaged or improperly programmed you may see all "00"s or "ff"s.

                  Comment


                    #10
                    Thanks for the link, it worked great! It didn't work with the etherlink II card, but to put each of the ROMS in the U19 socket was a great idea that worked very well!

                    I successfully read both of the ROMs a couple of times, while placed in U19 socket, using 2 different programs, and I got some really interesting results. Using the Etherlink II and that absolutely wonderful mtcp program suite I easily transferred them to my main computer

                    Both of the ROMs read correctly in the file area of 0x4000-7FFF, but are empty from 0x0000-0x3FFF. Yes, half of the ROM is correct, for both of them, the other half isn't. The first half of the U18 chip repeatedly read blank, but the U19 chip was unstable, and I got slightly different reads each time, although mostly zeroes. Does this behavior mean anything to you guys? Bad EPROM? Bad programmer? Bad eraser? Am i correct assuming that the problem isn't with my computer since one ROM read zeroes, and the other was unstable, which are different behaviors?

                    Comment


                      #11
                      Instability in the data read usually means a pin is not making contact with the socket. But if the pins look good, and it is firmly in the socket then it is probably a damaged chip.

                      The lack of data in the first half probably means it was incorrectly burned. For example, perhaps a 27128 type was selected during the burn process. In other cases it could also mean an incompatibility between a chip and motherboard, but in this case that 27c256 chip should work perfectly with no changes to the motherboard.

                      Comment


                        #12
                        Originally posted by SomeGuy View Post
                        The lack of data in the first half probably means it was incorrectly burned. For example, perhaps a 27128 type was selected during the burn process.
                        Sounds very resonable. I'll be getting new ROMs in a few days and I keep my fingers crossed!

                        Comment


                          #13
                          I have news!

                          I got two new ROMS from the same guy and learned something really interesting. By keeping the original U18 (1982 version) in it's socket, I was able to boot the computer and read other ROMS from the U19 socket.

                          I have 2 x 2 ROMS with the 09/05/86 BIOS
                          U18: NEC D27C2560-25 and National NMC27C2560 200
                          U19: two NEC D27C2560-25

                          The NEC's read correctly only from 0x4000h and above, the lower half of the ROM reading blank (or nearly blank), the NMC27C2560 read correctly. Could this be a faulty U19 socket on my mobo? Not likely, since one of the ROMs actually work fine.

                          So, I got a Minipro TL866A programmer to really find out what was going on, and I can now confirm that all the ROMs verify perfectly to the BIN files. So I conclude that the NEC D27C2560-25 aren't compatible with (at least mine) 5160 motherboard of the 64-256KB type.

                          Has anyone else encountered this?

                          Comment


                            #14
                            Are you sure that 0 on the end is correct, shouldn't it be the letter D ie: NEC D27C256D-25 ?
                            The NEC D27C256 is pin compatible with 27256 so should work, Unless the Eproms are faulty in some way.

                            Can you erase the non working eproms and reprogram them in your new programmer, Also see if your programmer software has an ID function to ID the eprom, I don't know about the Minipro so it may or may not have that option. Another thing is the NEC D27C256 requires 21V VPP and that might be a problem on some USB programmers.

                            Comment


                              #15
                              Originally posted by Malc View Post
                              Are you sure that 0 on the end is correct, shouldn't it be the letter D ie: NEC D27C256D-25 ?
                              Sorry, you are absolutely correct! The parts are all D27C256D-25.

                              Originally posted by Malc View Post
                              The NEC D27C256 is pin compatible with 27256 so should work, Unless the Eproms are faulty in some way.
                              Can they be faulty in a way that the eprom programmer reads them correctly, but the computer doesn´t? That's really strange.

                              Originally posted by Malc View Post
                              Can you erase the non working eproms and reprogram them in your new programmer, Also see if your programmer software has an ID function to ID the eprom, I don't know about the Minipro so it may or may not have that option. Another thing is the NEC D27C256 requires 21V VPP and that might be a problem on some USB programmers.
                              I believe the programmer does 21V, but I don't have an eraser. I did order some new eproms on ebay, hopefully the'll get here soon.

                              Comment

                              Working...
                              X