We've got the opt2ttlcom option ourselves too. It's implemented in
the board's CPLD (i.e., glue logic), so it is a *hardware*
implementation. Linux drivers just access the reconfigured CPLD in
order to interface the new UART ports. They do work as independent
UART ports and you can find them as /dev/ttyTS1 and /dev/ttyTS2. I
understand that with the proper cabling and CPLD source code you
should be able upload the new CPLD definition to your board yourself,
but source code of the opt2ttlcom option is proprietary to
Technologic Systems AFAIK, so you're out of luck. I'd recommend you
try and contact them again to ask them about this procedure (I bet
you'll have to resend the board to them for CPLD reprogramming).
Guille
--- In "Kulendra Janaka" <>
wrote:
>
> Hi
> I thought of writing to you since we are having a very ground level
problem
> with the opt2ttlcom. I thought I'd ask you cos u've said that you
have
> ordered that option with your board.
>
> OK now the problem is that we didnt order the opt2ttlcom option :S
(ok dont
> laugh :) ) I have mailed them asking whether its possible to get
the option
> later but I have not yet got any answer.
>
> This is the help that I need from you. Can you please tell me what
exactly
> do you get with the opt2ttlcom option? I mean does the kernel
really change
> to accomodate teh COM4 and 5 on the DIO2 or is it some utility
patch that
> allows the DIO2 to be used as the UARTs? I'm quite new to this
area, and I
> know that you have to have some sort of serial stack in DIO2 to use
it as a
> serial port. I hope you can see the problem now, and if you can
please send
> me a reply on this
>
> Thanks a lot in Advance
> Kulendra
>
> On 8/2/06, Kym Newbery <> wrote:
> >
> > HI There,
> >
> > Thanks for the rapid and helpfull suggestions!
> >
> > I have solved my problem after verifying with a loopback that the
CPU
> > was fine, rather, it was my peripheral (a microchip PIC cpu with
> > software uart) that had a slight, 3%, baud rate error. So I have
fixed
> > the PIC and it seems fine now. It seems as if the TSUarts are not
> > that tolerant of timing errors (neither are some other brands of
uarts
> > anyway)
> >
> > Regards
> > Kym
> >
> >
> > --- In <ts-7000%40yahoogroups.com>, "Eddie
> > Dawydiuk" <eddie@> wrote:
> > >
> > > Hello,
> > >
> > > > I am having problems with the tsuart serial ports on a TS-
7260 with
> > > > the opt2ttlcom option, with kernel 2.4.26-ts9 (supplied with
the
> > > > board) and the default mtd filesystem.
> > > >
> > > > I have cross-compiled microcom (a small terminal emulator) to
access
> > > > /dev/ttyTS1 at 9600,N,8,1 however, when I access the port I
get a
> > > > console message :
> > > >
> > > > tsuart:change_speed port 1: 9600 bad
> > >
> > > This is normal this is the driver telling you the baud rate has
been
> > > changed to 9600.
> > >
> > > > and nothing is transmitted/received...
> > >
> > > How are you testing if anything is being transmitted?
> > >
> > > > So I compiled the ts-11 kernel and included the tsuart
modules into
> > > > the kernel (not as modules), and tried again. This time with
the ts11
> > > > kernel, there is no console message, but at 9600,N,8,1 approx
1 in 3
> > > > receive characters are corrupted. If I send single chars to
> > > > /dev/ttyTS1 then they are usually received ok, but if I send
a string,
> > > > eg "0123456789" then most characters are randomly corrupted.
> > >
> > > I tried to reproduce this here and everything was transmitted
properly.
> > > How are you testing this? I'd recommend connecting a null modem
cable
> > > to COM3 then starting a terminal emulator on the PC the null
modem
> > > cable is connected to set the terminal emulator to use
9600,8,n,1.
> > > Finally from the command line run the following command.
> > >
> > > echo 1234567890987654321 > /dev/ttyTS0
> > >
> > > You should see the string 1234567890987654321 appear immediatly
in your
> > > terminal emulator.
> > >
> > > //Eddie
> > >
> >
> >
> >
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|