Re: minicom questions, need expert

On Monday 12 May 2008, Rick Stevens wrote:
Gene Heskett wrote:
On Monday 12 May 2008, Gene Heskett wrote:
Greetings;

I'm trying to make an antique computer talk to this linux box via a
usb<->serial adaptor and a long USB extension cord that has a hub kit in
the far end of it.

When I plug in the cable to a 7 port extension hub here, dmesg reports:

May 12 14:00:58 coyote kernel: [314986.418050] usb 1-1.3: new full speed
USB device using ehci_hcd and address 33 May 12 14:00:58 coyote kernel:
[314986.503819] usb 1-1.3: configuration #1 chosen from 1 choice May 12
14:00:58 coyote kernel: [314986.504986] hub 1-1.3:1.0: USB hub found May
12 14:00:58 coyote kernel: [314986.509657] hub 1-1.3:1.0: 4 ports
detected May 12 14:00:58 coyote kernel: [314986.818989] usb 1-1.3.4: new
full speed USB device using ehci_hcd and address 34 May 12 14:00:58
coyote kernel: [314986.910261] usb 1-1.3.4: configuration #1 chosen from
1 choice May 12 14:00:58 coyote kernel: [314986.910630] ftdi_sio
1-1.3.4:1.0: FTDI USB Serial Device converter detected May 12 14:00:58
coyote kernel:
[314986.910684] ftdi_sio: Detected FT232RL May 12 14:00:58 coyote kernel:
[314986.910721] usb 1-1.3.4: FTDI USB Serial Device converter now
attached to ttyUSB1

And I have sent several very long directory listings up the cable, but
nothing, not a single character is being output to the minicom screen.
I do not know if the minicom utility can reach out into that FT232RL to
tell it what the baud rate is or not, no clue. If minicom can't do that,
then what linux utility can perform this initialization?

Thanks all.

PEBKAC. It turned out that the serial port params on the legacy machine
were a bit foobared. And to minicom, it is now working well. A small
copy/paste: Directory of /dd/cmds 2008/05/12 14:42

Owner Last modified Attributes Sector Bytecount Name
----- ---------------- ---------- ------ --------- ----
0 2006/04/21 13:38 --e-rewr 1EBF8 1B00 asm
0 2006/04/21 13:38 --e-rewr 1EBFC 1FF attr


I can put the fixes for that in the startup file for the coco3/nitros9
machine.

Now, I would like to be able to put something in my own rc.local that
would first tune that /dev/ttyUSB1 port for the proper params, then go
away and allow a "cat /dev/ttyUSB1 >/lp3" to be done, the idea being to
use the linux box to convert that text into something for a modern printer
which doesn't understand P.O.A. (Plain Old Ascii). I need to be able to
make paper copies of program src, probably from the assembler.

Uh, "man setserial"

Apparently only for messydos style hardware serial ports, stty however seems
to work just fine with /dev/ttyUSB1.

But, this command line, which outputs to the screen very nicely if the pipe
and the rest of the line are removed, seems to send the data to /dev/null:

#>cat /dev/ttyUSB1 | lpr -Plp1

Humm, I just found a copy of the data I sent in /tmp under a hashnumber name.
Do I need to train my src machine to send some sort of an eof signal? On
that machine I'd need to set the hex value. Humm. Went down and set the
eof=$1b, (it was cleared to $00) so theoretically, when the pipe is closed
down there, it should send an $EOF char, but a repeat of that exercise only
doubled the size of the tmp file. But the end of the file only contains an
extra set of $0d0a's, no final char of $1b made it to the file.

Ok, maybe now we're back to some stty option? Here is its current output:
[root@coyote tmp]# stty -F /dev/ttyUSB1
speed 9600 baud; line = 0;
min = 1; time = 5;
ignbrk -brkint -icrnl -imaxbel
-opost -onlcr
-isig -icanon -iexten -echo -echoe -echok -echoctl -echoke

There are many more options according to the manpage, no idea what might or
might not work. However, I just set it to raw and did not get the EOF on
this end of the cable, so I'm doubting it is being sent. Check the other end
for creaks and squeeks of old age I guess, thanks for listening, unless you
can see what is stopping it from working in the above ramblings.

--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Even God lends a hand to honest boldness.
-- Menander

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Serial help - minicom?
    ... I've got an Access Point that has a serial port. ... The AP runs Linux ... I suspect it's minicom that's causing me problems. ... - Moving the cable from my linux box to Windows Hyperterm works right ...
    (Debian-User)
  • Samsung SPH N200 mobile phone
    ... Has anyone been successful in accessing this phone from Linux? ... this phone to serial port but could not get even an 'OK' response from ... minicom. ...
    (comp.os.linux.networking)
  • Re: Minicom configuring incoming EOL
    ... > I've got a device with a serial port which I am connecting directly to ... > my Linux box via serial and accessing via minicom. ... the rabbit. ...
    (comp.os.linux.misc)
  • Re: serial port characteristics
    ... >> port in Linux? ... > The stty utility should do what you describe. ... Or whatever program you are accessing the serial port with (like minicom) ...
    (comp.os.linux.networking)
  • Re: Linux "print server"
    ... porting Ghostscrip to a C64 is ... so a Linux server seemed possible. ... "> I already have TCP/IP communication using ppp between the C64 and the ... "> DTP app I use can send data to a serial port, ...
    (comp.os.linux.misc)