jamieiles / 80x86 Goto Github PK

Having the MCGA enabled causes writing to the sd card crash (on de0-cv). Writing will work if MCGA is disabled.

Hi Jamie, its a little unclear how to run the simulator after ./scripts/build

I get the following error when running ./_build/build/sim/simulator

./_build/build/sim/simulator: error while loading shared libraries: libsimdisplay.so: cannot open shared object file: No such file or directory

Is this related to running cmake? Could you please provide some command line examples to get it running?

I'm trying to build your project for my DE0-NANO. I've read the development guide several times, but I think I'm missing some critical piece of understanding.

./scripts/build appears to fetch & build; all CI tests pass, but I'm confused as to what build targets to invoke to create the quartus project, and how to build and execute the verilator sim environment. Hoping you could please provide some insight here.

Thanks in advance!

Hi Jamie, this is a very interesting project you have here. I’m thinking of porting the rtl to small xilinx spartan-6 based devices (lx9 and/or lx16) . I was wondering how altera/intel specific your code is and how you assess the amount of work it would take. Are there any specific requirements on the fpga like internal sram, fifos and such?

Hi @jamieiles wonderfull project you have here!

I have an Altera-DE0-CV board here and i've been trying to get monkey island 1 running on it.
CGA mode works okay monkey c k i, however its very limited in colour palette.
When I enable MCGA mode monkey m k i, the game appears to stall at startup.

I am using the .sof file provided on your website (checksum: 02580D43) as well as your provided freedos disk image. Do I need to recompile from the latest source?

Are there any steps I am missing to get MCGA working?

Thanks!

Hey Jamieiles!

First off, thanks for publishing this project, it's super neat. I really like how you have it set up thru Docker and CMake. It really makes it feel much more akin to normal software development.

Can I ask what your workflow for working on this is like? I feel like I'm missing a few steps and it's making it a bit difficult to do work on it. So far, I've been running CMake, then attaching to the s80x86-dev docker image to do builds and stuff, but I feel like I'm missing a lot of power of the other scripts. I have read the documentation that it builds and digested it the best I can, but I'm just not groking the intermediate steps as much as I'd hoped.

I'm also happy to flesh out the documentation with the additional info if you wouldn't mind tossing it out there :)

Thanks!

Is it possible to extend support for:

• NEC V20 series
  • NEC x86 instructions
  • 286 real mode instructions
  • 8080 mode
    • Z80 x86/8085 and x86/Z80 machines (single-chip or two-chip)
    • 8085 x86/8085 and x86/Z80 machines (single-chip or two-chip) - undocumented instructions are implemented here.
  • PC/XT I/O and peripherals
  • additional I/O and peripherals
    • V25
    • V53A
    • V55SC
    • RX116 RTOS
    • 8251
    • 8253/8254 remaining modes
    • 8255 parallel port
    • RTC
  • additional features
    • interrupt vector numbers compatible with Intel x86
    • 16MB addressing V33 type
    • 16MB addressing V55 type
    • separate address and data buses
      • Weitek 1067 FPU
      • 80287
    • PC/AT I/O and peripherals
  • NEC FPUs
    • x87 μPD72091 FPU
    • x87 μPD72191, D9008D FPU - FPOWER X^y = e^(y*logeX)
    • non-x87 FPU NEC 72291
• 8087
• 80187
• Am9511/Intel 8231 APU (works with 8080/8086) - z88dk-ticks has an implementation here.
• Am9512/Intel 8232 FPU (works with 8080/8086)