Re: SS4000E Cable Wiring
H Danny,
Will let you know if I make any progress. Feel like such a noob, which I
am when it comes to this embedded stuff.
Just a quick question. Do I need to have the linux arm kernel installed
via tftp before the serial console shows any output? I should think not
and that the redboot? loader would output text to the console by default?
Is this correct?
thanks
> I wrote to this list a few weeks back with similar problems Mark. I
> couldn't get any communication via the serial ports.
>
> Two null modem cables and two idc10s to db9 brackets. Tried
> resoldering the correct pinouts on the bracket too, nada. No garbage
> no nothing.
>
> Let us know if you make any headway with the cable.
>
> I'd also be interested in knowing if anyone has managed to get real
> perfomance out of the unit, or at least found the bottlenecks that cap
> it at around 5-6 MB/s
>
> Might be fun to trunk eth0 and eth1 too :-)
>
> Sent from my iPhone
>
> On Dec 27, 2009, at 2:19 AM, mark@jumpingbean.co.za wrote:
>
>> Hi,
>>
>> The java app is just to see if it possible to test the cable
>> somehow. I
>> can connect to the serial port on the pc and I know that that is
>> working.
>> Just writing the data receive event handlers now to see if I can get
>> anything.
>>
>> I will try screen with the serial device too. Its all a learning
>> curve for
>> me so nothing is wasted :)
>>
>> Thanks
>>
>>
>>
>>> On 12/26/2009 06:26 AM, mark@jumpingbean.co.za wrote:
>>>> I think I may have to write a little java app to see whats wrong
>>>> with
>>>> the
>>>> cable. I can find any message on /var/log/message or /var/log/
>>>> syslog so
>>>> its a bit difficult to see if its just a poor soldering job or I am
>>>> doing
>>>> something else wrong. May be the long way round but it holidays so
>>>> got
>>>> time to mess around with this stuff. Any pointers appreciated,
>>>
>>> what are you planning to use the java app for? assuming you're
>>> connecting to this serial port from (for example) a host's first USB
>>> serial port, you should be able to try it out with plain ol' GNU
>>> screen:
>>>
>>> screen /dev/ttyUSB0 115200
>>>
>>> (if your device defaults to a different baud rate, substitute it for
>>> 115200).
>>>
>>> you'd get out of it like killing any other screen session: C-a C-k
>>>
>>> hth,
>>>
>>> --dkg
>>>
>>>
>>
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-arm-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact
>> listmaster@lists.debian.org
>>
>
Reply to: