Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am running an Open suse 10.2 in my system...and my minicom version is 2.2..
i am connecting my serial port to my targets serial port..
As soon my target is booted, i can see the bootup text messages on my minicom screen...But what ever i type on the minicom screen, i could not get it on the screen..
I tried Local echo ON, then some how i could get what i typed on the screen, but my board is not responding to my input...the same board works well with the minicom 2.0 installed on an Red Hat enterprise Linux..
All the setting and baud rate are Ok...
Is there any tweaking i should do to make it work??
Have you ruled out a hardware failure on the SUSE system? If the TX lines were damaged, then you would only be able to see the output from the device and not send anything to it.
It could also be a permissions issue, where you have read but not write permissions to /dev/ttyS0. You may want to try running minicom as root to see if that fixes the issue (if you have not already). If it works under the root account, then you need to modify the permissions on the device, or put your user into the appropriate group(s).
My serial cable is working properly...This i checked by connecting my target board through the same serial cable to another computer,where the minicom is working properly... so serial cable is not faulty...
I tried starting the minicom as root...then also the problem is persists...
What MS3FGX said might apply to the serial port hardware itself as well. Make a connector with pins 2 and 3 shorted as a test device and connect that to the serial port of the PC.
Start minicom and type something, it should echo what is transmitted (if local echo is on, you should see it twice).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.