[FE training-materials-updates] ttyUSB1 replaced by ttyUSB0

[Gregory CLEMENT]

On 10/04/2012 06:56 AM, Michael Opdenacker wrote:
> Repository : git://git.free-electrons.com/training-materials.git
> 
> On branch  : master
> Link       : http://git.free-electrons.com/training-materials/commit/?id=2416f07853b4c74739c948b6c001b0da084b15c8
> 
>> ---------------------------------------------------------------
> 
> commit 2416f07853b4c74739c948b6c001b0da084b15c8
> Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
> Date:   Thu Oct 4 05:23:39 2012 +0200
> 
>     ttyUSB1 replaced by ttyUSB0
>     
>     - We only see /dev/ttyUSB0 now
>       Only one port appears when plugging the Calao board

Ah bon?
Moi j'avais toujours le /dev/ttyUSB1 et c'est celui là que je devais
utiliser il me semble.
Pourtant j'étais bien en 12.04.

> 
> 
>> ---------------------------------------------------------------
> 
> 2416f07853b4c74739c948b6c001b0da084b15c8
>  .../kernel-module-environment.tex                  |   11 ++++-------
>  .../kernel-serial-interrupt.tex                    |    4 ++--
>  labs/kernel-serial-output/kernel-serial-output.tex |    2 +-
>  3 files changed, 7 insertions(+), 10 deletions(-)
> 
> diff --git a/labs/kernel-module-environment/kernel-module-environment.tex b/labs/kernel-module-environment/kernel-module-environment.tex
> index 11fbda5..02e01dc 100644
> --- a/labs/kernel-module-environment/kernel-module-environment.tex
> +++ b/labs/kernel-module-environment/kernel-module-environment.tex
> @@ -118,11 +118,8 @@ errors disappear.
>  \section{Setting up serial communication with the board}
>  
>  Plug the Calao board on your computer using its USB-A connector. When
> -plugged-in, two serial ports should appear, \code{/dev/ttyUSB0} and
> -\code{/dev/ttyUSB1}. \code{/dev/ttyUSB0} is used for the JTAG while
> -\code{/dev/ttyUSB1} corresponds to the {\em DBGU}, the debugging
> -serial port of the AT91 processor. You can also see this device appear
> -by looking at the output of \code{dmesg}.
> +plugged-in, a new serial ports should appear: \code{/dev/ttyUSB0}.
> +You can also see this device appear by looking at the output of \code{dmesg}.
>  
>  To communicate with the board through the serial port, install a serial communication program, such as \code{picocom}:
>  
> @@ -130,8 +127,8 @@ To communicate with the board through the serial port, install a serial communic
>  sudo apt-get install picocom
>  \end{verbatim}
>  
> -Run \code{picocom -b 115200 /dev/ttyUSB1}, to start a serial
> -communication on \code{/dev/ttyUSB1}, with a baudrate of \code{115200}. If
> +Run \code{picocom -b 115200 /dev/ttyUSB0}, to start a serial
> +communication on \code{/dev/ttyUSB0}, with a baudrate of \code{115200}. If
>  you wish to exit \code{picocom}, press \code{[Ctrl][a]} followed by
>  \code{[Ctrl][x]}.
>  
> diff --git a/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex b/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex
> index af997a7..2ebb2b1 100644
> --- a/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex
> +++ b/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex
> @@ -73,7 +73,7 @@ message.
>  Compile and load your driver. Have a look at the kernel messages. You
>  should no longer be flooded with interrupt messages.
>  
> -Start \code{picocom} on \code{/dev/ttyUSB1}. Press one character (nothing will
> +Start \code{picocom} on \code{/dev/ttyUSB0}. Press one character (nothing will
>  appear since the target system is not echoing back what we're
>  typing). Then, in the kernel log, you should see the message of our
>  interrupt handler. If not, check your code once again and ask your
> @@ -96,7 +96,7 @@ character.
>  For each received character, print a message containing the character.
>  Compile and load your driver.
>  
> -From \code{picocom} on \code{/dev/ttyUSB1} on the host, send characters
> +From \code{picocom} on \code{/dev/ttyUSB0} on the host, send characters
>  to the target. The kernel messages on the target should properly tell
>  you which characters are being received.
>  
> diff --git a/labs/kernel-serial-output/kernel-serial-output.tex b/labs/kernel-serial-output/kernel-serial-output.tex
> index 358683c..78aa8f1 100644
> --- a/labs/kernel-serial-output/kernel-serial-output.tex
> +++ b/labs/kernel-serial-output/kernel-serial-output.tex
> @@ -43,7 +43,7 @@ echo "test" > /dev/serial
>  \end{verbatim}
>  
>  The \code{test} string should appear on the remote side (i.e in
> -the \code{picocom} process connected to \code{/dev/ttyUSB1}).
> +the \code{picocom} process connected to \code{/dev/ttyUSB0}).
>  
>  You'll quickly discover than newlines do not work properly. To fix
>  this, when the userspace application sends \verb+"\n"+, you must send
> 
> _______________________________________________
> training-materials-updates mailing list
> training-materials-updates at lists.free-electrons.com
> http://lists.free-electrons.com/mailman/listinfo/training-materials-updates
> 


-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com