RC2014 is a simple 8 bit Z80 based modular computer. It is inspired by the home built computers of the late 70s and computer revolution of the early 80s. It is not a clone of anything specific, but there are suggestions of the ZX81, UK101, S100, Superboard II and Apple I in here. It nominally has 8K ROM, 32K RAM, runs at 7.3728MHz and communicates over serial at 115,200 baud.
RC2014 is a simple 8 bit Z80 based modular computer. It is inspired by the home built computers of the late 70s and computer revolution of the early 80s. It is not a clone of anything specific, but there are suggestions of the ZX81, UK101, S100, Superboard II and Apple I in here. It nominally has 8K ROM, 32K RAM, runs at 7.3728MHz and communicates over serial at 115,200 baud.
Now I'll get to the point. I see the future of the RC2014 ecosystem as "leveling up" with the user. Received a grab bag of Diligent PMods in the mail the other day: air pressure, ADC, temperature, servo control etc etc etc and all work with SPI or I2C. My thought was: "Wouldn't this be cool to build into the RC2014 world and for example access a motor control module which uses 201X parts from MSBasic written in 1980?"
Now I'll get to the point. I see the future of the RC2014 ecosystem as "leveling up" with the user. Received a grab bag of Diligent PMods in the mail the other day: air pressure, ADC, temperature, servo control etc etc etc and all work with SPI or I2C.
I don't necessarily include myself in this category but if the "experts" get scared off I have no reason to stick around. Not really interested in helping someone write a very basic algorithm in z80 asm to convert BCD to binary or to help someone with poor soldering skills. I used to but now starting to find it tedious. Would rather talk about if it's possible to bitbang SPI or I2C with a Z80.
--
You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+...@googlegroups.com.
To post to this group, send an email to rc201...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/CAK9X0%2BtcD6aPBLtC3DgN3rrAR8P8RfqUi_8J%3DfB4kMnBOUkLNg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
SpencerThanks for clarifying the official position on the future of RC2014.A while back you provided, on this forum, some provisional guidance on the use of additional bus pins:I've been musing over enhancements to the backplane for a little while now, and whilst nothing is set in stone, the pin layout would follow this;Enhanced StandardA31 1 1 A15A30 2 2 A14A29 3 3 A13A28 4 4 A12A27 5 5 A11A26 6 6 A10A25 7 7 A9A24 8 8 A8A23 9 9 A7A22 10 10 A6A21 11 11 A5A20 12 12 A4A19 13 13 A3A18 14 14 A2A17 15 15 A1A16 16 16 A0Gnd 17 17 Gnd5v 18 18 5vRFSH 19 19 M1Page 20 20 ResetClock2 21 21 ClockBUSACK 22 22 INTHALT 23 23 MREQBUSRQ 24 24 WRWAIT 25 25 RDNMI 26 26 IOI think some of us have been basing our "designed for RC2014" on this guidance. Are you saying this guidance is not correct?You say "However, it should be clear that anything which will not plug in to and run on a RC2014 is not compatible with the RC2014.". Does that mean anything that does not work on a backplane Pro can no longer be described as RC2014 compatible?Steve
The enclosed picture is how I visualize the various BUS standards.
We can then start discussing the layout of the RC80 and RC40 bus, and leave the RC2014 bus alone.
Karl
I think the X0 to X7 as user defined pins is reasonable, its unlikely to need 32 bit address bus.
A16 to A23 raises a few questions. I think z180 would only use A16 to A19, and Z280 would support A16 to A23. Should extended memory modules be configured to decode the full address A16 to A23 to support later use with 24 bit addressing?
If extended address decoding is included for memory, the address lines should not be floating, does this mean the processor boards should include drive for the full 24 bit address? Or should some provision be included in the memory module?
Experimenting with 16 bit data bus may need separate upper and lower byte control, but would fit into the X0 to X7 user defined pins.
Mark
Perhaps one should restrict ourselves to some kind of Z80 bus system, so that means:
* IEO/IEI problem
--
You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+...@googlegroups.com.
To post to this group, send email to rc201...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/CAO93PteD%3D0OSA2acYCWYjvtrNPVH1_LTvM7urSSdkjrOhf3QPw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
I really like this forum. It is friendly, entertaining, educational, active, and got some great members. Whenever I fancy a break I can drop in here and there is usually something being discussed.However, I would like to broaden my activities into areas not really appropriate to "RC2014-Z80". Can anyone suggest a good place to hang out?
In google groups it is possible to create message categories to group messages according to these categories. Groups also support message tagging but not both at the same time. To test this concept I created a new group which you can check out here: SBC-Z80 t with the following categories (see image). It is also possible to organize the categories into hierarchical groups to keep thing organized. My suggestion for this group would be to add something like the following (see image). Before a message can be posted a group must be selected. The groups are just off the top of my head, suggestions are welcome
I do not appreciate some contributors with strongly negative views and knocking others at a personal level, and hope that they will just quietly take a hint and drop out of this group. It is after all a group founded by Spencer to support RC2014.
Thank you to all the supporters, I won't be naming them as I would be forgetting someone important, but thanks to all designers enhancing rc2014.
Just wish we had some case designers on Tindie :)
Richard
The RC2014 was never designed to run super fast CPUs with a huge range of exotic peripherals and loads of memory. It was designed to be simple. Simple to build, simple to understand, and simple to program. . .
Mark
To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/8AB769D6-6C3A-4283-885F-ED4102ABB4C7%40filteracy.com.
@Mike
I am really not interested in having a fight. I have nothing further to add.
To post to this group, send email to rc201...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/CANDE_bmM6K17H-HEztYr5H3s5-mguwD2-nLZwD2gAHUWpxThgA%40mail.gmail.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/A3433B5E-46AA-4D74-862F-1F9E25D82BF4%40filteracy.com.
Hi Mark,Sorry, still learning the admin features . It is now set for "anyone" to be able to join. Please feel free to check it out: https://groups.google.com/forum/#!forum/sbc-z80In order to post will need to request permission-Richard
https://groups.google.com/forum/m/#!forum/retro-comp
Michael
There is more than one way to skin a cat. That is why I have a dozen or so z80 systems. Th Rc2014 wasn't one of my favourites but I liked the idea of plug in boards and so do a lot of people it seems.I am now at my happiest with a Teensy running emulated CPM. The DOS formatted SD card makes life a breeze but more importantly it allows me to write Z80 assembler all day long.Derry.PS I will get that text editor finished one day ....PPS I don't read a Teensy forum for my Z80 fix I read this one.