Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
I don't know anything about gdb, but judging by your input and your error message, does gdb ignore the first / in /dev/ttyUSB? Is / the character that indicates you're feeding an argument, like - with ls -l? Do you need to say something like (gdb) target /rdi //dev/ttyUSB Another idea: do you need to use gdb at all? Can you just read raw output from /dev/ttyUSB? It should be a file device, like anything else that hides out in /dev Maybe you can just do cat /dev/ttyUSB and redirect the output to a log you can pick through later. I don't know anything about your device. Is it expecting input on the serial device, or does it just dump debugging info to serial? Has somebody created a proprietary communications method, which requires their binary? Did they wire the pins in a nonstandard way, and you have to get their connector or wire your own interface? This would be a good time to dig through the docs for the device. If this device is compatible with minicom, you still need to know which modem settings to try. -- David Backeberg (dave at math.mit.edu) Network Staff Assistant MIT Math Dept. Rm. 2-332 (617) 253-4995 On Sat, 29 Jan 2005, David Kramer wrote: > I'm using a Prolific PL2303HX-based Sewell USB to serial cable to go from > my laptop to an ARM7 embedded development board. The adapter talks ok to a > modem and other devices, so I know I have the device and the permissions > right. > > When I try to talk to the board through the cross-platform version of the > gdb debugger, arm-elf-gdb, I get: > > (gdb) target /rdi /dev/ttyUSB0 > (gdb) > Could not open device "dev/ttyUSB0" > > I've tried it both as root and as a mortal. > > What tools do people use to work with serial port problems? I fooled > around with setserial, but it seemed rather displeased at the device, > saying "Cannot get serial info: Invalid argument". I tried fooling around > with Minicom, but it REALLY REALLY wants to talk to a modem, and doesn't > want to let me talk to the serial port until I've dialed a number. > > Any clues? > > > Thanks. > > > _______________________________________________ > Discuss mailing list > Discuss at blu.org > http://olduvai.blu.org/mailman/listinfo/discuss >
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |