Re: SS4000E Cable Wiring
Phew - Got it working. It seems most guides about the wiring are incorrect. This page is wrong http://www.tomjudge.com/index.php/SS4000-E/Serial_Cable This page has the correct wiring - http://projects.kwaak.net/twiki/bin/view/EM7210/SerialConsoleCable At least the bottom part. I soldered 3=3, 5=2 and 9=5. The LHS side is the pins from the DL10 side and the RHS. Now I am getting the redboot output on the console. I hope this helps someone else. This setup seems to use non-standard wiring for the null modem cable. Is most embedded systems like this? Kind of a guessing game? Thought serial cables were standard. regards > What I don't understand is why one would work and not the other if > we're (re)soldering the wires ourselves? > > Sent from my iPhone > > On Dec 27, 2009, at 5:06 PM, "JF Straeten" > wrote: > >> >> Hi Mark, >> >> On Sun, Dec 27, 2009 at 05:51:32PM +0200, m...@jumpingbean.co.za >> wrote: >> >>> 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? >> >> Yes, it's correct. >> >> It's not easy to find a suitable cable. I have tried with three of >> them before finding the right one. They were supposedly "standard" >> serial PC bracket cables, but whith the first two, I had only some >> garbage on the screen. >> >> Good luck, >> >> >> -- >> >> J.-F. Straeten >> >> --- >> Mutt 1.5.18 - Debian GNU/Linux > > > -- > To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > > -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: SS4000E Cable Wiring
What I don't understand is why one would work and not the other if we're (re)soldering the wires ourselves? Sent from my iPhone On Dec 27, 2009, at 5:06 PM, "JF Straeten" wrote: Hi Mark, On Sun, Dec 27, 2009 at 05:51:32PM +0200, m...@jumpingbean.co.za wrote: 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? Yes, it's correct. It's not easy to find a suitable cable. I have tried with three of them before finding the right one. They were supposedly "standard" serial PC bracket cables, but whith the first two, I had only some garbage on the screen. Good luck, -- J.-F. Straeten --- Mutt 1.5.18 - Debian GNU/Linux -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: SS4000E Cable Wiring
Hi Mark, On Sun, Dec 27, 2009 at 05:51:32PM +0200, m...@jumpingbean.co.za wrote: > 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? Yes, it's correct. It's not easy to find a suitable cable. I have tried with three of them before finding the right one. They were supposedly "standard" serial PC bracket cables, but whith the first two, I had only some garbage on the screen. Good luck, -- J.-F. Straeten --- Mutt 1.5.18 - Debian GNU/Linux signature.asc Description: Digital signature
Re: SS4000E Cable Wiring
Redboot gives a 1 second prompt through ttys0 before booting the image. From everything that I have read, getting an active serial connection is pretty much step 1. Sent from my iPhone On Dec 27, 2009, at 10:51 AM, m...@jumpingbean.co.za wrote: 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, m...@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, m...@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-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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, m...@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, m...@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-requ...@lists.debian.org >> with a subject of "unsubscribe". Trouble? Contact >> listmas...@lists.debian.org >> > -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: SS4000E Cable Wiring
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, m...@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, m...@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-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: SS4000E Cable Wiring
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, m...@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-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: SS4000E Cable Wiring
On 12/26/2009 06:26 AM, m...@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 signature.asc Description: OpenPGP digital signature
Re: SS4000E Cable Wiring
Hi John, I first tried the three wires as per tom judge page, then all of them as per the Russian page. Still no luck. Currently I am reading up on serial communication on http://en.wikibooks.org/wiki/Serial_Programming 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, regards Mark > m...@jumpingbean.co.za wrote: >> j...@sinodun.org.uk wrote: >>> mxc wrote: Hi all, I am using this tutorial http://www.tomjudge.com/index.php/SS4000-E/Serial_Cable for the pin mappings for my serial cable. This differs from the following http://pinouts.ru/SerialPorts/Serial9_pinout.shtml Anyone know which one is correct? >>> >>> I've looked at the two pages you reference and they seem to agree >>> exactly. What discrepancy are you seeing? >> >> I am new to this so maybe I don't understand the terminology. I assumed >> the NC on the tom judge page meant "no connection", i.e no wires to be >> soldered. On the pinouts page from the Russian domain the remaining pins >> are connected and not necessarily straight through. >> >> The pins that are shown do agree. What about the rest? Can I just ignore >> them. I am getting no characters coming through at all with the cable at >> the moment. No even garbage. > > > Sorry - I'm so used to these things that I just mentally edited out the > extra ones. Yes, NC does indeed mean "no connection". > > All you need for the most basic serial connection are the three wires > which are common to both - two for data and one for ground. Whether you > then need the others depends on what type of flow control you are using. > > You say your existing cable doesn't work. Have you wired up just the > three connections or all of them? > > Cheers, > John > > > -- > To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > > -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: SS4000E Cable Wiring
m...@jumpingbean.co.za wrote: > j...@sinodun.org.uk wrote: >> mxc wrote: >>> Hi all, >>> >>> I am using this tutorial >>> http://www.tomjudge.com/index.php/SS4000-E/Serial_Cable for the pin >>> mappings >>> for my serial cable. This differs from the following >>> http://pinouts.ru/SerialPorts/Serial9_pinout.shtml >>> >>> Anyone know which one is correct? >> >> I've looked at the two pages you reference and they seem to agree >> exactly. What discrepancy are you seeing? > > I am new to this so maybe I don't understand the terminology. I assumed > the NC on the tom judge page meant "no connection", i.e no wires to be > soldered. On the pinouts page from the Russian domain the remaining pins > are connected and not necessarily straight through. > > The pins that are shown do agree. What about the rest? Can I just ignore > them. I am getting no characters coming through at all with the cable at > the moment. No even garbage. Sorry - I'm so used to these things that I just mentally edited out the extra ones. Yes, NC does indeed mean "no connection". All you need for the most basic serial connection are the three wires which are common to both - two for data and one for ground. Whether you then need the others depends on what type of flow control you are using. You say your existing cable doesn't work. Have you wired up just the three connections or all of them? Cheers, John -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: SS4000E Cable Wiring
Hi John, I am new to this so maybe I don't understand the terminology. I assumed the NC on the tom judge page meant "no connection", i.e no wires to be soldered. On the pinouts page from the Russian domain the remaining pins are connected and not necessarily straight through. The pins that are shown do agree. What about the rest? Can I just ignore them. I am getting no characters coming through at all with the cable at the moment. No even garbage. thanks > mxc wrote: >> Hi all, >> >> I am using this tutorial >> http://www.tomjudge.com/index.php/SS4000-E/Serial_Cable for the pin >> mappings >> for my serial cable. This differs from the following >> http://pinouts.ru/SerialPorts/Serial9_pinout.shtml >> >> Anyone know which one is correct? > > I've looked at the two pages you reference and they seem to agree > exactly. What discrepancy are you seeing? > > John > > > -- > To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > > -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: SS4000E Cable Wiring
Hi Willem, Thanks for the info. Yup, I know maybe trying too many things at once, seems its the only way though as I can't find any shop over here with the correct null modem cable. Hopefully I at least get part way there. Once again thanks for the feedback. regards Mark > Hi Mark, > > specifically null-modem cable: > http://en.wikipedia.org/wiki/Null_modem > > R, > Willem > > > > > > > > > > > > > > > > > > > > . > -- > Preisknaller: GMX DSL Flatrate für nur 16,99 Euro/mtl.! > http://portal.gmx.net/de/go/dsl01 > -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: SS4000E Cable Wiring
mxc wrote: > Hi all, > > I am using this tutorial > http://www.tomjudge.com/index.php/SS4000-E/Serial_Cable for the pin mappings > for my serial cable. This differs from the following > http://pinouts.ru/SerialPorts/Serial9_pinout.shtml > > Anyone know which one is correct? I've looked at the two pages you reference and they seem to agree exactly. What discrepancy are you seeing? John -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: SS4000E Cable Wiring
Hi Mark, specifically null-modem cable: http://en.wikipedia.org/wiki/Null_modem R, Willem . -- Preisknaller: GMX DSL Flatrate für nur 16,99 Euro/mtl.! http://portal.gmx.net/de/go/dsl01 -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: SS4000E Cable Wiring
Hi > http://www.tomjudge.com/index.php/SS4000-E/Serial_Cable this one is only partially connected, may not work on some hardware > http://pinouts.ru/SerialPorts/Serial9_pinout.shtml this one is fully connected it seems See also on DB9 connector http://en.wikipedia.org/wiki/RS-232 It seems to me you are trying to achieve progress on hardware, cable and software domains at the same time. Although this may work, it will be difficult to troubleshoot. Good luck anyway, Willem -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
