Serial console ports on systems with no console connected.

Arun Dharankar ADharankar at ATTBI.Com
Tue Jul 9 22:08:15 EST 2002

Hello, and thanks for your reply!

The board has SCC4 and SMC1 based serial ports. I have
tried both of these as console ports under Linux and PPCBOOT.
PPCBOOT code is unmodified (as it is from the distribution) for
SCC4 and SMC1 code. The Linux code is unmodified for
SMC1, and I see this behavior in case of both these serial

The place where the BDI shows the PC to hang is in
serial_putc(...) waiting for the transmit buffer to be drained by the

    /* Wait for last character to go.
    while (tbdf->cbd_sc & BD_SC_READY)

Ofcourse, when the cable is present, things work well.

Though I dont see any code path, or from hardware perspective
what could be wrong, I am open to any guesses/hints at
debugging it.

Best regards,

On Tuesday 09 July 2002 01:14 am, Wolfgang Denk wrote:
> In message <200207082127.16518.ADharankar at ATTBI.Com> you wrote:
> > This question is common to both ppcboot and ppc-linux.
> > The ppcboot I am using is 1.1.5 and Linux kernel 2.4.18.
> >
> > If there is no console connected to the serial console port,
> > is it true that a thread sending output to it hangs? If this is
> No, this is NOT true.
> Why should it? There is no flow control used - neither in the PPCBoot
> nor in the Linux UART drivers...
> > I have a MPC8260ADS based board, and see the above
> least not in the standard MPC8xx and MPC8260 UART drivers.
> > behavior under ppcboot. Under Linux using a BDI debugger
> > the thread sending output to the console hangs. Perhaps
> You must be doing something wrong.
> Wolfgang Denk

** Sent via the linuxppc-embedded mail list. See

More information about the Linuxppc-embedded mailing list