[Buildroot] can not open ttyUSB0

[Buildroot] can not open ttyUSB0

[Adeel Nafis]

Dear All,
I have a kit2416 (http://www.armdesigner.com/KIT2416.html) module with 
Samsung ARM926EJS*. *I have configured buildroot with static device 
table, and added the ttyUSB0,1,2,3 to with major 188 and minor 0,1,2,3 
to the file.
I also added the line to /etc/fstab

none    /dev/bus/usb    usbfs    defaults,devmode=0666    0    0

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.

If I do `cat /dev/bus/usb/devices` output is
# cat /dev/bus/usb/devices

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 2.06
S:  Manufacturer=Linux 2.6.21.5-cfs-v19 ohci_hcd
S:  Product=S3C24XX OHCI
S:  SerialNumber=s3c24xx
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=12d1 ProdID=1446 Rev= 0.00
S:  Manufacturer=HUAWEI Technology
S:  Product=HUAWEI Mobile
S:  SerialNumber=1234567890ABCDEF
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=01(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms


Any pointers?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130130/138bf6e6/attachment.html>

[Buildroot] can not open ttyUSB0

[Thomas Petazzoni]

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

[Buildroot] can not open ttyUSB0

[Adeel Nafis]

From: Thomas Petazzoni<thomas.petazzoni@free-electrons.com>
To: Adeel Nafis<adeel@linkwisetech.com>
Cc:buildroot at busybox.net
Subject: Re: [Buildroot] can not open ttyUSB0
Message-ID: <20130130093112.73034ecd@skate>
Content-Type: text/plain; charset=US-ASCII

> 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.
Thanks,
the listing from dmesg does indicate the first detection and not the 
subsequent mode switching or connection to the ttyUSB0 of the modem

usb 1-1: new full speed USB device using s3c2410-ohci and address 4
usb 1-1: configuration #1 chosen from 1 choice
scsi4 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
scsi5 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
mmc0: starting CMD25 arg 00360d30 flags 00000035
mmc0: req done (CMD25): 0/0/0: 00000900 00000000 00000000 00000000
mmc0: starting CMD13 arg e6240000 flags 00000015
mmc0: req done (CMD13): 0/0/0: 00000900 00000000 00000000 00000000
mmc0: starting CMD25 arg 00360d48 flags 00000035
mmc0: req done (CMD25): 0/0/0: 00000900 00000000 00000000 00000000
mmc0: starting CMD13 arg e6240000 flags 00000015
mmc0: req done (CMD13): 0/0/0: 00000900 00000000 00000000 00000000
scsi 4:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
scsi 5:0:0:0: Direct-Access     HUAWEI   MMC Storage      2.31 PQ: 0 ANSI: 2
usb-storage: device scan complete
sd 5:0:0:0: Attached scsi removable disk sda
usb-storage: device scan complete

there is no symlink for /sys/class/tty/ttyUSB0, so I guess this 
indicates that there is a missing driver, but which one? I have also 
tried doing the following

modprobe usbserial vendor=0x12d1 product=0x1446

but it makes no difference.

-- 
Adeel Ahmed Nafis
Design Engineer
LINKWISE TECHNOLOGY PTE LTD
Blk 3 Ang Mo Kio Industrial Park 2A
#06-08, AMK TECH 1
Singapore 568050

[Buildroot] can not open ttyUSB0

[Gustavo Zacarias]

On 01/30/2013 05:59 AM, Adeel Nafis wrote:

> scsi 4:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0
> ANSI: 2
> scsi 5:0:0:0: Direct-Access     HUAWEI   MMC Storage      2.31 PQ: 0
> ANSI: 2
> usb-storage: device scan complete
> sd 5:0:0:0: Attached scsi removable disk sda
> usb-storage: device scan complete
> 
> there is no symlink for /sys/class/tty/ttyUSB0, so I guess this
> indicates that there is a missing driver, but which one? I have also
> tried doing the following
> 
> modprobe usbserial vendor=0x12d1 product=0x1446
> 
> but it makes no difference.

Huawei modems usually require the "option" module in the kernel
(CONFIG_USB_SERIAL_OPTION). Do you have it enabled and loaded?
Regards.

[Buildroot] can not open ttyUSB0

[Stefan Fröberg]

Hi Adeel

30.1.2013 8:27, Adeel Nafis kirjoitti:
> Dear All,
> I have a kit2416 (http://www.armdesigner.com/KIT2416.html) module with
> Samsung ARM926EJS*. *I have configured buildroot with static device
> table, and added the ttyUSB0,1,2,3 to with major 188 and minor 0,1,2,3
> to the file.
> I also added the line to /etc/fstab
>
> none    /dev/bus/usb    usbfs    defaults,devmode=0666    0    0
>
> 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.
>
> If I do `cat /dev/bus/usb/devices` output is
> # cat /dev/bus/usb/devices
>
> T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
> B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
> D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
> P:  Vendor=0000 ProdID=0000 Rev= 2.06
> S:  Manufacturer=Linux 2.6.21.5-cfs-v19 ohci_hcd
> S:  Product=S3C24XX OHCI
> S:  SerialNumber=s3c24xx
> C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
> I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
> E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms
>
> T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
> D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
> P:  Vendor=12d1 ProdID=1446 Rev= 0.00
> S:  Manufacturer=HUAWEI Technology
> S:  Product=HUAWEI Mobile
> S:  SerialNumber=1234567890ABCDEF
> C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA
> I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
> E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> E:  Ad=01(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> I:* If#= 1 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
> E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
> E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
>
>
> Any pointers?
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

If I remember correctly those Huawei modems (I had one once) detect
allright at the boot but then they switch to usb storage because all(?)
3G modems have some memory reserved
to work as regular USB stick (all "CD-ROM" in windows).

So it might be that your modem detected ok at boot but then immediately
switched to that storage mode and you have to switch it back by playing
with usb_modeswitch
command parameters.

There is a meniton of that in "Troubleshooting, Kernel related issues"
in usb_modeswitch makers pages:

http://www.draisberghof.de/usb_modeswitch/#trouble

Regards
Stefan



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130130/2f989222/attachment.html>