homebrew msx

Paragon (1236)

15-11-2009, 09:38

Hi all,

I was wondering if anyone had built its own MSX : home brew msx.
Since a few weeks i am thinking : my turbo R is not that fast , and
i'd like to have 3 slots instead of 2.
And it is such a pain to find a decent , good speed text editor , additionally
id like to have multi windows ( or screens ) one for editing mais asm file
one for editing include files one with msx dos sessin for compiling.
i dont need huge ram, 128kb is fair enough

Dont misunderstand me : this has nothing to do with msx3 or what ever
i just would like one machine for me since i like coding on the same HW
that it is supposed to run , cant get used to cross dev tools + emulator ...

to compile a diskrom it takes like 10mins on regular msx.

So if anyone has experience on homebrew mother board like the ciel3++
but with a ez80 ...
Is it possible to have a msx based on Z380 from leonardo padial , or is
it always an extension ?

Entrar ou registrar-se para comentar

Por legacy

Hero (570)

15-11-2009, 13:12

Yes, there is, have a look here here and here

Por Manuel

Ascended (19688)

15-11-2009, 13:27

You can also cross assemble on pc and run directly on real MSX using Nowind.

Por usuario_msx2

Paladin (763)

15-11-2009, 14:04

http://www.flickr.com/photos/44218601@N06/sets/72157622682682571/

Por iamweasel2

Paladin (722)

15-11-2009, 15:07

Well, Ademir Carchano did with his CIEL2+ turbo and Expert3 motherboards.

Por spl

Paragon (1470)

15-11-2009, 19:20

It's a pity that now CIEL2+ turbo and Expert3 are not available...

Por RetroTechie

Paragon (1563)

15-11-2009, 21:46

to compile a diskrom it takes like 10mins on regular msx.
If you'd want it to save time on compile cycles, then step 1 is: skip the 'build your own MSX' part. That would take so much time that any (small) savings you get from using it, are irrelevant. Better stick to cross-assemble and run on real HW then. Or grab the fastest MSX hardware you can find (either Turbo-R or 1chipMSX, I suppose).

Btw: I thought waiting times are for relaxing the programmer's brain... After chasing a bug, finding it, cracking the brain for a fix, and editing it into the source code?

Por NYYRIKKI

Enlighted (6094)

16-11-2009, 00:08

d like to have multi windows ( or screens ) one for editing mais asm file
one for editing include files one with msx dos sessin for compiling.

About 12 years ago I used actively setup where I had GFX9000 connected to another monitor. This way I could compile the sources on one monitor (DEVPAC2) and edit the sources on other monitor (TED) It makes it more easy when the errors don't dissappear from sight.

This also had other advantages... DEVPAC2 (=GEN80) compiles sources extremely fast on GFX9000 compared to using V9958

Por Leo

Paragon (1236)

16-11-2009, 14:10

yes i know it is going to be costly and i already have turboR , but still it is slow to scroll / compile .
A few year ago this would not have bothered me , but the thing is that i often have only 35mins or less
than 1hour time budget ahead when i plug msx , so it is not like i can fix more bugs or do more things with
faster msx , but it is a matter of time to do anything , i dont have more time per day, lets say on evenings
before going to bed i can do one or two trial to bug fix and that's it...
Building my own msx on the other hand is going to take some time ... i was more thinking in a cpu upgrade.
Like an fpga with sdram to replace Z80 DIP40 socket, so code in RAM executes in turbo mode while the rest is
regular speed,just like turbo 7MHz but with a one cycle cpu core ( instead of 4) and more MHz , more like 30 -50 MHz...
a Z80 with cache could make it also but cache system have to take into account mapper/slot switches , like
any output operation on A8/FC-FF flush cache : but too complicated ..

Por boomlinde

Resident (54)

17-11-2009, 12:19

I wonder what happened to the MSX-UNI. I'm drooling over the specs of that and it sounds like just what you're looking for.

Por FiXato

Scribe (1743)

17-11-2009, 12:30

Btw: I thought waiting times are for relaxing the programmer's brain... After chasing a bug, finding it, cracking the brain for a fix, and editing it into the source code?

imgs.xkcd.com/comics/compiling.png