[Coco] Dragon & Drivewire

[Ken H.]

Just submitted 2 bug reports. The first with ProtocolXORInputBits=true and
the second with ProtocolXORInputBits=false
Ken


On Tue, Oct 30, 2012 at 12:28 AM, Aaron Wolfe <aawolfe at gmail.com> wrote:

> After looking at the log a bit closer... we are getting an awful lot
> of reset codes, which would be F8, FE or FF.  Looks like several per
> second.
> These are mixed in with the "unknown opcode" messages.  Any ideas why
> the serial port would be seeing those?  I guess its actually getting a
> whole bunch of 0, 1 or 8s assuming the XOR is happening?
>
>
>
> On Mon, Oct 29, 2012 at 6:19 PM, Aaron Wolfe <aawolfe at gmail.com> wrote:
> > Well you are getting something, which is good.  Unfortunately the
> > values aren't mapping to valid op codes.  They look mostly consistent,
> > so that's good too.  I'd say either the XOR feature is "doing it
> > wrong", not enabled, or we have a baud rate mismatch.
> >
> > Could you send a bug report using the option in the help menu (after
> > causing some failures)?  That will send me much more useful
> > information.
> > -Aaron
> >
> >
> > On Mon, Oct 29, 2012 at 6:00 PM, Ken H. <dragon.atv at gmail.com> wrote:
> >> After several attempts I still haven't succeeded to setup the Dragon
> with
> >> Drivewire 4.3.0
> >>
> >> I am using an adapter based on Darren A's diagram here:
> >> http://tandycoco.com/forum/viewtopic.php?f=71&t=104
> >> AFAIK my cable matches exactly Darren's Diagram. I have enabled
> >> ProtocolXORInputBits and restarted Drivewire.
> >>
> >> On the Dragon side, I am running HDB-DOS 1.4 DW3 CoCo2 (running on the
> >> Dragon in CoCo mode)
> >> The Drivewire log shows
> >>  29 Oct 2012 23:38:58 WARN  [dwproto-0-13  ] UNKNOWN OPCODE: 116 t
> >> 29 Oct 2012 23:38:58 WARN  [dwproto-0-13  ] UNKNOWN OPCODE: 2
> >> 29 Oct 2012 23:38:58 ERROR [dwproto-0-13  ] Port 4 is not open
> >> 29 Oct 2012 23:39:01 WARN  [dwproto-0-13  ] UNKNOWN OPCODE: 116 t
> >> 29 Oct 2012 23:39:01 WARN  [dwproto-0-13  ] UNKNOWN OPCODE: 6
> >> ....
> >>
> >> I attached the complete log (5KB zipped)
> >>
> >> Any suggestions?
> >> Perhaps we're XORing the wrong bits?
> >>
> >> Ken
> >>
> >>
> >>
> >> On Mon, Oct 22, 2012 at 2:50 AM, Aaron Wolfe <aawolfe at gmail.com> wrote:
> >>
> >>> The new 4.3.0 version has an option for this, untested...  (if this
> >>> works, I'll add Dragon to the setup wizard with it preset, etc).
> >>>
> >>> For now, to enable:
> >>>
> >>> In the Config menu, choose "Configuration Editor".
> >>>
> >>> Along the top of the editor, toggle "Device" and "Show Advanced Items".
> >>>
> >>> Look for "ProtocolXORInputBits".  Toggle to true.
> >>>
> >>> Click "Write to Server" so the config is sent to the server.
> >>>
> >>> You'll have to then either Choose "Restart Instance Device" from the
> >>> config menu or just restart DriveWire before it takes effect.  I'll
> >>> make that smoother once we have it working correctly.
> >>>
> >>> -Aaron
> >>>
> >>
> >>
> >> --
> >> 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
>