Problems with USB to serial adaptor

[jonathan at jonmasters.org (Jon Masters)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[ apologies for lack of reply threading, I just signed up and don't have
a handy message to reply to. btw, hi. I'm going to be coming to Boston
LinuxWorld in a couple of weeks and figured I might aswell delurk now.
I'm in the UK now but will be doing a road trip down from Ottawa. ]

David Backeberg writes:

| I don't know anything about gdb

The original poster probably wanted the "remote" target anyway.

| do you need to use gdb at all?

He wants to talk to a gdb stub on the embedded target, most likely.
Stubs are gdb clients that let you debug stuff from a host box -
especially useful if you don't have ethernet on the board since with
ethernet he could just use a stub running on a TCP/IP port.

| Did they wire the pins in a nonstandard way

He may not have working hardware handshaking on a USB adapter so might
want to switch to standard 8N1 non-hardware handshaking at 9600bps.

| If this device is compatible with minicom, you still need to know
| which modem settings to try.

Take out the dial strings from the Minicom Options, or use another
client such as kermit or something similar. Personally, I still use
minicom despite the recommendations of various others, because I'm
stubborn and really need to be convinced that I am wrong :-)

Minicom does support other options btw, for example I recently learned
it can talk to UNIX domain sockets using a unix# "device" prefix. Great
for debugging a kernel running within a recent VMware since VMware no
longer supports talking to regular ttys how you might want it to.

Cheers,

Jon.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB/YA3eTyyexZHHxERAj3xAJ9KtrrNWLPT3H2iRcN2mAB61JDQowCgjfbd
YnlG+RpYLhsSNkvN569T528=
=NieC
-----END PGP SIGNATURE-----