Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] can not open ttyUSB0
Date: Wed, 30 Jan 2013 09:31:12 +0100	[thread overview]
Message-ID: <20130130093112.73034ecd@skate> (raw)
In-Reply-To: <5108BD5B.3050001@linkwisetech.com>

Dear Adeel Nafis,

On Wed, 30 Jan 2013 11:27:39 +0500, Adeel Nafis wrote:
> After attaching a 3G Modem USB  I am able to successfully use 
> 'usb_modeswitch" and get the device to switch with messages indicating 
> that the device is connected to /dev/ttyUSB0,1,2. However, after this I 
> can not open the /dev/ttyUSBx any more. If i use gnokii for arm it 
> prints out some messages indicating that it failed to open the port.
> 
> Gnokii output
> GNOKII Version 0.6.26
> Gnokii serial_open: open: No such device        <----- the port here is 
> set to /dev/ttyUSB0
> Couldn't open ATBUS device: No such device
> Telephone interface init failed: Command failed.
> Quitting.
> Cannot unlock device.
> Command failed.
> 
> I have tested the thing out with Ubuntu for arm on the same platform and 
> can verify that it works.

Before trying to access the device through /dev, make sure that your
kernel has actually detected this device, and that a driver has been
bound to it:

 *) Check your dmesg to see if there is something related to your 3G
 modem and the creation of ttyUSB0

 *) Check /sys/class/tty/ and check if there is a ttyUSB0 symlink.
 Until there is no ttyUSB0 symlink, it means that the kernel hasn't
 detected the device, or that a driver is missing for it.

 *) Once you have /sys/class/tty/, do a cat /dev/class/tty/ttyUSB0/dev
 and check that the major/minor that you see here match the ones you
 have used in the static device table (but it seems like 188:0 is
 correct for ttyUSB0, so your problem is most likely due to the fact
 that the kernel has not detected the device at all).

Best regards,

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

  reply	other threads:[~2013-01-30  8:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.83813.1359524634.32592.buildroot@busybox.net>
2013-01-30  6:27 ` [Buildroot] can not open ttyUSB0 Adeel Nafis
2013-01-30  8:31   ` Thomas Petazzoni [this message]
2013-01-30 12:19   ` Stefan Fröberg
     [not found] <mailman.83869.1359534753.32592.buildroot@busybox.net>
2013-01-30  8:59 ` Adeel Nafis
2013-01-30 10:15   ` Gustavo Zacarias

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=20130130093112.73034ecd@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox