Not able to see the usb device instance in minicom for uclinux target

Hello,
I am new to this post,Currently I am working on a target for which I need to connect a usb keyboard and should be able to input on the console of the device.The details are:
Target board:uclinux for coldfire processor.

when I connect through the serial port and see the filesystem through minicom,I couldnot see the usbdevice instance in /dev of uclinux but there are messages of connection and disconnection(drivers are available in uclinux for the keyboard).I have to input through the keyboard.Can anyone plz help me in approaching the issue.

I will rephrase your question to make sure I understand it correctly.
You have a ucLinux based board with a USB-attached keyboard. The ucLinux based board also has a serial port which you can use to login from a serial terminal of some sort (minicom running on some other host). You want to be able to use the USB keyboard as the standard input component of your serial login?
In order to do this, I think you will have to craft your own getty process that switches its standard input upon completion of the login process. You would probably want to start by writing some code to open and read the keyboard as a device, reading from /dev/whatever_the_USB_keyboard_is. Once you understand how the keyboard sends its data, you can build this into your_getty.
--- rod.

Yes you are right.But "You want to be able to use the USB keyboard as the standard input component of your serial login?" this is not right.I have to input through the keyboard to the device it is attached.Basically it has two processors and one is running uclinux kernel and the other is running the bootloader and UI of the device so that we can input our data into it.Here I can see the dmesg messages showing drivers are installed.

Current status: I can input the characters through the keyboard seen on the minicom terminal.Now I have to capture the characters going to terminal and place them on the GUI specific fields on the device.That is I have to communicate from one processor to another processor.

Okay, your description seems to have some holes. A processor running a bootloader? To boot what?
Are you saying that you have a whole separate CPU that is reading the USB keyboard and writing to the 'GUI'? If I understand this correctly, you essentially have a CPU of some sort that is performing the function of a terminal. It uses a USB keyboard and some kind of display device. What physical connection is there between this second device and your coldfire ucLinux host? Is this second CPU also running Linux?

--- rod.