From: prashant s. <pra...@ya...> - 2007-02-03 10:19:06
|
hello to all of you, this is my first mail to his group. I am quite new to player, and I am trying to run player on ARM board. I have ported player-2.0.3 with linux 2.4.19 on the arm board. i am trying to move pioneer with player ported on this board. when i tried with same version complied on my PC, it worked fine. now when i run player pioneer.cfg along with sonarobstacleavoid in example/libplayerc++/ folder, it gives following errors. 1. on player console it gives: #player pioneer.cfg * Part of the Player/Stage/Gazebo Project [http://playerstage.sourceforge.net]. * Copyright (C) 2000 - 2006 Brian Gerkey, Richard Vaughan, Andrew Howard, * Nate Koenig, and contributors. Released under the GNU General Public License. * Player comes with ABSOLUTELY NO WARRANTY. This is free software, and you * are welcome to redistribute it under certain conditions; see COPYING * for details. Listening on ports: 6665 accepted client 0 on port 6665, fd 5 P2OS connection opening serial port /dev/ttyS0...P2OS::Setup():tcgetattr():: Input/output error P2OS connection opening serial port /dev/ttyS0...P2OS::Setup():tcgetattr():: Input/output error closing connection to client 0 on port 6665 Quitting. # 2. on " sonarobstacleavoid" console it gives: #./sonarobstacleavoid calling connect done localhost: 6665 playerc error : timed out waiting for server reply to request 4:0:3:2 playerc error : poll call failed with error [2:No such file or directory] playerc error : recv failed with error [No such file or directory] warning : failed to reconnect playerc warning : warning : no socket to write to playerc warning : warning : no socket to write to playerc error : close failed with error [Bad file descriptor] PlayerClient::Read()(-1) : recv failed with error [No such file or directory] # one thing i want to mention here. I have only one serial port available. so primarily i use this port to communicate with host PC through minicom, because the bootloader require certain inputs while booting up. once the board is boot up, i disconnect minicom, remove the serial cable and attach it to pioneer. in communicating with minicom and pioneer, /dev/ttyS0 is used. kindly tell me where may be the problem. is it due to communication of both applications access /dev/ttyS0. if this is the case, then how should i proceed further. Kindly suggest me a solution . I'll be highly oblized and thankfull to all of you. with warm regards Prashant Sangal --------------------------------- Heres a new way to find what you're looking for - Yahoo! Answers |