I’m using minicom to connect through a serial link to a target (UART link of a sparc processor).
With gtkterm or cutecom, I can connect, read and send characters. The only issue with them is that they both insert empty lines after each LF character, and :
-gtkterm cannot record output to a file
-cutecom does not "flush" after recording output to a file (it gets delayed, and flushed only after every 16k bunch of data)
Minicom, which is console based, would solve these problems (and it does not insert empty lines…), but I still cannot send any character with it, and don’t understand why!
When I press a key (for example, "0" + Return), is is written (if I enable local echoing), but nothing happens (while it works with gtkterm and cuteterm!!).
In my program, I read using the following :
r = scanf("%d", &option);
Using a debugger, I see that the program never goes past this line…
Has anybody any idea?
Local echo says nothing about what goes over the wire. It can also be something with how scanf() interprets newlines. Try to create a program with getchar() and see if that gets any input at all, especially what happens when you press enter in the different terminal emulators.
Check that all baud rate, etc settings are set correctly in minicom. Check out the command line parameters for minicom, this way you can specify options directly.