From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Jawad Hassan <jawad@emblemtechnologies.com>
Cc: yocto@yoctoproject.org
Subject: Re: TtyUsb Yocto Issue
Date: Tue, 08 Oct 2013 17:04:10 +0100 [thread overview]
Message-ID: <1801165.6ZCs8TucHi@helios> (raw)
In-Reply-To: <CAPhCmJrN9fEaainDVW70A1NSZA3c+oTb-fsx4_CkDJQ0qqdS-Q@mail.gmail.com>
Hi Jawad,
On Tuesday 08 October 2013 06:43:18 Jawad Hassan wrote:
> We're trying to access the USB serial port using rxtx on a java application
> on Yocto. The problem is that we're unable to list out any ports on the
> Nitrogen Lite board, we think this could be a permissions issue, if anyone
> has been able to do this or any resources that can help us in getting this
> done.
It's hard to say for sure without further details, but assuming the device
nodes actually exist in /dev and it's a typical device permissions issue there
are two options:
1) Look at the /dev/ttyUSB* device nodes that exist and see if there is
already a group assigned with write access; if so you just need to ensure the
user you are running as is a member of that group.
2) Create a udev rule to set the device permissions correctly. This would be a
matter of creating a recipe to install an extra file to /etc/udev/rules.d that
assigned the desired permissions. There are lots of HOWTOs out there on the
web for this, e.g.:
http://sourceforge.net/apps/mediawiki/gizmod/index.php?title=HOWTO_-_Setting_Input_Device_Permissions_-_Creating_a_udev_Rule
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-10-08 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 13:43 TtyUsb Yocto Issue Jawad Hassan
2013-10-08 16:04 ` Paul Eggleton [this message]
2013-10-09 12:36 ` Jawad Hassan
2013-10-09 12:44 ` Jawad Hassan
2013-10-09 12:45 ` Jawad Hassan
2013-10-09 13:07 ` Paul Eggleton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1801165.6ZCs8TucHi@helios \
--to=paul.eggleton@linux.intel.com \
--cc=jawad@emblemtechnologies.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.