Toolchain setup for 16-bit Intel 8088 and 80188 step by step

[@Just-4-Fun]

This is very interesting, especially the gcc ia16-elf compiler. When I've the time I'll try it out with my homemade SBC (V20-MBC) with a V20 CPU.

[@cocusar]

I've been using the ia-16 for all my projects, but under Linux. nice changes you've added for Windows support.

[@aidandodds7672]

This is so usefull for my current project. Thanks so much for the tutorial and providing the release binaries. :)

[@der.Schtefan]

Please continue the series :)

[@SladorSoft]

Oh, yes, I will, definitely! I'm sorry I haven't produced any video for quite a long time, but it doesn't mean that I gave up. I already have a few videos planned. I had a few distractions on the way and lack of time, but I hope to release next video later in November. Thank you!

[@ModSlash]

I'd second that :) It has been a while now, what happened?

[@jozsiolah1435]

8089 is an I/O processor, and can be installed into the 8087 coprocessor’s socket. Probably, it can fit into the HDD FDD controller card.

[@pol.kraine7890]

what exactly is an I/O processor?

[@SladorSoft]

@jozsiolah1435 Yes. But in my case it is not that useful. Not only is it not easily available to buy, but also it is really designed for 8086/8 (not 80188) and - more importantly - it is effectively a DMA controller which the 80188 has already built-in.

[@SladorSoft]

@pol.kraine7890 - that's a fair question, but that was the language used by Intel themselves in their datasheet.

[@Kheir2]

Thank you a lot 🙏

[@tcpbox]

I followed your installation tutorial to the letter, including using the same cmake, make, etc. versions, but it doesn't work at all and gives the following error: [cmake] -- Detecting C compiler ABI info - failed This toolchain is not easy to install on Linux, Ubuntu doesn't compile. I thought that on Windows with the binaries it would be much easier, I was wrong.

[@SladorSoft]

Sorry to hear that it didn't work for you. Don't even let me start on building it on Ubuntu. The code (or dependencies between the repos) is very often broken and rarely builds. After producing my binaries I tried to update them later on, but there was always a problem with compilation at different stages. It's hard to troubleshoot your problem remotely, but you could check two things: 1) check if this toolchain is in the PATH: run a command line and type "ia16-elf-gcc.exe" and see if it can be found. 2) go to VS Code, press Shift+Ctrl+P and type "select a kit". Choose this option and check if you can see "GCC 6.3.0 ia16-elf" on your list of toolchains. If it's not there, rescan the toolchains (by again pressing Shift+Ctrl+P and typing "scan for kits") - but it will work only if it is in the PATH.

[@tcpbox]

@@SladorSoft Thank you for your answer, the project gcc-ia16 is a mess for someone that does not know it deeply, but I found out that gcc-ia16 is not mantained anymore and the project that should be used todays is build-ia16, I am trying it. If I get a succes in this task, I can send to you a version project that compiles in linux ubuntu, so you can make it available , if you agree with this.

[@henrydmr]

The Src for the Slador188 project no longer appears in GitHub as part of the Code ZIP download. Am I missing something or has a recent update removed the source?

[@SladorSoft]

Hi there! You're right. Well spotted - the "src" directory is gone (temporarily). I decided to re-create the whole repo and reorganise the directory structure before I go further into development. The "src" contained the example code used in one of my videos and I have moved it into "/turorials/01-Pico_as_IO_device" directory instead. The "src" is going to hold the actual BIOS code and the Raspberry Pi Pico code for the "MultiIO" controller instead. The idea is that along the development of the code in "src", I may occasionally write some temporary code to test/demo some particular feature - not related to the current state of "src" - in such case this code would go inside "tutorials". That's the idea. TLDR; Whatever was in "src" is now in "/turorials/01-Pico_as_IO_device" - apologies for recreating the whole repository.

[@henrydmr]

Thanks for the update, will check there. @@SladorSoft

[@artahir123]

is this the last video of the series ?

[@SladorSoft]

It is definitely NOT. I shall release next video soon - it requires lots of preparations, but I'm almost done. Any other videos I created recently were related to this series anyway. I made the most recent one, about running FreeRTOS on RPi Pico, because I needed the Pico in my Intel computer as a peripheral, which you will se working very soon. There will be at least three more videos before I create the new, finalised PCB, which I will show you later and start working seriously on its BIOS to get a complete, working computer.

[@0-oreo-0]

Hello,can you add an HDD so you can install windows on that pc so you can test some stuff with it. Thank you for reading this.

[@SladorSoft]

Thank you for your comment and interest ;-) One step at a time. I will add a HDD very soon. I would not call it a "PC" as it will never be a "PC-compatible". Nonetheless, I would like to keep some compatibility at the BIOS level. My next step (after adding a HDD) is to start writing the BIOS procedures which will allow booting from the HDD. We'll try DOS and/or elks. To run any Windows (I assume you talk about Windows 1.0 or 2.0) we would need at least a VGA-compatible graphics card. It's quite possible that the computer would need to be more PC-like than it is possible in this design to run these version of Windows. Also, they were barely known to the world (only Windows 3.0 became popular), so I'm not sure if there is any software to run on them at all, so not sure what kind of stuff you would like to test. Anyway, unfortunately - that's out of scope of this project. Thanks!

[@henumeramon08]

hey! i need some help, you may have this sound chip the "YMZ710-D" i have it and want to use it for a project but i cant find any information about it, maybe you can give me a hand on it, i understand if you cant

[@SladorSoft]

@user-fi5hr2ig4s Hi there! I don't know that chip at all. It does not seem to be used in any of the popular microcomputers from the 80s. I tried to search it in Google, but with no luck as well. Sorry, but it looks like I'm unable to help you. Take care!

[@henumeramon08]

Oh dang i prob got scammed then, it costed me 7 dollars and 50 cents man i was so excited, since im also making a breadboard computer so i wanted to add sound to it so i saw that chip and said "looks good enough" and ordered it ;( @@SladorSoft

[@SladorSoft]

Yeah, well - it happens. Next time consider using a well known chip, like, for example, AY-3-8910 (AY-3-8912) which was popular in the micros in the 80s. It's well documented and still available for almost free on AliExpress.

[@aka_vitfil]

Windows?