[Coco] System gen problem

[Boisy G. Pitre]

On Feb 9, 2010, at 8:33 AM, Steven Hirsch wrote:

> On Tue, 9 Feb 2010, Boisy G. Pitre wrote:
> 
>> Steve,
>> 
>> Are you building these modules from the latest project sources?  If so, then there is an issue with using the latest dw3.sb with a non-Java server.  Aaron's work has caused an understandable incompatibility with the older servers that would cause the symptoms you are seeing.
> 
> Boisy,
> 
> I'm not building the modules at all.  I'm using the ones in the RBF directory of the Cloud9 6809l2 boot image.  I actually was not able to find the sources for the dw drivers - where are they?
> 
> Can you elaborate on what 'dw3.sb' actually is?  I'm not used to seeing that extra layer of device driver.  If I'm inferring correctly, you need:
> 
> rbdw3.dr
> dw3.sb
> ddx0.dd
> etc, etc

dw3.sb is a subroutine module that has code which  talks to the bitbanger.  It is segregated into its own module for possible future expansion (i.e. talking to a 6551 for instance).  rbdw3 and  clock2_dw3 link to the dw3 module and make calls into it.

> is that correct?
> 
> This morning I had partial success using the build script on the Cloud9 image.  If I have dw support as:
> 
> rbdw3.dr
> dw3.sb
> ddx0.dd
> x1.dd
> x2.dd
> x3.dd
> 
> followed by my hard disk drivers:
> 
> hdisk.dr
> h0.dd
> h1.dd
> 
> I get a working system that boots from a floppy diskette and logs to dw drive 0 as the home disk (/dd).  I do have working access to the hard drive, so this is a big step in right direction.

Good.

> HOWEVER, if I replace ddx0.dd with x0.dd and h0.dd with ddh0.dd in an attempt at making my first hard drive volume the home disk, I get no drivewire connectivity.  It logs to the hard disk, but attempts at accessing /x0 get me an ERROR #235 (and, yes, the diskette image IS mounted in the server).  The server shows no indication that any communication is taking place.

Error 235 is E$BNam and grepping the NitrOS-9 sources shows that error being returned from the kernel's F$FModul routine.  It's as though the dw3.sb module cannot be found.

Hmmm, I suspect I know what is going on.  You need to put clock2_dw3 in your bootfile and let me know if this clears up things.

> Am I doing something obviously wrong?
> 
> Steve
> 
> 
> -- 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco

--
Boisy G. Pitre
http://www.tee-boy.com/