Reading ALDL 8192 stream from '165

[Craig Moates]

Nice idea on the 160 stream, Ludis! I was starting to wonder if something
like that might work...

Many thanks for helpful input (terryk, Ludis, s.ravet, b.tisdale, a.mattei,
dan burk, et.al...) ! I was able to get my 165 to send the 8192 stream.
Reads nicely as a 63-byte packet as hoped. The command for Mode 1 8192
communications was $80,$56,$01,$29(CS). Sending that in 8192, looking for
8192 data in return during the initial 160bd mode. Sent it a couple of times
till it caught the time-slot needed and then it responds each time, with an
echo, followed by $80,$95,$01,byte1-63,(CS).

Very nice, exactly what I was looking for. Much appreciation goes out. Now
about that Mode 4 Protocol (LOL!)... I need to spend some quality time with
the PROM disassembly of my system's close cousin... Then maybe a Mode 2
dump...

Aahhh... Feels good! Thanks so much! If I can get this little Diacom-like
program polished up in Qbasic, I'd be glad to pass it on for what it's
worth...

-Craig

-----Original Message-----
From: steve ravet <sravet at arm.com>
To: gmecm at efi332.eng.ohio-state.edu <gmecm at efi332.eng.ohio-state.edu>
Date: Monday, October 18, 1999 10:02 AM
Subject: Re: Reading ALDL 8192 stream from '165


>
>
>Craig Moates wrote:
>>
>> Making progress am I?
>
>Well.....  The 160 baud format is not an RS-232 format signal, even if
>you level shift it.  The timing is not anything like RS-232.  For one,
>there are at least 2 edges for every bit.  If you search around in the
>DIY_EFI (not gmecm) archives for 160 baud aldl you'll find a description
>of the signal.  I posted it so try throwing my name into the search.
>
>Better to focus on getting the 8192 stream out, maybe Ludis can tell you
>what that takes.
>
>--steve
>
>
>--
>Steve Ravet
>steve.ravet at arm.com
>Advanced Risc Machines, Inc.
>www.arm.com