busybox output to lcd display
Denys Vlasenko
vda.linux at googlemail.com
Sun Nov 23 14:20:47 UTC 2008
On Saturday 22 November 2008 19:56, Sudipta GHOSH wrote:
> What I am missing or any info you want?
>
> In my development board, I use uboot as boot loader.
> busybox files are in flash.
> when I boot , I can see the boot logo (peguin) in the lcd display and
> all "printk" output.
>
> But I am unable to see the busybox in the lcd display.
This is the confusing part. It's unclear what do you mean by
"unable to see the busybox [output]". There is no "busybox"
output per se, you can only see some output if some program
(be it busybox applet or not) outputs something.
So, you need to tell us _which_ busybox applet do you run
and see its output on the wrong device, and from where and how
(what command line parameters etc) do you run it.
> busybox prompt and all output from busybox is going to the serial port.
> Like if I do ls, then I see the output of "ls" in my serial port
> (teraterm/hyper terminal).
I assume this actually means "shell prompt and everything
I type in is seen on serial console".
> How I can see busybox prompt and all output to my lcd display.
By finding out where shell (which is most likely a busybox applet)
is started, and what tty is given to it. Then fix tty name there.
> I use console=tty0 in the bootargs.
I assume you mean "I have 'console=tty0' on kernel command line".
This merely makes your /dev/console be the same as /dev/tty0
(as opposed to, say, serial console /dev/ttyS0).
If your shell is given different tty to be on, kernel parameter
does not matter.
For example, if shell is started by init using /dev/inittab
line like this:
ttyS0::respawn:/bin/ash
it will be on ttyS0.
--
vda
More information about the busybox
mailing list