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

XT-CF-lite v4.1 on 5155 not booting BIOS

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

    XT-CF-lite v4.1 on 5155 not booting BIOS

    I have put a freshly purchased XT-CF-lite v4.1 in my IBM 5155.
    The CF card I'm using is a 512 MB Sandisk that has been formatted for FAT.
    I uploaded the latest version of the XT IDE universal BIOS (tried both the XT and XTL build) to the 28C64 ROM (with a MiniPro) and set the ROM address jumpers to D0000 as I gather from the description that's the default address configured in the ROM code.
    Based on some articles I found, I also tried setting it to C0000 and CA000, all with the same result:

    When the machine passed the RAM check, it shows on screen a message with the address that is selected with the jumpers and then "ERROR" and I need to press F1 to continue.
    Then it continues to boot from floppy.
    It does not show anything from XT IDE universal bios and I also cannot access the card.

    I've taken out all the logic chips one by one and tested them with a chip tester, just to make sure that is not the problem.
    The ROM can also be read from and written to with a MiniPro, so that doesn't seem to be the problem either.

    Does anyone know what is going wrong?

    #2
    Can you boot to DOS and view the contents of that memory location with DEBUG? I'd look for bits that aren't set, or memory that repeats itself.

    Also, if you are creating your own rom image, make sure the checksum in the ROM image is updated.

    Comment


      #3
      Is there another hard disk controller in the 5155? I've only seen this kind of behavior when there is an I/O address conflict. The XT-IDE card needs to be sitting at a higher address than the ROM in the of the XT Hard Disk Controller. If it's lower it acts wonky.

      Comment


        #4
        I tested with all cards removed except for the floppy disk controller and the hercules graphics. I will also test without those.

        SomeGuy, do I need to do anything for that checksum or is this handle by the MiniPro (TL866) software?
        Just to be clear, I didnt create my own image but downloaded a build from the website.

        Comment


          #5
          You did configure the bios properly using XTIDECFG.COM FIRST before writing to EEprom ??, The XTL won't fit in a 8k rom.

          Comment


            #6
            Eprom writing tools don't change or even know anything about the checksum used by IBM PC BIOSs. This is supposed to be set by whatever tools are used to build and configure the XT-IDE ROM binary image.

            Comment


              #7
              Originally posted by Malc View Post
              You did configure the bios properly using XTIDECFG.COM FIRST before writing to EEprom ??, The XTL won't fit in a 8k rom.
              I was going to ask this same question. I'm pretty sure the files you download straight from the web repository will just make you sad if you flash them straight onto a ROM.

              If absolutely necessary you can run the configurator inside of an emulator like DOSBOX, just use the menu option to write the configured image back to the BIOS file you started with. (As I recall a giveaway if you've configured it correctly is the "odd-sized" image you started with will be written back as being exactly 8k or whatever.) Then write that file with your programmer.

              Re this:

              and set the ROM address jumpers to D0000 as I gather from the description that's the default address configured in the ROM code
              FWIW, the BIOS code is position-independent, you don't need to reconfigure the image for the starting address of the ROM. You *do* need to reconfigure it if you change the port address you map the IDE/CF interface to.
              My Retro-computing YouTube Channel (updates... eventually?): Paleozoic PCs Also: Blogspot

              Comment


                #8
                * In an IBM 5155, do not put the XT-IDE card into slot 8. Slot 8 is 'special'.

                * The settings of {base address = D0000 and I/O base = 300} are expected to work in an IBM 5155 that only has the IBM CGA card and IBM 5.25" Diskette Drive Adapter fitted.

                * At [here], see the note regarding XTIDECFG.COM. Use of XTIDECFG is the normal way to both suitably configure the XUB and then write it to the EEPROM on the XT-IDE card. XTIDECFG also creates the required 8-bit checksum (so you don't get a 'D0000 ROM' error at boot). You can put XTIDECFG.COM (a DOS program) onto a DOS boot floppy, executing it from A:

                * At [here], see the note regarding the downloaded XUB not necessarily being suitable out-of-the-box.

                * It is preferable to the partitioning and formatting of the CF card on the 5155.

                * Be aware of the 'non-standard master boot code' issue described at [here].

                Comment


                  #9
                  Originally posted by DutchMaker View Post
                  I have put a freshly purchased XT-CF-lite v4.1 in my IBM 5155.
                  I just now brought out a (static) bagged 'XT-CF-Lite Version 4.1' that I have.
                  On the bag, I had earlier written, "Card type in XUB is 'XTCF PIO'".

                  Comment


                    #10
                    I'm trying to go for the approach in which I load the BIOS file into a DOS emulator, run the configuration utility and then write back the BIOS to the image.
                    Does anyone know what emulator can do that?
                    It seems DOSBox cannot do this and I also can't get the BIOS to load in DOSBox-X and even if I did, I don't know if you can write to it.

                    I'm not able to write the utility to a floppy disk. That's exactly why I got this CompactFlash solution in the first place

                    Comment


                      #11
                      Originally posted by DutchMaker View Post
                      I'm trying to go for the approach in which I load the BIOS file into a DOS emulator, run the configuration utility and then write back the BIOS to the image.
                      Does anyone know what emulator can do that?
                      It seems DOSBox cannot do this and I also can't get the BIOS to load in DOSBox-X and even if I did, I don't know if you can write to it.
                      I have never tried using XTIDECFG in DOSBOX myself. I see that others have:
                      Post #6 at [here].
                      Post #13 at [here].

                      Presumably:
                      1. Run XTIDECFG
                      2. XTIDECFG: Read in downloaded-XUB-from-website BIN file
                      3. XTIDECFG: Configure the XUB
                      4. XTIDECFG: Export configured XUB to a BIN file
                      5. Use EPROM programmer to program new BIN file to EEPROM

                      Originally posted by DutchMaker View Post
                      I'm not able to write the utility to a floppy disk. That's exactly why I got this CompactFlash solution in the first place
                      In case of use to you, at [here] is a BIN file of the 2013-04-03 version of v2.0.0B3 from my XT-CF-LITE Version 4.1
                      Configured for the base I/O address of 300h (0x300).
                      Created direct from the EEPROM (AT28C64B) using my EPROM programmer.

                      Comment


                        #12
                        Thanks modem7,

                        I thought I had to somehow load the bios in the emulator and didn't realise the config util can just open and write the bin file.
                        After doing that, the BIOS shows up when booting my IBM 5155!

                        It now tries to boot from C (the CF card) which has no files on it yet, but at least I'm a bit further now.

                        Comment


                          #13
                          Originally posted by DutchMaker View Post
                          I thought I had to somehow load the bios in the emulator and didn't realise the config util can just open and write the bin file.
                          After doing that, the BIOS shows up when booting my IBM 5155!
                          Hah! Yeah, sorry if I wasn't clear. Obviously when you run it in DosBox or whatever the limited "auto config" functions don't work because there's no hardware or BIOS to probe (unless, I guess, you've made your own emulator that actually emulates an XTIDE) but the "read a bios file, manually config it, write it back to the file" loop works fine and gives you a usable BIOS.
                          My Retro-computing YouTube Channel (updates... eventually?): Paleozoic PCs Also: Blogspot

                          Comment

                          Working...
                          X