Hi all,

First up, I'm a novice when it comes to UART stuff so please be kind :)

I've been developing on a TS-7550. I've connected the rs232 to an external
controller. By running the following:

xuartctl --port=0 --speed=9600

I can manually type the letter 'a', for example, hit return and the controller
sends a nice big string back to the screen like :xyz123;

But what I really want to do is have a simple shell script that sends 'a' to
port 0 every x seconds, and when it gets the string back it assigns it to a
variable for use by other functions.

I've read all the manuals and scoured the net, but even why I try the suggested
test of something like:

echo "hello world" > /dev/pts/0

it doesn't actually do anything :(

Could anyone possibly point me in the right direction as it's the very last bit
of the puzzle to make my whole fun project work!

Thanks in advance to anyone who can help me with this :)

I'm attempting to run the TS sample from:

ftp://ftp.embeddedarm.com/ts-arm-sbc/ts-7260-linux/samples/button.c

modified slightly to toggle output on the DIO1 header, rather than the on-board
LEDs.  I'm monitoring DIO1 pin 9 (DIO_4) with a volt meter across a resister to
ground, and it reads a constant 5.6mV, even when the program enters into the
toggle loop.

Can anyone tell me what I need to do differently?

Don


int main(int argc, char **argv)
{
    volatile unsigned int *PBDR, *PBDDR, *GPIOBDB;
    int i;
    unsigned char state;
    unsigned char *start;
    int fd = open("/dev/mem", O_RDWR|O_SYNC);

    start = mmap(0, getpagesize(), PROT_READ|PROT_WRITE, MAP_SHARED, fd,
0x80840000);
    PBDR = (unsigned int *)(start + 0x04);     // port b
    PBDDR = (unsigned int *)(start + 0x14);    // port b direction register
    GPIOBDB = (unsigned int *)(start + 0xC4);  // debounce on port b

    *PBDDR = 0xf0; 		      // upper nibble output, lower nibble input
    *GPIOBDB = 0x01; 		      // enable debounce on bit 0

    state = *PBDR;                             // read initial state
    while (state & 0x01) {                     // wait until button goes low
       state = *PBDR;                          // remember bit 0 is pulled up
with 4.7k ohm
    }


    // blink 5 times, sleep 1 second so it's visible
    for (i = 0; i < 5; i++) {
       *PBDR = 0xf0;
       sleep(1);
       *PBDR = 0x00;
       sleep(1);
    }
    close(fd);
    return 0;
}

I am even seeing the same behavior using TS's scripts in ts7xxx.subr
(ftp://ftp.embeddedarm.com/ts-arm-sbc/ts-7260-linux/binaries/ts-scripts/ts7xxx.s\
ubr).  No change in in the output value from toggling the output line:

ts7000:~# dio_dir_set 4 1
0xF0
ts7000:~# dio_data_set 4 0
0xF
ts7000:~# dio_data_set 4 1
0xF


Wtf?

Don

Rekcut_Nod <dtucker@...> [2011-07-01 19:54:02]:

> I am even seeing the same behavior using TS's scripts in ts7xxx.subr
>
(ftp://ftp.embeddedarm.com/ts-arm-sbc/ts-7260-linux/binaries/ts-scripts/ts7xxx.s\
ubr).
> No change in in the output value from toggling the output line:
>
> ts7000:~# dio_dir_set 4 1
> 0xF0
> ts7000:~# dio_data_set 4 0
> 0xF
> ts7000:~# dio_data_set 4 1
> 0xF
>
> Wtf?

Maybe you should ask their support instead of whinning here? :-) With a decent
kernel, you could use in-kernel gpio[1] library.

1. http://tech.groups.yahoo.com/group/ts-7000/message/19317

-- ynezz

As I said in another thread only the other day, you have to be carefull
when using integer pointers[1].

Change your pointers to "unsigned char *" from "unsigned int *"

Jim

[1] you might try printing out the hex values of start, PBDR & PBDDR,
and see if the numbers are what you think they should. You will
find they are start+0x10, start+0x50

To C  the address of (start+0x04) is the same as the address of start[4]
(the fourth integer in the integer array start) which is of course at
start+16 or start+0x10. As I said above using byte pointers is sooooo much
easier.

On Fri, 1 Jul 2011, Rekcut_Nod wrote:

> I'm attempting to run the TS sample from:
>
> ftp://ftp.embeddedarm.com/ts-arm-sbc/ts-7260-linux/samples/button.c
>
> modified slightly to toggle output on the DIO1 header, rather than the
> on-board LEDs.  I'm monitoring DIO1 pin 9 (DIO_4) with a volt meter
> across a resister to ground, and it reads a constant 5.6mV, even when the
> program enters into the toggle loop.
>
> Can anyone tell me what I need to do differently?
>
> Don
>
>
> int main(int argc, char **argv)
> {
>    volatile unsigned int *PBDR, *PBDDR, *GPIOBDB;
>    int i;
>    unsigned char state;
>    unsigned char *start;
>    int fd = open("/dev/mem", O_RDWR|O_SYNC);
>
>    start = mmap(0, getpagesize(), PROT_READ|PROT_WRITE, MAP_SHARED, fd,
0x80840000);
>    PBDR = (unsigned int *)(start + 0x04);     // port b
>    PBDDR = (unsigned int *)(start + 0x14);    // port b direction register
>    GPIOBDB = (unsigned int *)(start + 0xC4);  // debounce on port b
>
>    *PBDDR = 0xf0; 		      // upper nibble output, lower nibble input
>    *GPIOBDB = 0x01; 		      // enable debounce on bit 0
>
>    state = *PBDR;                             // read initial state
>    while (state & 0x01) {                     // wait until button goes low
>       state = *PBDR;                          // remember bit 0 is pulled up
with 4.7k ohm
>    }
>
>
>    // blink 5 times, sleep 1 second so it's visible
>    for (i = 0; i < 5; i++) {
>       *PBDR = 0xf0;
>       sleep(1);
>       *PBDR = 0x00;
>       sleep(1);
>    }
>    close(fd);
>    return 0;
> }
>
>

On Sat, 2 Jul 2011, Jim Jackson wrote:

>
> As I said in another thread only the other day, you have to be carefull
> when using integer pointers[1].
>
> Change your pointers to "unsigned char *" from "unsigned int *"
>
> Jim
>
> [1] you might try printing out the hex values of start, PBDR & PBDDR,
> and see if the numbers are what you think they should. You will
> find they are start+0x10, start+0x50
>
> To C  the address of (start+0x04) is the same as the address of start[4]
> (the fourth integer in the integer array start) which is of course at
        ^^^^^^

surprized no one picked me up. I meant the 5th integer.

> start+16 or start+0x10. As I said above using byte pointers is sooooo much
> easier.
>
> On Fri, 1 Jul 2011, Rekcut_Nod wrote:
>
> > I'm attempting to run the TS sample from:
> >
> > ftp://ftp.embeddedarm.com/ts-arm-sbc/ts-7260-linux/samples/button.c
> >
> > modified slightly to toggle output on the DIO1 header, rather than the
> > on-board LEDs.  I'm monitoring DIO1 pin 9 (DIO_4) with a volt meter
> > across a resister to ground, and it reads a constant 5.6mV, even when the
> > program enters into the toggle loop.
> >
> > Can anyone tell me what I need to do differently?
> >
> > Don
> >
> >
> > int main(int argc, char **argv)
> > {
> >    volatile unsigned int *PBDR, *PBDDR, *GPIOBDB;
> >    int i;
> >    unsigned char state;
> >    unsigned char *start;
> >    int fd = open("/dev/mem", O_RDWR|O_SYNC);
> >
> >    start = mmap(0, getpagesize(), PROT_READ|PROT_WRITE, MAP_SHARED, fd,
0x80840000);
> >    PBDR = (unsigned int *)(start + 0x04);     // port b
> >    PBDDR = (unsigned int *)(start + 0x14);    // port b direction register
> >    GPIOBDB = (unsigned int *)(start + 0xC4);  // debounce on port b
> >
> >    *PBDDR = 0xf0; 		      // upper nibble output, lower nibble input
> >    *GPIOBDB = 0x01; 		      // enable debounce on bit 0
> >
> >    state = *PBDR;                             // read initial state
> >    while (state & 0x01) {                     // wait until button goes low
> >       state = *PBDR;                          // remember bit 0 is pulled up
with 4.7k ohm
> >    }
> >
> >
> >    // blink 5 times, sleep 1 second so it's visible
> >    for (i = 0; i < 5; i++) {
> >       *PBDR = 0xf0;
> >       sleep(1);
> >       *PBDR = 0x00;
> >       sleep(1);
> >    }
> >    close(fd);
> >    return 0;
> > }
> >
> >
>

--- In ts-7000@yahoogroups.com, "jeffwebbuk1" <jeffwebbuk1@...> wrote:
>
> Hi all,
>
> First up, I'm a novice when it comes to UART stuff so please be kind :)
>
> I've been developing on a TS-7550. I've connected the rs232 to an external
controller. By running the following:
>
> xuartctl --port=0 --speed=9600
>
> I can manually type the letter 'a', for example, hit return and the controller
sends a nice big string back to the screen like :xyz123;
>
> But what I really want to do is have a simple shell script that sends 'a' to
port 0 every x seconds, and when it gets the string back it assigns it to a
variable for use by other functions.
>
> I've read all the manuals and scoured the net, but even why I try the
suggested test of something like:
>
> echo "hello world" > /dev/pts/0
>
> it doesn't actually do anything :(
>
> Could anyone possibly point me in the right direction as it's the very last
bit of the puzzle to make my whole fun project work!
>
> Thanks in advance to anyone who can help me with this :)

The xuartctl line as you have it sets up so that standard input is sent to the
port and conversely bytes read from the serial port are sent to standard output.
That's fine for interactive use but not for a shell script.

You will probably need to add the --server option which makes the xuartctl
program daemonise itself and creates a /dev/pts/XX device for you to read to and
write from.

The tricky thing is guaranteeing what device has been created.  If you have made
one or more telnet connection to the board, that will start to create /dev/pts
entries as well.

I don't think shell script is the best way to handle serial I/O, I am afraid.

It would be really nice to use Python and its serial libraries, but building
that lot has got to be a major job.

All my serial handling is one from C - where you do at least have complete
control.

In your project you will have to handle timeouts to decide when you have got a
complete string back.  Unless you can find an equivalent to 'read' which accepts
a timeout parameter.


>

Hi,

I am working on ts-7800 and would like to use kernel 2.6.23 or later.
For this purpose I have tried to compile the kernel from
ftp://ftp.embeddedarm.com/ts-arm-sbc/ts-7800-linux/sources/2.6.34.tar.gz
and as tool-chain, I have used
ftp://ftp.embeddedarm.com/ts-arm-sbc/ts-7800-linux/cross-toolchains/ts7800-cross\
tool-linux-gnueabi-2008q3-2.tar.gz,
but it does not work.
During the boot

"Uncompressing Linux... done, booting the kernel."

then it stuck,

Does Kernel 2.6.34 from embeddedarm.com work with ts-7800 embedded sbc?
If not, how can I work Kernel 2.6.34 on ts-7800?

Thanks for any kind of help.

Bolat

Hi,

My guess would be that you have no parameters set in make menuconfig -> boot
options -> default kernel command string. To see why it just hangs, add
console=ttyS0,115200n8 to the line. TS kernel default is console=none and then
you don't see the kernel panic message.

An alternative would be to use a kernel.org kernel with make
orion5x_defconfig... There are several messages in this Yahoo! group describing
the process of compiling a kernel.org kernel, but it is not easy when you have
little experience. As a starting point, you can look at message no 20289 in this
Yahoo! group.

Jaan

--- In ts-7000@yahoogroups.com, "bdinc2001" <bdinc2001@...> wrote:
>
> Hi,
>
> I am working on ts-7800 and would like to use kernel 2.6.23 or later.
> For this purpose I have tried to compile the kernel from
ftp://ftp.embeddedarm.com/ts-arm-sbc/ts-7800-linux/sources/2.6.34.tar.gz
> and as tool-chain, I have used
>
ftp://ftp.embeddedarm.com/ts-arm-sbc/ts-7800-linux/cross-toolchains/ts7800-cross\
tool-linux-gnueabi-2008q3-2.tar.gz,
> but it does not work.
> During the boot
>
> "Uncompressing Linux... done, booting the kernel."
>
> then it stuck,
>
> Does Kernel 2.6.34 from embeddedarm.com work with ts-7800 embedded sbc?
> If not, how can I work Kernel 2.6.34 on ts-7800?
>
> Thanks for any kind of help.
>
> Bolat

Hi, all

I just received a TS-7260 with TS-GSM1 + WaveCOM Q64 GSM modem onboard. To have
a quick test of the Q64 modem, I setup the TS-GSM1 to use COM2 (by shorting JP1
on TS-GSM1, with the rest of the jumpers as factory default). I then tried
accessing COM2 using picocom. The output is shown below:
-----------------------------------
$ ./picocom /dev/ttyAM1
picocom v1.6

port is        : /dev/ttyAM1
flowcontrol    : none
baudrate is    : 9600
parity is      : none
databits are   : 8
escape is      : C-a
local echo is  : no
noinit is      : no
noreset is     : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv
imap is        :
omap is        :
emap is        : crcrlf,delbs,

Removing stale lock: /var/lock/LCK..ttyAM1
Terminal ready
-----------------------------------

I typed "AT" and hit the Enter key but no response was received.

I am wondering if my way of testing the functionality of the Q64 modem is
correct. Hope someone out there can shed me some light.

Thanks

Tong

Thanks, Jim. I changed PBDR and PBDDR from unsigned int to unsigned
char. PBDR, and PBDDR look like what I would expect, but I'm not sure
what I should be seeing for start.

start= 2AAC9000, PBDR= 2AAC9004, PBDDR= 2AAC9014.

On 7/2/2011 3:48 AM, Jim Jackson wrote:
>
>
> As I said in another thread only the other day, you have to be carefull
> when using integer pointers[1].
>
> Change your pointers to "unsigned char *" from "unsigned int *"
>
> Jim
>
> [1] you might try printing out the hex values of start, PBDR & PBDDR,
> and see if the numbers are what you think they should. You will
> find they are start+0x10, start+0x50
>
> To C the address of (start+0x04) is the same as the address of start[4]
> (the fourth integer in the integer array start) which is of course at
> start+16 or start+0x10. As I said above using byte pointers is sooooo
> much
> easier.
>
> On Fri, 1 Jul 2011, Rekcut_Nod wrote:
>
> > I'm attempting to run the TS sample from:
> >
> > ftp://ftp.embeddedarm.com/ts-arm-sbc/ts-7260-linux/samples/button.c
> >
> > modified slightly to toggle output on the DIO1 header, rather than the
> > on-board LEDs. I'm monitoring DIO1 pin 9 (DIO_4) with a volt meter
> > across a resister to ground, and it reads a constant 5.6mV, even
> when the
> > program enters into the toggle loop.
> >
> > Can anyone tell me what I need to do differently?
> >
> > Don
> >
> >
> > int main(int argc, char **argv)
> > {
> > volatile unsigned int *PBDR, *PBDDR, *GPIOBDB;
> > int i;
> > unsigned char state;
> > unsigned char *start;
> > int fd = open("/dev/mem", O_RDWR|O_SYNC);
> >
> > start = mmap(0, getpagesize(), PROT_READ|PROT_WRITE, MAP_SHARED, fd,
> 0x80840000);
> > PBDR = (unsigned int *)(start + 0x04); // port b
> > PBDDR = (unsigned int *)(start + 0x14); // port b direction register
> > GPIOBDB = (unsigned int *)(start + 0xC4); // debounce on port b
> >
> > *PBDDR = 0xf0; // upper nibble output, lower nibble input
> > *GPIOBDB = 0x01; // enable debounce on bit 0
> >
> > state = *PBDR; // read initial state
> > while (state & 0x01) { // wait until button goes low
> > state = *PBDR; // remember bit 0 is pulled up with 4.7k ohm
> > }
> >
> >
> > // blink 5 times, sleep 1 second so it's visible
> > for (i = 0; i < 5; i++) {
> > *PBDR = 0xf0;
> > sleep(1);
> > *PBDR = 0x00;
> > sleep(1);
> > }
> > close(fd);
> > return 0;
> > }
> >
> >
>
>

Thanks, Mahendiran.  I know that this portion of my code works, since
the program will wait forever until I ground DIO1 pin 1, as it should.

Don

On 7/2/2011 3:58 AM, mahendiran gopal wrote:
> Hi,
> Remove the below code in your program and compile then try it will work.
>  state = *PBDR; // read initial state
>  while (state & 0x01) { // wait until button goes low
>  state = *PBDR; // remember bit 0 is pulled up with 4.7k ohm
>  }
> Regargs,
> Mahendiran
> India
>
>
> On Sat, Jul 2, 2011 at 2:18 PM, Jim Jackson <jj@...
> <mailto:jj@...>> wrote:
>
>
>     As I said in another thread only the other day, you have to be
>     carefull
>     when using integer pointers[1].
>
>     Change your pointers to "unsigned char *" from "unsigned int *"
>
>     Jim
>
>     [1] you might try printing out the hex values of start, PBDR & PBDDR,
>     and see if the numbers are what you think they should. You will
>     find they are start+0x10, start+0x50
>
>     To C the address of (start+0x04) is the same as the address of
>     start[4]
>     (the fourth integer in the integer array start) which is of course at
>     start+16 or start+0x10. As I said above using byte pointers is
>     sooooo much
>     easier.
>
>
>
>     On Fri, 1 Jul 2011, Rekcut_Nod wrote:
>
>     > I'm attempting to run the TS sample from:
>     >
>     > ftp://ftp.embeddedarm.com/ts-arm-sbc/ts-7260-linux/samples/button.c
>     >
>     > modified slightly to toggle output on the DIO1 header, rather
>     than the
>     > on-board LEDs. I'm monitoring DIO1 pin 9 (DIO_4) with a volt meter
>     > across a resister to ground, and it reads a constant 5.6mV, even
>     when the
>     > program enters into the toggle loop.
>     >
>     > Can anyone tell me what I need to do differently?
>     >
>     > Don
>     >
>     >
>     > int main(int argc, char **argv)
>     > {
>     > volatile unsigned int *PBDR, *PBDDR, *GPIOBDB;
>     > int i;
>     > unsigned char state;
>     > unsigned char *start;
>     > int fd = open("/dev/mem", O_RDWR|O_SYNC);
>     >
>     > start = mmap(0, getpagesize(), PROT_READ|PROT_WRITE, MAP_SHARED,
>     fd, 0x80840000);
>     > PBDR = (unsigned int *)(start + 0x04); // port b
>     > PBDDR = (unsigned int *)(start + 0x14); // port b direction register
>     > GPIOBDB = (unsigned int *)(start + 0xC4); // debounce on port b
>     >
>     > *PBDDR = 0xf0; // upper nibble output, lower nibble input
>     > *GPIOBDB = 0x01; // enable debounce on bit 0
>     >
>     > state = *PBDR; // read initial state
>     > while (state & 0x01) { // wait until button goes low
>     > state = *PBDR; // remember bit 0 is pulled up with 4.7k ohm
>     > }
>     >
>     >
>     > // blink 5 times, sleep 1 second so it's visible
>     > for (i = 0; i < 5; i++) {
>     > *PBDR = 0xf0;
>     > sleep(1);
>     > *PBDR = 0x00;
>     > sleep(1);
>     > }
>     > close(fd);
>     > return 0;
>     > }
>     >
>     >
>
>
>

On 05/07/11 11:16, Kok Hua wrote:
> Hi, all
>
> I just received a TS-7260 with TS-GSM1 + WaveCOM Q64 GSM modem onboard. To
have a quick test of the Q64 modem, I setup the TS-GSM1 to use COM2 (by shorting
JP1 on TS-GSM1, with the rest of the jumpers as factory default). I then tried
accessing COM2 using picocom. The output is shown below:
> -----------------------------------
> $ ./picocom /dev/ttyAM1
> picocom v1.6
>
>
When I used TS-GSM1 on TS7800, the device file is not ttyAMx. I had to
use ttts4. Not too sure about TS7260.

I think Simon is right. I use the TS-GSM1 with the TS-7260. The TS-GSM1
connects to the TS-7260 through the ISA bus. COM2 (/dev/ttyAM1) is a
separate header on the TS-7260 board. I connect through COM3, which is
/dev/ttyS0.

Don

On 7/5/2011 9:27 AM, Simon Leung wrote:
>
> On 05/07/11 11:16, Kok Hua wrote:
> > Hi, all
> >
> > I just received a TS-7260 with TS-GSM1 + WaveCOM Q64 GSM modem
> onboard. To have a quick test of the Q64 modem, I setup the TS-GSM1 to
> use COM2 (by shorting JP1 on TS-GSM1, with the rest of the jumpers as
> factory default). I then tried accessing COM2 using picocom. The
> output is shown below:
> > -----------------------------------
> > $ ./picocom /dev/ttyAM1
> > picocom v1.6
> >
> >
> When I used TS-GSM1 on TS7800, the device file is not ttyAMx. I had to
> use ttts4. Not too sure about TS7260.
>
>

On Tue, 5 Jul 2011, Don Tucker wrote:

> Thanks, Jim. I changed PBDR and PBDDR from unsigned int to unsigned char.
> PBDR, and PBDDR look like what I would expect, but I'm not sure what I should
> be seeing for start.

what you see is what you get - The page address returned by the mmap call.
You see that in actual fact PBDR IS start+0x4 and PBDDR IS start + 0x14
If you had used unsigned int * they would NOT have been what you expected.

When you write/read from these addresses you ARE accessing the correct
locations.

cheers
Jim
> start= 2AAC9000, PBDR= 2AAC9004, PBDDR= 2AAC9014.
>
> On 7/2/2011 3:48 AM, Jim Jackson wrote:
> >
> >
> > As I said in another thread only the other day, you have to be carefull
> > when using integer pointers[1].
> >
> > Change your pointers to "unsigned char *" from "unsigned int *"
> >
> > Jim
> >
> > [1] you might try printing out the hex values of start, PBDR & PBDDR,
> > and see if the numbers are what you think they should. You will
> > find they are start+0x10, start+0x50
> >
> > To C the address of (start+0x04) is the same as the address of start[4]
> > (the fourth integer in the integer array start) which is of course at
> > start+16 or start+0x10. As I said above using byte pointers is sooooo much
> > easier.
> >
> > On Fri, 1 Jul 2011, Rekcut_Nod wrote:
> >
> > > I'm attempting to run the TS sample from:
> > >
> > > ftp://ftp.embeddedarm.com/ts-arm-sbc/ts-7260-linux/samples/button.c
> > >
> > > modified slightly to toggle output on the DIO1 header, rather than the
> > > on-board LEDs. I'm monitoring DIO1 pin 9 (DIO_4) with a volt meter
> > > across a resister to ground, and it reads a constant 5.6mV, even when the
> > > program enters into the toggle loop.
> > >
> > > Can anyone tell me what I need to do differently?
> > >
> > > Don
> > >
> > >
> > > int main(int argc, char **argv)
> > > {
> > > volatile unsigned int *PBDR, *PBDDR, *GPIOBDB;
> > > int i;
> > > unsigned char state;
> > > unsigned char *start;
> > > int fd = open("/dev/mem", O_RDWR|O_SYNC);
> > >
> > > start = mmap(0, getpagesize(), PROT_READ|PROT_WRITE, MAP_SHARED, fd,
> > 0x80840000);
> > > PBDR = (unsigned int *)(start + 0x04); // port b
> > > PBDDR = (unsigned int *)(start + 0x14); // port b direction register
> > > GPIOBDB = (unsigned int *)(start + 0xC4); // debounce on port b
> > >
> > > *PBDDR = 0xf0; // upper nibble output, lower nibble input
> > > *GPIOBDB = 0x01; // enable debounce on bit 0
> > >
> > > state = *PBDR; // read initial state
> > > while (state & 0x01) { // wait until button goes low
> > > state = *PBDR; // remember bit 0 is pulled up with 4.7k ohm
> > > }
> > >
> > >
> > > // blink 5 times, sleep 1 second so it's visible
> > > for (i = 0; i < 5; i++) {
> > > *PBDR = 0xf0;
> > > sleep(1);
> > > *PBDR = 0x00;
> > > sleep(1);
> > > }
> > > close(fd);
> > > return 0;
> > > }
> > >
> > >
> >
> >
>
>

On Tue, 5 Jul 2011, Kok Hua wrote:

> Hi, all
>
> I just received a TS-7260 with TS-GSM1 + WaveCOM Q64 GSM modem onboard.
> To have a quick test of the Q64 modem, I setup the TS-GSM1 to use COM2
> (by shorting JP1 on TS-GSM1, with the rest of the jumpers as factory
> default). I then tried accessing COM2 using picocom. The output is shown
> below:
> -----------------------------------
> $ ./picocom /dev/ttyAM1
               ^^^^^^^^^^^

You have to be very very careful about using words like COM1/COM2 etc.
/dev/ttyAM0 /dev/ttyAM1 have NOTHING to do with the GSM board. They
are the 2 RS232 ports on the TS7260 board.

The GSM1 board provides ANOTHER serial interface, using addresses
and IRQs that would correspond to COM1 COM2 etc on a STANDARD X86 PC.

So I suggest leaving the jumpers exactly as factory default, and using
the device /dev/tts/0 , if you keep the settings you have now then use
/dev/tts/1

> picocom v1.6
>
> port is        : /dev/ttyAM1
> flowcontrol    : none
> baudrate is    : 9600
> parity is      : none
> databits are   : 8
> escape is      : C-a
> local echo is  : no
> noinit is      : no
> noreset is     : no
> nolock is      : no
> send_cmd is    : sz -vv
> receive_cmd is : rz -vv
> imap is        :
> omap is        :
> emap is        : crcrlf,delbs,
>
> Removing stale lock: /var/lock/LCK..ttyAM1
> Terminal ready
> -----------------------------------
>
> I typed "AT" and hit the Enter key but no response was received.
>
> I am wondering if my way of testing the functionality of the Q64 modem is
correct. Hope someone out there can shed me some light.
>
> Thanks
>
> Tong
>
>
>

Thanks to all of you for pointing out my mistake on the COM port. I can now talk
to the Q64 on my TS-7260 via serial port /dev/tts/0, using baud rate of 115200.

$ ./picocom -b 115200 --echo -f h /dev/tts/0
picocom v1.6

port is        : /dev/tts/0
flowcontrol    : RTS/CTS
baudrate is    : 115200
parity is      : none
databits are   : 8
escape is      : C-a
local echo is  : yes
noinit is      : no
noreset is     : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv
imap is        :
omap is        :
emap is        : crcrlf,delbs,

Terminal ready
AATT

OK
AATTEE00

OK
AT

OK

Tong

--- In ts-7000@yahoogroups.com, Jim Jackson <jj@...> wrote:
>
>
>
>
> On Tue, 5 Jul 2011, Kok Hua wrote:
>
> > Hi, all
> >
> > I just received a TS-7260 with TS-GSM1 + WaveCOM Q64 GSM modem onboard.
> > To have a quick test of the Q64 modem, I setup the TS-GSM1 to use COM2
> > (by shorting JP1 on TS-GSM1, with the rest of the jumpers as factory
> > default). I then tried accessing COM2 using picocom. The output is shown
> > below:
> > -----------------------------------
> > $ ./picocom /dev/ttyAM1
>               ^^^^^^^^^^^
>
> You have to be very very careful about using words like COM1/COM2 etc.
> /dev/ttyAM0 /dev/ttyAM1 have NOTHING to do with the GSM board. They
> are the 2 RS232 ports on the TS7260 board.
>
> The GSM1 board provides ANOTHER serial interface, using addresses
> and IRQs that would correspond to COM1 COM2 etc on a STANDARD X86 PC.
>
> So I suggest leaving the jumpers exactly as factory default, and using
> the device /dev/tts/0 , if you keep the settings you have now then use
> /dev/tts/1
>
> > picocom v1.6
> >
> > port is        : /dev/ttyAM1
> > flowcontrol    : none
> > baudrate is    : 9600
> > parity is      : none
> > databits are   : 8
> > escape is      : C-a
> > local echo is  : no
> > noinit is      : no
> > noreset is     : no
> > nolock is      : no
> > send_cmd is    : sz -vv
> > receive_cmd is : rz -vv
> > imap is        :
> > omap is        :
> > emap is        : crcrlf,delbs,
> >
> > Removing stale lock: /var/lock/LCK..ttyAM1
> > Terminal ready
> > -----------------------------------
> >
> > I typed "AT" and hit the Enter key but no response was received.
> >
> > I am wondering if my way of testing the functionality of the Q64 modem is
correct. Hope someone out there can shed me some light.
> >
> > Thanks
> >
> > Tong
> >
> >
> >
>

--- In ts-7000@yahoogroups.com, "naturalwatt" <martin@...> wrote:
>
>
>
> --- In ts-7000@yahoogroups.com, "jeffwebbuk1" <jeffwebbuk1@> wrote:
> >
> > Hi all,
> >
> > First up, I'm a novice when it comes to UART stuff so please be kind :)
> >
> > I've been developing on a TS-7550. I've connected the rs232 to an external
controller. By running the following:
> >
> > xuartctl --port=0 --speed=9600
> >
> > I can manually type the letter 'a', for example, hit return and the
controller sends a nice big string back to the screen like :xyz123;
> >
> > But what I really want to do is have a simple shell script that sends 'a' to
port 0 every x seconds, and when it gets the string back it assigns it to a
variable for use by other functions.
> >
> > I've read all the manuals and scoured the net, but even why I try the
suggested test of something like:
> >
> > echo "hello world" > /dev/pts/0
> >
> > it doesn't actually do anything :(
> >
> > Could anyone possibly point me in the right direction as it's the very last
bit of the puzzle to make my whole fun project work!
> >
> > Thanks in advance to anyone who can help me with this :)
>
> The xuartctl line as you have it sets up so that standard input is sent to the
port and conversely bytes read from the serial port are sent to standard output.
That's fine for interactive use but not for a shell script.
>
> You will probably need to add the --server option which makes the xuartctl
program daemonise itself and creates a /dev/pts/XX device for you to read to and
write from.
>
> The tricky thing is guaranteeing what device has been created.  If you have
made one or more telnet connection to the board, that will start to create
/dev/pts entries as well.
>
> I don't think shell script is the best way to handle serial I/O, I am afraid.
>
> It would be really nice to use Python and its serial libraries, but building
that lot has got to be a major job.
>
> All my serial handling is one from C - where you do at least have complete
control.
>
> In your project you will have to handle timeouts to decide when you have got a
complete string back.  Unless you can find an equivalent to 'read' which accepts
a timeout parameter.
>
>
> >
>

Hi there,

Many thanks for your reply - Cracked it in the end, thanks to help from TS
themselves :). Set a simple script to 'listen' for when /dev/pts/X changes,
checks for the string length, and if correct assigns it to a temporary variable.
Works like a charm.

I am using:

stty -F /dev/pts/0 raw # only need to do this once
read TEST < /dev/pts/0 # can then read the variable $TEST in rest of script.

I've had the script running every three seconds for almost a week now and it's
behaving itself wonderfully.

Thanks again for your help and advice!

I am trying to run a simple Hello World QT program using QT embedded 3.3.4(the
recommended version by Technologic). It executes fine, except that any mouse
movement paints a yellow color over the window and toolbar wherever the cursor
moves.

We are using a TS 7800, TS-7KV VGA card. If any one has any clue or suggestions
OR have come across this issue please reply or email me at vivints@...

Thanks in advance
V

Greetings peoples..

I want to get audio output from a TS-7550, I am awaiting a USB audio
device (not sure of spec etc)

Does anyone have any pointers, or better yet, a howto ??

my best guess would to be put a codec on a small board and attach to the TWI

--- On Fri, 7/8/11, Neil Stone <neil@...> wrote:

> From: Neil Stone <neil@...>
> Subject: [ts-7000] Sound
> To: ts-7000@yahoogroups.com
> Date: Friday, July 8, 2011, 12:55 PM
> Greetings peoples..
>
> I want to get audio output from a TS-7550, I am awaiting a
> USB audio
> device (not sure of spec etc)
>
> Does anyone have any pointers, or better yet, a howto ??
>
>

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

On 08/07/11 17:55, Neil Stone wrote:
> Greetings peoples..
>
> I want to get audio output from a TS-7550, I am awaiting a USB audio
> device (not sure of spec etc)
>
> Does anyone have any pointers, or better yet, a howto ??
>
_really_ helpfull output from the kernel after plugging in the USB dongle;

[265675.090000] usb 2-2: new full speed USB device using str8100-ohci
and address 2
[265675.270000] usb 2-2: configuration #1 chosen from 1 choice

*sigh*

time to poke things..
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4YLN4ACgkQz3Av8JKgzxT9IQCgpqMbxJ7BxULT4LvGZbXVEnVv
Nq8Amwd/jEQVqI3S0CcS9/NCbu2PLKz1
=YBz+
-----END PGP SIGNATURE-----

Neil Stone <neil@...> [2011-07-09 11:26:44]:

> > Does anyone have any pointers, or better yet, a howto ??
> >
> _really_ helpfull output from the kernel after plugging in the USB dongle;

And what would you rather see sir, link to some howto 'howto use google'? :-)

> time to poke things..

lsusb, lookup that VID/PID via google etc...

If I were you, I would try to make it work on some desktop distro first and
then make it work on the embedded device. This could save you some hours of
*sigh*s.

-- ynezz

Hi All,

Does anyone have any pointers to sample code to read the analog inputs
on a TS-7350?  Also I was wondering what the voltage range is on those
inputs.

Thanks,
Fred

Hi Jaan,

Thanks for your sincere help.

I have changed CONFIG_CMDLINE as
CONFIG_CMDLINE="console=ttyS0,115200n8", but there is no change.

Still I cannot see anything on the terminal except

>> TS-BOOTROM - built Jun 10 2009
>> Copyright (c) 2008, Technologic Systems
>> Booting from SD card...
.
.
.
.
Uncompressing Linux... done, booting the kernel.

Do I need to modify head.S and/or head-xscale.S in arc/arm/boot/compressed/ to
pass board parameter to the kernel?
as in article no 20289
#ifdef CONFIG_MACH_TS78XX
ldr r1, =0x00000674 @ TS-7800 is 0x674
#endif

My board is ts-7800, Rev D, and JP1 is connected.

Best Regards.
--- In ts-7000@yahoogroups.com, "Jaan" <jaan_r@...> wrote:
>
> Hi,
>
> My guess would be that you have no parameters set in make menuconfig -> boot
options -> default kernel command string. To see why it just hangs, add
console=ttyS0,115200n8 to the line. TS kernel default is console=none and then
you don't see the kernel panic message.
>
> An alternative would be to use a kernel.org kernel with make
orion5x_defconfig... There are several messages in this Yahoo! group describing
the process of compiling a kernel.org kernel, but it is not easy when you have
little experience. As a starting point, you can look at message no 20289 in this
Yahoo! group.
>
> Jaan
>
> --- In ts-7000@yahoogroups.com, "bdinc2001" <bdinc2001@> wrote:
> >
> > Hi,
> >
> > I am working on ts-7800 and would like to use kernel 2.6.23 or later.
> > For this purpose I have tried to compile the kernel from
ftp://ftp.embeddedarm.com/ts-arm-sbc/ts-7800-linux/sources/2.6.34.tar.gz
> > and as tool-chain, I have used
> >
ftp://ftp.embeddedarm.com/ts-arm-sbc/ts-7800-linux/cross-toolchains/ts7800-cross\
tool-linux-gnueabi-2008q3-2.tar.gz,
> > but it does not work.
> > During the boot
> >
> > "Uncompressing Linux... done, booting the kernel."
> >
> > then it stuck,
> >
> > Does Kernel 2.6.34 from embeddedarm.com work with ts-7800 embedded sbc?
> > If not, how can I work Kernel 2.6.34 on ts-7800?
> >
> > Thanks for any kind of help.
> >
> > Bolat
>