Merge lp:~stylesen/lava-project/device-connect-method-doc into lp:lava-project

[Senthil Kumaran S]

Add different connection methods, to connect to the device serial port.

[Andy Doan (doanac)]

I think I might collapse the method 3 part about "screen" into method 1. Something like:

In some cases cu on Ubuntu has shown issues sending STDIN to the target. In this case GNU screen is an alternative::

  sudo screen -t 'ttyUSB0 115200 8n1' /dev/ttyUSB0 115200,-ixoff,-ixon

[lp:~stylesen/lava-project/device-connect-method-doc]

45. By Senthil Kumaran S on 2012-12-04

Merge connect method 3 with method 1 as per doanac's comment.

[Senthil Kumaran S (stylesen)]

Hi Andy,

On Tuesday 04 December 2012 09:21 PM, Andy Doan wrote:
> I think I might collapse the method 3 part about "screen" into method 1. Something like:
>
> In some cases cu on Ubuntu has shown issues sending STDIN to the target. In this case GNU screen is an alternative::
>
> sudo screen -t 'ttyUSB0 115200 8n1' /dev/ttyUSB0 115200,-ixoff,-ixon

Made the above change to the documentation.

Thank You.
--
Senthil Kumaran S
http://www.stylesen.org/
http://www.sasenthilkumaran.com/

[Andy Doan (doanac)]

On 12/04/2012 10:56 AM, Senthil Kumaran S wrote:
> Hi Andy,
>
> On Tuesday 04 December 2012 09:21 PM, Andy Doan wrote:
>> I think I might collapse the method 3 part about "screen" into method 1. Something like:
>>
>> In some cases cu on Ubuntu has shown issues sending STDIN to the target. In this case GNU screen is an alternative::
>>
>> sudo screen -t 'ttyUSB0 115200 8n1' /dev/ttyUSB0 115200,-ixoff,-ixon
>
> Made the above change to the documentation.

Merge it! thanks

=== modified file 'doc/lava-image-creation.rst'
--- doc/lava-image-creation.rst	2012-11-28 17:16:04 +0000
+++ doc/lava-image-creation.rst	2012-12-04 16:55:26 +0000
@@ -48,15 +48,57 @@
 
 LAVA needs to know about your particular device. However, before adding the
 device to LAVA, you need to work out how you want connect to the device and
-provide that command to the dispatcher.
+provide that command to the dispatcher. There are different ways to
+connect to the device which are as follows:
 
-The easiest way to do this if you have a direct serial connection to the device
-is with "cu". Here's an example command:
+*Method 1:* The easiest way to do this is, if you have a direct serial
+connection to the device then you can use "cu". Here's an example
+command (the following command assumes "cu" is already installed in
+your machine):
 
 ::
 
     sg dialout "cu -l /dev/ttyUSB<X> -s 115200"
 
+In some cases "cu" on Ubuntu has shown issues sending STDIN to the
+target. In this case GNU screen is an alternative (the following
+command assumes "screen" is already installed in your machine):
+
+::
+
+   sudo screen -t 'ttyUSB0 115200 8n1' /dev/ttyUSB0 115200,-ixoff,-ixon
+
+*Method 2:* The next method to connect to the board is to use ser2net. It
+provides a convenient way which allows you to 'telnet' into your board
+over a serial link. After connecting your board, let us assume your
+board appears as "/dev/ttyUSB0".
+
+::
+
+    sudo apt-get install ser2net
+
+Edit /etc/ser2net.conf and add this line:
+
+::
+
+    2000:telnet:600:/dev/ttyUSB0:115200 8DATABITS NONE 1STOPBIT banner
+
+Then restart so that ser2net sees your changes:
+
+::
+
+    sudo /etc/init.d/ser2net restart
+
+You can now connect to the board with:
+
+::
+
+    telnet localhost 2000
+
+The advantage of connecting with ser2net is that, your device/board is
+available from the connected host machine IP to the entire network at
+port 2000 or any port that is specified in the config file.
+
 Once you have a good way of connecting to the device, you need to tell LAVA
 about it in two places:
 
@@ -89,7 +131,8 @@
 .. _here: http://bazaar.launchpad.net/~linaro-validation/lava-dispatcher/trunk/files/head:/lava_dispatcher/default-config/lava-dispatcher/device-types/
 
 The critical piece that ties the dispatcher to the connection information
-described above is the "connection_command" setting.
+described above is the "connection_command" setting. Based on the
+connection method you have chosen above your "connection_command" will vary.
 
 Adding to the scheduler
 -----------------------