SCC3 console problem on MPC860

SCC3 console problem on MPC860

[??????]

Hi, all
I am not used to write in English.

I would like to use SCC3 as second console, and use SMC1 as first console.
I ported denx kernel 2.4.3-pre4 into my 860 board.
when I compiling, checked SCC3 for UART option in MPC8xx CPM option.
SMC1(ttyS0) is connected to my linux box COM2, SCC3(ttyS1) is connected to COM1.

After booting, in COM2 echo 1111 > /dev/ttyS1 result is shown in SCC3(ttyS1).
so far good.
but, COM1 port don't any receive keyboard key.

In /arch/ppc/uart.c
I modified CONFIG_SERIAL_CONSOLE_PORT for SCC3 console

#if 1
#undef CONFIG_SERIAL_CONSOLE_PORT
#define CONFIG_SERIAL_CONSOLE_PORT	1
#endif

Is it enough to to make SCC3 console?

Thanks for any comments and replyings.

==================================================
우리 인터넷, Daum
평생 쓰는 무료 E-mail 주소 한메일넷
지구촌 한글 검색서비스 Daum FIREBALL
http://www.daum.net

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: SCC3 console problem on MPC860

[Wolfgang Denk]

In message <20010330095839.HM.30000000001Zxx8@www4.hanmail.net> you wrote:
>
> I would like to use SCC3 as second console, and use SMC1 as first console.
> I ported denx kernel 2.4.3-pre4 into my 860 board.
> when I compiling, checked SCC3 for UART option in MPC8xx CPM option.
> SMC1(ttyS0) is connected to my linux box COM2, SCC3(ttyS1) is connected to COM1.

What's the kernel output for the serial ports? Please send me your kernel boot messages!

> After booting, in COM2 echo 1111 > /dev/ttyS1 result is shown in SCC3(ttyS1).
> so far good.
> but, COM1 port don't any receive keyboard key.

Please define what you mean by COM1 and COM2.

How did you test this?

> In /arch/ppc/uart.c
> I modified CONFIG_SERIAL_CONSOLE_PORT for SCC3 console
>
> #if 1
> #undef CONFIG_SERIAL_CONSOLE_PORT
> #define CONFIG_SERIAL_CONSOLE_PORT	1
> #endif

If in your configuration SCC3 is the second entry in rs_table[], then
this should work.


Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
God made machine language; all the rest is the work of man.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: SCC3 console problem on MPC860

[Daris A Nevil]

Daum,

I had problems trying to get the uart.c driver to do what you wanted as
well.  I don't think it was really meant to support both SCC and SMC at
the same time.  I ended up splitting the driver into two different
drivers, making one work just for the SCC, and the other only for the
SMC.  This works quite well.

The code is in the QSLinux release, which you can download from
ftp:://qslinux.org.  When you untar the kernel you can find the two
drivers in the directory snmc/qslinux/kernel/drivers/char.

Regards,
Daris Nevil


?????? wrote:
>
> Hi, all
> I am not used to write in English.
>
> I would like to use SCC3 as second console, and use SMC1 as first console.
> I ported denx kernel 2.4.3-pre4 into my 860 board.
> when I compiling, checked SCC3 for UART option in MPC8xx CPM option.
> SMC1(ttyS0) is connected to my linux box COM2, SCC3(ttyS1) is connected to COM1.
>
> After booting, in COM2 echo 1111 > /dev/ttyS1 result is shown in SCC3(ttyS1).
> so far good.
> but, COM1 port don't any receive keyboard key.
>
> In /arch/ppc/uart.c
> I modified CONFIG_SERIAL_CONSOLE_PORT for SCC3 console
>
> #if 1
> #undef CONFIG_SERIAL_CONSOLE_PORT
> #define CONFIG_SERIAL_CONSOLE_PORT      1
> #endif
>
> Is it enough to to make SCC3 console?
>
> Thanks for any comments and replyings.
>
> ==================================================
> ¿ì¸® ÀÎÅͳÝ, Daum
> Æò»ý ¾²´Â ¹«·á E-mail ÁÖ¼Ò ÇѸÞÀϳÝ
> Áö±¸ÃÌ ÇÑ±Û °Ë»ö¼­ºñ½º Daum FIREBALL
> http://www.daum.net
>

--
Daris A Nevil
Simple Network Magic Corporation
401 Kentucky Lane
McKinney, TX 75069
214-793-7757
dnevil@snmc.com
www.snmc.com
quickstack.com
qslinux.org

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: SCC3 console problem on MPC860

[Wolfgang Denk]

In message <3AC49EC3.978D9A4A@snmc.com> you wrote:
>
> I had problems trying to get the uart.c driver to do what you wanted as
> well.  I don't think it was really meant to support both SCC and SMC at
> the same time.  I ended up splitting the driver into two different

I cannot verify this problem.

> drivers, making one work just for the SCC, and the other only for the
> SMC.  This works quite well.

This is really not needed.

We have tested the normal uart driver in a setup running on 5  serial
ports  (2  x  SMC, 3 x SCC, with Ethernet of the 4th SCC). No serious
load tests so  far,  but  basic  I/O  functions  worked  without  any
problems.

> The code is in the QSLinux release, which you can download from
> ftp:://qslinux.org.  When you untar the kernel you can find the two
> drivers in the directory snmc/qslinux/kernel/drivers/char.

Ummm... AFAIK QSLinux is based on a 2.2.5  kernel?  That's  _awfully_
old.  I  can  imagine  that there were lots of problems with the uart
driver at this time. And other bugs as well.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
"How is this place run - is it an anarchy?"
"No, I wouldn't say so; it is not that well organised..."

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/