From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monstr-eu.20150623.gappssmtp.com; s=20150623; h=reply-to:subject:references:to:from:message-id:date:user-agent :mime-version:in-reply-to; bh=O1nevKUERq9gQl2WexDZ3Uod+3L0+BwYDtpTsDoe+gA=; b=rYq81AZqnyPwcgGN1JALfSrunyaFR99fZlnZiCnnTDtOYn9ponDP+DNZov5lJoMJak 5FU7VfFn3fifPJ+IVGa7eUwKYbd8n1TCQ4hBISMZ8ArxzKTSs+sn0RwAd17GC+JPMzOA HwhEimUBnFreOonx5Cwtamo5O/wgSQOBujVKRK2QLqD7j9epH9wpUUlnmivWBS0bNmIC hhS/LGXO8LCVAQgRAV7JlAoX4becGFpDaIUg/0JpuEvH04dcJP1wn7FEHNXTeU5UPiFp cie294xixYoQ6fTnetpbloAF00WxXCdtCsOfeodj/JHR7UOxBnpNV6cNDJq2Rbs7w73v ocOg== Reply-To: monstr@monstr.eu References: <00467eb7-31d8-baff-8b12-f1175712fcac@monstr.eu> <58EEBBC2.5020403@gmail.com> From: Michal Simek Message-ID: <73842e0e-cd2e-234c-2324-2f5a30c559e6@monstr.eu> Date: Thu, 13 Apr 2017 07:05:50 +0200 MIME-Version: 1.0 In-Reply-To: <58EEBBC2.5020403@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xpaMXGubvrhK1UbNwEg5gMUwc9IxUrPqF" Subject: Re: [Fuego] Board setup List-Id: Mailing list for the Fuego test framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Frank Rowand , "Bird, Timothy" , "fuego@lists.linuxfoundation.org" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --xpaMXGubvrhK1UbNwEg5gMUwc9IxUrPqF Content-Type: multipart/mixed; boundary="6a0IiIO7TvtHLXhMgPLbdsUe64lamB70v"; protected-headers="v1" From: Michal Simek Reply-To: monstr@monstr.eu To: Frank Rowand , "Bird, Timothy" , "fuego@lists.linuxfoundation.org" Message-ID: <73842e0e-cd2e-234c-2324-2f5a30c559e6@monstr.eu> Subject: Re: [Fuego] Board setup References: <00467eb7-31d8-baff-8b12-f1175712fcac@monstr.eu> <58EEBBC2.5020403@gmail.com> In-Reply-To: <58EEBBC2.5020403@gmail.com> --6a0IiIO7TvtHLXhMgPLbdsUe64lamB70v Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 13.4.2017 01:44, Frank Rowand wrote: > On 04/12/17 02:22, Michal Simek wrote: >> On 11.4.2017 20:25, Bird, Timothy wrote: >>>> -----Original Message----- >>>> From: Michal Simek on Tuesday, April 11, 2017 2:18 AM >=20 > < snip > >=20 >>>> Also default docker is not supporting /dev/serial/* which is elegant= way >>>> how to handle connecting to multiple boards connected to one PC. >>>> >>>> Because what you need to really do is to connect to board via this l= ink >>>> SERIAL=3D"/dev/serial/by-path/pci-0000:00:1d.0-usb-0:1.7.1.2.4.4:1.0= -port0" >>>> instead of just >>>> SERIAL=3D"/dev/ttyUSB10" >>>> which is changing all the time. >>>> >>>> Do you know what to do? >>> We have a separate "docker-create-container" script for handling port= s >>> that docker needs permission to, and that can change dynamically >>> on the host at runtime. It is called >>> docker-create-usb-privileged-container.sh, and it's in the fuego/fueg= o-host-scripts >>> directory. It makes certain device nodes on the host available insid= e the target. >>> >>> I don't have experience with /dev/serial/by-path, but what this scrip= t >>> does is volume-mount certain directories from the host into the conta= iner filesystem. >>> Maybe it would work to add a line like the following to this script: >>> >>> -v /dev/serial/by-path:/dev/serial/by-path \ >>> >>> and use that script to create the container. >> >> This is working but the problem is with sercp which reports >> ERROR: Port must be configured before it can be used. >> >> sersh is fine with this serial setup >> >> SERIAL=3D"/dev/serial/by-path/pci-0000:00:1d.0-usb-0:1.7.1.2.4.4:1.0-p= ort0" >> >> Both are pointing to the same file that's why I expect that issue is t= here. >> >> In serio.git there is >> 9daaf498e0fc4a086fd50e32c2edd3d7410d47ae >> >> You have this in commit message. >> You can _not_ use /dev/ttyACM0 for host1 and host2 because the '/'= >> before a ':' is how scp determines that you are trying to copy >> a file with a ':' in the name instead of specifying a host name. >> >> Frank: Can you please comment? >=20 > < snip > >=20 > The command line syntax of sercp is based on the command line syntax > of scp, so that sercp can (mostly) be a drop in replacement for scp. >=20 > From 'man scp': >=20 > File names may contain a user and host specification to indicate t= hat the > file is to be copied to/from that host. Local file names can be m= ade > explicit using absolute or relative pathnames to avoid scp treatin= g file > names containing ':' as host specifiers. >=20 > There is a slight impedence mismatch between scp and sercp since scp > refers to network hosts and sercp refers to serial devices. >=20 > Since '/' is not allowed in a sercp host name, sercp expects host to be= a > serial device located in /dev/. >=20 > sersh also expects host to be a serial device located in /dev/. And > 'sersh -h' documents host in this manner. But the host parsing code > for sersh does not prefix the host name with '/dev/' if there are > any slashes in the host name. Allowing a slash in a sersh host name > is an artifact that crept into sersh. slash is not a valid character > in a host name and sersh should be updated to not allow the slash. I understand your statement. Then I think fuego should help to workaround this. Because if you work with several similar boards you have no idea which one it is and ttyUSBx assignment is done at run time and it is not stable. Only path to certain port is the same all the time. Also with one flaky usb cable this is not going to work. Thanks, Michal --=20 Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91 w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel - Xilinx Microblaze Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs --6a0IiIO7TvtHLXhMgPLbdsUe64lamB70v-- --xpaMXGubvrhK1UbNwEg5gMUwc9IxUrPqF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAljvBy4ACgkQykllyylKDCH+kwCfWd7RGfGWqPacX3Xukg2NmcbT k7wAn1/XC7V6cK5nhDTqTVwDw2aK0MGb =1uZI -----END PGP SIGNATURE----- --xpaMXGubvrhK1UbNwEg5gMUwc9IxUrPqF--