RoboSavvy Forum

Re: no /etc/serial.conf

2011-10-13T02:54:37+01:00

afiebig wrote:
Hi, thanks for your advice, but i have no /etc/serial.conf

Normal you have to create it.
The default configuration file is : /var/lib/setserial/autoserial.conf
You could modify this one directly but I prefer to use /etc/serial.conf instead.
But be careful, if /etc/serial.conf exists, /var/lib/setserial/autoserial.conf is not used

afiebig wrote:
Now I realise that the IRQ are coded on the
/arch/alpha/include/asm/serial.h

it goes somethin like this:

Code:
/*UART CLK PORT IRQ FLAGS */ {0, BASE_BAUD, 0x3f8, 4, STD_COM_FLAGS}, /* ttyS0 */ {0, BASE_BAUD, 0x2f8, 3, STD_COM_FLAGS}, /* ttyS1 */ {0, BASE_BAUD, 0x3e8, 4, STD_COM_FLAGS}, /* ttyS2 */ {0, BASE_BAUD, 0x2e8, 3, STD_COM4_FLAGS}, /* ttyS3 */

so i change that and i'm compiling my kernel.

Yes it is an other good solution.

Good luck,
gdo

Statistics: Posted by gdo — Thu Oct 13, 2011 2:54 am

no /etc/serial.conf

2011-10-12T22:36:10+01:00

Hi, thanks for your advice, but i have no /etc/serial.conf

Now I realise that the IRQ are coded on the
/arch/alpha/include/asm/serial.h

it goes somethin like this:

Code:: /*UART CLK PORT IRQ FLAGS */ {0, BASE_BAUD, 0x3f8, 4, STD_COM_FLAGS}, /* ttyS0 */ {0, BASE_BAUD, 0x2f8, 3, STD_COM_FLAGS}, /* ttyS1 */ {0, BASE_BAUD, 0x3e8, 4, STD_COM_FLAGS}, /* ttyS2 */ {0, BASE_BAUD, 0x2e8, 3, STD_COM4_FLAGS}, /* ttyS3 */

so i change that and i'm compiling my kernel.

Statistics: Posted by afiebig — Wed Oct 12, 2011 10:36 pm

TTL (COM3) in Ubuntu

2011-10-12T16:11:13+01:00

Have a look at /etc/serial.conf.

That's were you can save your setserial configuration.

gdo

Statistics: Posted by gdo — Wed Oct 12, 2011 4:11 pm

Same IRQ on Serial Ports.

2011-10-11T15:40:50+01:00

Hi, I'm fairly new to this forum and would like to make a few
questions related to this thread.

I've configured COM3 and COM4 as shown in the previous post

haydndup wrote:
Also, I'm not sure if it's normal, but I have to rerun setserial every time the Roboard boots. Does setserial not save the configuration?

The problem is that when my Debian boot it says

Code:: Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A serial8250: ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A serial8250: ttyS3 at I/O 0x2e8 (irq = 3) is a 16550A

here I see that they share the same IRQ, if I use setserial the irq changes, but I'm not sure these changes will work until the roboard restarts.

so, there is my problem, i'm using ttyS0 for console redirect, and i need to use the ttyS2 for AX-12 Control, but their share the same IRQ.

Hope you can help me

Statistics: Posted by afiebig — Tue Oct 11, 2011 3:40 pm

TTL (COM3) in Ubuntu

2011-08-03T14:25:38+01:00

All is ok for me !

Thanks

Statistics: Posted by gdo — Wed Aug 03, 2011 2:25 pm

TTL (COM3) in Ubuntu

2011-08-03T05:31:06+01:00

roboard wrote:
...The details for our kernel configuring and building should be answered by our Linux engineer, who is on vacation this week. We will ask him to mention the details next week.

Hi gdo,

the following is the answer from our Linux engineer:

No kernel source is modified for COM3/COM4. We only set the following configuration for RoBoard's native COM before builing the kernel:

CONFIG_SERIAL_8250_NR_UARTS=8
CONFIG_SERIAL_8250_RUNTIME_UARTS=2

Statistics: Posted by roboard — Wed Aug 03, 2011 5:31 am

TTL (COM3) in Ubuntu

2011-07-26T20:53:51+01:00

Hi gdo,

COM1~COM4 have existed in serial.h and no need to update the serial.h unless you want to make the base address & IRQ of COM3/4 be hard coded in the kernel.

The details for our kernel configuring and building should be answered by our Linux engineer, who is on vacation this week. We will ask him to mention the details next week.

Statistics: Posted by roboard — Tue Jul 26, 2011 8:53 pm

TTL (COM3) in Ubuntu

2011-07-26T16:05:05+01:00

But kernel from kernel.org does it by default ?
The only thing is that the COM3/COM4 are not associated to an IRQ.

I'm sure we say the same thing in two different way.

Statistics: Posted by gdo — Tue Jul 26, 2011 4:05 pm

TTL (COM3) in Ubuntu

2011-07-26T15:23:47+01:00

gdo wrote:
...Does it mean you modified something in or near /arch/alpha/include/asm/serial.h file ?
...

Hi gdo,

we just configure and build the kernel to support COM3/4. "serial.h" is not modified.

Statistics: Posted by roboard — Tue Jul 26, 2011 3:23 pm

TTL (COM3) in Ubuntu

2011-07-26T13:15:25+01:00

As seen with haydndup, needed actions to use COM3 are :

- Set IRQ 10 as reserved in BIOS
- Launch the following comand : sudo setserial /dev/ttyS2 port 0x03e8 irq 10 autoconfig
- Be sure you have good permissions to access /dev/ttyS2

Tested on RB-100 with cutecom by plugging TX to RX. Communications parameters are 115200 8N1 and no flow controls.

@Haydndup, you confirm it is working for RB-110 ?

@roboard, when you say :

Alternatively, RoBoard's linux kernel has been configured to open COM3 and COM4 by default. So if you employ RoBoard's linux kernel, the COM3 and COM4 can work directly.

Does it mean you modified something in or near /arch/alpha/include/asm/serial.h file ?

gdo

Statistics: Posted by gdo — Tue Jul 26, 2011 1:15 pm

TTL (COM3) in Ubuntu

2011-07-26T11:01:27+01:00

haydndup wrote:
...I see that I have CONFIG_USB_SERIAL set to no. I know that this will affect COM5 and COm6 because they use the FTDI chip. Is it possible that this is affecting the 16550A UART chip too?

Hi haydndup,

CONFIG_USB_SERIAL shouldn't affect the COM3 and COM4. Your issue may be caused by inadequate configuration or option setting of Xenomai kernel; to confirm this, you may switch back to the normal Ubuntu kernel to see whether COM3/4 work on the normal kernel.

Statistics: Posted by roboard — Tue Jul 26, 2011 11:01 am

TTL (COM3) in Ubuntu

2011-07-26T09:24:39+01:00

Hi roboard,

Thanks for the help. I did initially set the 8250.nr_uarts when I followed the COM3 and COM4 tutorial on your site.

The weird thing is that I can see the ports, and I can open a connection to them, but I can't send/receive unless I am using the RB kernel. When I switch over to the Xeno kernel, I can't send/receive (I have checked this with an oscilloscope).

This makes me think it's something in the kernel .config, but I'm not sure what. I see that I have CONFIG_USB_SERIAL set to no. I know that this will affect COM5 and COm6 because they use the FTDI chip. Is it possible that this is affecting the 16550A UART chip too?

Statistics: Posted by haydndup — Tue Jul 26, 2011 9:24 am

TTL (COM3) in Ubuntu

2011-07-26T06:38:57+01:00

Hi haydndup,

1.
To enable COM3 & COM4 for your kernel, please try to modify the boot loader configuration file as follows (assuming you use GRUB):

title ...
root ...
kernel /boot/vmlinuz-2.6.34 root=... 8250.nr_uarts=4
initrd /boot/initrd.img-2.6.34

2.
RoBoIO 1.8/1.81 assumes that the serial device file names are "ttyS0" ~ "ttyS3". If you employ the real-time serial driver of Xenomai, the device file names for COM ports may change, and you may need to modify the com.cpp of RoBoIO 1.8/1.81 to adopt the new device names:

Find in com.cpp the following line:

Code:: static char* COM_portname[4] = {"/dev/ttyS0", "/dev/ttyS1", "/dev/ttyS2", "/dev/ttyS3"};

Modify the strings to the device names of Xenomai's real-time driver and then rebuild the RoBoIO.

Statistics: Posted by roboard — Tue Jul 26, 2011 6:38 am

TTL (COM3) in Ubuntu

2011-07-25T20:53:25+01:00

@ShiU_Damien,

Thanks for the config, I'm busy comparing it to my config and looking for differences. Unfortunately, I'm not sure what exactly I'm looking for.

With regards to the error message for com_Read(), all it says is "time-out to read bytes"

@roboard,

Thanks for the reply. What in the kernel config do I need to change? I've been comparing mine, but haven't found anything obvious that I need to change. If you can point me to the exact things I need to modify, I would greatly appreciate it.

I would love to use the roboard kernel where I know everything will work, but I have to use real-time Linux for my project, which means I can't use the kernel you provide.

On a separate note, as I mentioned in my first post, I am using Xenomai to provide hard real-time support. Now, Xenomai has a real-time driver for the 16550A which is what the RB-110 uses for COM3 and COM4. If I enable the real-time driver, would I still be able to use RoBoIO, or would I need to use standard Linux C serial? More info on the driver is here: http://www.xenomai.org/index.php/16550A

Thanks again!

Statistics: Posted by haydndup — Mon Jul 25, 2011 8:53 pm

TTL (COM3) in Ubuntu

2011-07-25T07:59:04+01:00

haydndup wrote:
...
Could the kernel be causing this? Is there any definite way to test that the COM3 and COM4 ports are even working?
...

Hi,

the kernels of most Linux distributions open only two COMs, and you need to manually modify the kernel configuration to open COM3 and COM4 in order to get them work.

Alternatively, RoBoard's linux kernel has been configured to open COM3 and COM4 by default. So if you employ RoBoard's linux kernel, the COM3 and COM4 can work directly.

Statistics: Posted by roboard — Mon Jul 25, 2011 7:59 am