RE: [N8VEM: 5534] CUBIX on the 6809 Host Processor board

No it still uses most of the groundwork you had in the original. I did some tests with other methods and they did not work as well, so I just coded around any shortcomings in the interface hardware. Hopefully I will get to a point where I can post some code tonight. I have the server side disk drivers coded now, I just need to code the CUBIX side and then some serious testing can begin. I plan on supporting Floppy, IDE, and ATAPI devices to start with. I am also going to need a program that will read/write CUBIX disk images, from windows or CP/M so that we can get the CUBIX utility programs and languages on to a disk.

Basically there is the “server” program that runs under CP/M and a modified version of your minibug program in ROM (it uses the new communication protocol, and has a Hex Dump feature). I have a script that builds CUBIX to a .S19 file and use the “L” function to load it into RAM, and then use the “G” function to start CUBIX.

Dan Werner

From: Andrew Lynch [mailto:lyn...@yahoo.com]
Sent: Monday, November 23, 2009 4:36 AM
To: n8...@googlegroups.com
Subject: RE: [N8VEM: 5534] CUBIX on the 6809 Host Processor board

Hi Dan! Thanks! That sounds great! Is your interface using one channel for status/commands and the other for data? That seemed to be the way to go rather than use the PPI and PIA strobes. I think it would be more reliable when polling the status on both sides. Using channel A for input and channel B for output didn’t really work very well for me especially since the PPI doesn’t really have a good way of telling if it has received an input strobe.

Thanks and have a nice day!

Andrew Lynch

From: Dan Werner [mailto:dwe...@dpcpipe.com]
Sent: Sunday, November 22, 2009 4:09 PM
To: n8...@googlegroups.com
Subject: RE: [N8VEM: 5528] CUBIX on the 6809 Host Processor board

The interface is not interrupt driven, I created a master/slave protocol that allows a sort of “command” driven communication. The console was just one part of it, it will also allow disk access, lpt port access or whatever. I am about 2/3 of the way through getting disk access done. The way CUBIX is set up, once the IO board is done we can just add drivers for that as well, and then by just changing a table the user could configure the OS to use either console.

Dan

From: Andrew Lynch [mailto:lyn...@yahoo.com]
Sent: Sunday, November 22, 2009 8:28 AM
To: n8...@googlegroups.com
Cc: 'Dave Dunfield'
Subject: RE: [N8VEM: 5519] CUBIX on the 6809 Host Processor board

Wow! Dan that is incredibly great! Thanks! Excellent work!

How are you using the 6809 host processor interface? My original version needed some major rework. The console interface was never very stable because I was trying to use the separate in and out channels. I never got it to work very well.

I can’t wait to get the IO mezzanine board out for the 6809 host processor so it can operate by itself or connected to the N8VEM system!

In theory at least, the 6809 host processor should be able to generate /INT signals for the N8VEM SBC. The connections are there for the 8255 to generate interrupts although I haven’t tested them. It may be possible CP/M could run on the N8VEM SBC and provide IO support to the 6809 host processor as an interrupt service routine.

I’ll courtesy copy Dave as I am sure he’ll be glad to see his CUBIX OS booting on a new system!

Thanks and have a nice day!

Andrew Lynch

From: Dan Werner [mailto:dwe...@dpcpipe.com]
Sent: Saturday, November 21, 2009 7:05 PM
To: n8...@googlegroups.com
Subject: [N8VEM: 5509] CUBIX on the 6809 Host Processor board

Lots of work to do yet, CUBIX is running on the 6809 host processor board (see pic). I still have a bug in the console input code, and there is no disk IO code yet, but it is booting and all of the communications framework is there. I am hoping that a couple of good days coding and I should have it fairly stable.

Dan

You received this message because you are subscribed to the Google Groups "N8VEM" group.
To post to this group, send email to n8...@googlegroups.com.
To unsubscribe from this group, send email to n8vem+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/n8vem?hl=.