Hello, I have come up with a strange problem. I am running an application on my mini2440(Linux) which uses its one of the serial ports. But the communication stops after certain amount of data has been communicated. I tried all the serial ports (ttySAC0, ttySAC1, ttySAC2). But same thing happened. When I used USB port (converted to serial (ttyUSB0)using serial to usb converter) on mini2440, the same application worked fine. Is there any problem with serial ports...?
serial ports does not work
Using serial ports, the application stops at a particular stage when fixed amount of data has been communicated (say 1kb). No such problem with ttyUSB0.. I have to use serial port only.. Kernel- 2.6.32.2 rootfs - root_qtopia
Sounds familiar, but think it was quite awhile on this or another mini2440 forum. Lots of hits on <serial port not working> here and a few more interesting ones at: http://groups.google.com/group/mini2440/search?group=mini2440&q=seri... Good luck
1kb is not a huge amount of data. About 1 second at 9600 baud. Think there were some issues on really BIG files and transferring files in some unusual format. Try searching these forums as well: http://billforums.station51.net/ http://groups.google.com/group/mini2440
hii, m using tiny6410,n default linux os...m not able to understand y my data is nt being receive by serial port 0f friendly arm.. it transmit d data to my PC..n gives n error [root@FriendlyARM /]# efdgfdgfgf -/bin/sh: efdgfdgfgf: not found when i feed d data from PC on terminal can suggest some solution?? thnakz
@orbit: can you please explain more precise what you are doing, and what you want your Tiny6410 to do? What data do you want to exchange via the serial line. > [root@FriendlyARM /]# efdgfdgfgf > -/bin/sh: efdgfdgfgf: not found If you have typed the "efdgfdgfgf" string at your host's serial terminal everything seems okay. The shell at your Tiny6410 responds correctly with an error message, due to it tries to run the program "efdgfdgfgf" which does not exitsts on your Tiny6410. What do you expect instead?