The shortest possible answer to your question is to tell you to install
minicom as well
as UUCP (the thing that gives you cu).
From minicom, hit Ctrl A-Z and you get this screen:
Code:
Minicom Command Summary |
OPTIO| |
Compi| Commands can be called by CTRL-A <key> |
Port | |
| Main Functions Other Functions |
| |
| Dialing directory..D run script (Go)....G | Clear Screen.......C |
| Send files.........S Receive files......R | cOnfigure Minicom..O |
| comm Parameters....P Add linefeed.......A | Suspend minicom....J |
| Capture on/off.....L Hangup.............H | eXit and reset.....X |
| send break.........F initialize Modem...M | Quit with no reset.Q |
| Terminal settings..T run Kermit.........K | Cursor key mode....I |
| lineWrap on/off....W local Echo on/off..E | Help screen........Z |
| Paste file.........Y | scroll Back........B |
| |
| Select function or press Enter for none. |
| |
| Written by Miquel van Smoorenburg 1991-1995 |
| Some additions by Jukka Lahtinen 1997-2000 |
| i18n by Arnaldo Carvalho de Melo 1998 |
+-------------------------------------------------------------------+
Minicom allows you to turn "local echo on" (E). That is why you are not seeing anything when
you type.
I cannot tell you exactly what your problem is but I can shine some light that ought to let you solve it.
A terminal emulator allows you to send data over a serial port (every key you press gets sent) and then to recieve
replies over serial port from your target, which are decoded and appear on your screen.
The target you are using is not sending replies. When you type and "see nothing", you are probably still sending
commands to your target. You are only distressed that you can't see them. Your target probably
also has a
setting like "Echo On". If you turn it on in your target, then whenever you send a character (by typing) it will send
it back, and you will see it on your emulator. Until you figure out how to do this (and perhaps your target is
so dumb it does not have this feature) then you can use "Local Echo On" so that your terminal emulator (minicom)
shows what keystrokes it is sending.
We are all used to high-function systems that are full of illusions (like automatic echo of keys you press, and Windows and a mouse cursor,
the biggest illusion of all!) Your activity looks like firmware/hardware development.
There are no illusions here .... just hardware.
If you get a login screen on your target, try logging in, even though you don't "see" that you are typing anything.
If you login despite not seeing any text, then my explanation is correct. You are "sending" but the target is
not "echoing".