Thread (4 messages) flat view 4 messages, 2 authors, 2011-01-20

Re: Problem with Busybox shell

From: MohanReddy koppula <hidden>
Date: 2011-01-19 05:06:04

But, if there is any problem with cable I could not have seen any
character in the interrupt routine of the driver. I turned off both
software and hardware flow control as by board doesn't have hardware
flow control. tty_read is called and it hangs at ldisc->read. And I
see that data is put into the tty buffer by the driver. Will there be
any problem with copy_to_user() if there is some problem in the
memory?

Thanks,
Mohan

On Tue, Jan 18, 2011 at 12:55 PM, Nicholas Mc Guire [off-list ref] wrote:
On Tue, 18 Jan 2011, MohanReddy koppula wrote:
quoted
Hi All,

I am working on an MPC885 based custom board. I am able to boot up the
linux (linux-2.6.33.7). I could see busybox shell (ash) prompt. But it
is not accepting any inputs, I am not able to enter any command, it
just hangs there. I am using ttyCPM0 terminal.

I suspected if there was any problem in CPM driver interrupts
generation and put some printk's in the interrupt handler and could
see interrupts are raised and data is read, but shell is not taking
the input.

I wrote an init.c and opened the ttyCPM0 and tried to read from it,
but couldn't. I am able to write to ttyCPM0 and see it on the host
minicom.
if you are using minicom to connect check if you have hardware/software flow
control turned on - it also could be a cabling problem - had this with the
beagle board where the tx line was on the wrong pin - so I got output but
could not get any response to input.

hofrat
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help