Deepankar Vidyarthi <deepankar@embeddedinfotech.com> writes: > Thanks for the response Ed, it has been helpful. > > I checked the communication both ways - its working fine. > But on the dev m/c if I do "cat", it does not wait long. You have to > give echo on test m/c as soon as possible, else it comes out of prompt. That doesn't sound quite right. My cat will wait until I hit control-c, getting all the stuff I direct into the serial port on the other host. > There is another test using minicom where I should see the message sent > by test kernel when it waits for connection with remote gdb at boot > time. Here I am not getting anything. Not sure why. > > One thing is my dev machine is RedHat 8.0 while target is Mandrake. > Could this be creating problems. I don't know, but while having different distros could possibly mean the serial ports currently have incompatible settings, you could always fix that. There are a lot of tips for troubleshooting serial connections in the serial HOWTO: http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Serial-HOWTO.html Good luck! -- --Ed L Cashin PGP public key: http://noserose.net/e/pgp/ -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
