[Coco] [!! SPAM] Re: DE1 - More data

[John Kent]

I've been using the DE1 board with Drivewire 3 Winserver rather than 
Drivewire 4.
I have not reflashed the ROMs in quite a while.
I type "DOS" then "DIR" and it lists the files on the disk.
I have DOS1.DSK in drive 0
slider switch 0 - 3 are in the up position
slider switch 4 - 9 are in the down position
I'm not sure which version of the code I'm using, but I think it's the 
second last version uploaded by Gary.
Could be the latest CC3_DE1_2011-05-01... not sure.
(That is the naming convention I'm using anyway.)

John.

On 30/05/2011 10:57 AM, Aaron Wolfe wrote:
> one other thing that occurred to me.. originally you just needed to
> write the coco rom to the beginning of flash on the board, but at some
> point that changed and you need to write the coco rom, then
> immediately after that the DECB rom.  maybe you want to check that
> you've done that?  just an idea.
>
> On Sun, May 29, 2011 at 8:53 PM, Aaron Wolfe<aawolfe at gmail.com>  wrote:
>> On Sun, May 29, 2011 at 8:19 PM, Steven Hirsch<snhirsch at gmail.com>  wrote:
>>> On Sun, 29 May 2011, Aaron Wolfe wrote:
>>>
>>>> I recommend turning on "log protocol device bytes" in the advanced
>>>> page of the instance config in DW.
>>>> this will let you see every byte sent or received on the serial port,
>>>> even if they don't add up to a valid operation.
>>>> you also will want to turn the logging level to DEBUG or ALL.
>>> I did have it on DEBUG.  There is simply nothing coming over the wire.
>>>
>>>> The search for disks in drives 0-2 at power on is normal.
>>> Yes, and I think that's actually done by an autonomous bit of code in Gary's
>>> design rather than the emulated machine.
>>>
>> Right, that comes from the floppy processor, not the coco itself.
>>
>>>> It sounds
>>>> like you may have some switches set wrong on the board if it is
>>>> returning immediately with an error.  Double check those, find out if
>>>> there are other bytes coming over the wire,
>>> No, nothing over the wire so this does seem like an improper setting -
>>> somewhere.  Thing is, I haven't touched the bloody thing since the beginning
>>> of the year and it was working at that point.  Oh, well.  Keeps life
>>> interesting.
>>>
>> The meanings of the switches have changed over time, some quite a bit.
>>   It may be that the settings that used to work are no longer valid.
>> Unfortunately my FPGA board is still on it's way back from chicago,
>> UPS taking it's time to deliver the gear I took.
>>
>> BTW are you using the latest build from the yahoo group?
>> Documentation vs software version may be critical here, as things have
>> changed over time.  If you use the latest build, maybe Frank can post
>> his working switch settings and you'll have a known good config to
>> start with.
>>
>>
>>>> and maybe consider posting
>>>> in the CoCo3FPGA board, Gary monitors that but I don't know if he
>>>> reads this group.
>>> Thanks, will do that.
>>>
>>> Steve
>>>
>>>
>>> --
>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>

-- 
http://www.johnkent.com.au
http://members.optusnet.com.au/jekent