Motorola W385 and p2k-core

[cavit8]

I've been struggling with accessing this phone for some time and have tried moto4lin, kmobiletools and now p2k.

Motorola W385 (a CDMA phone)
Linux: Zenwalk 5.0 running 2.6.23.12.  The cdc_acm module is installed.
p2kc ver 0.6, compiled from source.

Attaching the phone, and running "modprobe usbserial vendor=0x22b8 product=0x2b44" according to dmesg, the phone is on /dev/ttyUSB0  /dev/ttyUSB1.  Both locations pop up. Staring p2k-core as "p2k-core -v -m  /dev/ttyUSB0 as root seems to connect to the phone as it indicates that it's "_Found: Motorola W385" which repeats numerous times and ends at a command prompt.  However, I can't seem to get it to do anything at that point.  file l  or any other command appears to run the same connect sequence ending in a string of " _Found: Motorola W385"'s and a command prompt.

So it seems to be finding and recognizing the phone okay, I just don't seem to be able to do anything.  Running p2k-core without the modem (-m) option as root results in "!error: bulk write failed".

Any thoughts from anyone?

[s5vi]

Sorry to say that, this output dosent mean phone is connected.
I havent experience with CDMAs

option "-v" enforces to list all sub devices found
there must be "test command" sub device. to work with p2k interface

if p2k-core find the modem device, it try to switch p2k mode, then try to find test command sub device

I think the command to switch p2kmode is sent, and test command subdevice not found
In fact p2k mode command is "AT+MODE=8" which can send to phone modem device with minicom or similar app. So we can switch phone to p2kmode by hand also.

pl post output here.

Maybe usb IDs and subdevices different.
Pls enter this command:
USB_DEBUG=255 ./p2k-core -v m  /dev/ttyUSB0

To discover usb device details pls use "lsusb -v" as root

To log usb activity we can use kernel:
do this as root:
echo 1 > /sys/module/usbcore/usbfs_snoop
./p2k-core -m /dev/ttyUSB0
echo 0 > /sys/module/usbcore/usbfs_snoop
and post the tail of /var/log/message

Good luck

[cavit8]

Yes, I suspected it could detect the phone and couldn't connect with it. Thanks for your help, I know nothing about telephony. Here's the output from what you requested:

<<USB_DEBUG =255 ./p2k-core -v -m /dev/ttyUSB0>>
Search for Motorola USBLAN Interface.
_Found: Motorola W385
 Search for Motorola Test Command.
_Found: Motorola W385
 Modem mode, device: /dev/ttyUSB0
 Switching to P2kmode (cca. 2-3 sec)
_Sent  Data  0  1  2  3  4  5  6  7  8  9  A  B  C  D  E  F ASCII characters

    000000: 41 54 2b 4d 4f 44 45 3d 38 0d 0a                AT+MODE=8..
 Search for Motorola Test Command.
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device

_Found: Motorola W385
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device

last four lines re-iterate then goes to a command prompt.

<<lsusb -v>>
 
 
Bus 001 Device 002: ID 22b8:2b44 Motorola PCS
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x22b8 Motorola PCS
  idProduct          0x2b44
  bcdDevice            0.01
  iManufacturer           1 Motorola Inc.
  iProduct                2 Motorola W385
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           62
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xc0
      Self Powered
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              3 Motorola Communication Interface
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval             128
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              3 Motorola Communication Interface
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)

<usbfs_snoop output>>

I don't seem to be able to do this command.  My system architecture doesn't contain /sys/module/usbcore.  I'll enquire on the distro site to see if there is some equivalent to monitor usb activity. 

[s5vi]

lsusb -v was quite informative
I see 2 seub devices , both named "Motorola comm interface"
one has 3 enpoints IN: 0x81,0x82, OUT: 0x02
othes has 2 endpoint IN:0x84, OUT:0x04
interfaces are bulk type so this can be p2k05 protocol, except 0x81 endpoint

is phone in p2k mode?
what distribution do you use? This is an article about usbfs_snoop: http://www.linuxjournal.com/article/7582

ps: found this (moto4lin forum): http://ubuntuforums.org/archive/index.php/t-638509.html

[cavit8]

The phone appears to be in AT mode, at least according to moto4lin.  I'd seen the thread in modmymoto that you included and that was the first thing I tried. Using the vendor/product settings suggested has no effect. I can't seem to get the phone to switch to p2k mode. The only way I can get the phone to show as p2k in moto4lin is to enter erroeous AT mode vendor/product info, but I still can't connect.  Apparently this worked for someone in the forum but it doesn't seem to work for me.  I was starting to look at minicom as a means of switching the phone to p2k but got nervous as I'm not very experienced and sort of shooting in the dark here (also tried gnokii, bitpim, kmobiletools with no joy). 

My distro is Zenwalk 5.0, a paired down slackware essentially (www.zenwalk.org).  I've got a query on the forum board there with regard to monitoring activity via the kernel using usbfs_snoop or some equivalent as well as just connecting to the phone in general.  I found a couple of programs on sourceforge but they required older versions of gtk than I'm running and installing that stuff is pushing my tolerance for required mods.

I'll refocus my googling to look at switching the phone to p2k mod.  The ioctl error in the usb_debug command was recreated with another software package, but I can't recall which one. Looks like I need to start keeping a log :-)

Thanks for your suggestions to date.

[cavit8]

I haven't had a lot of success getting any further on this, unfortunately.  No joy in getting usb_fs or an equivalent going.

BIT-PIM detects the ports but tells me "These ports are active, but cannot be used because they are in use by another program or device driver, you do not have permissions to access them, or a device driver is required.

Further details

Property	Value	Description
PID	0x2B44	Product ID
VID	0x22B8	Vendor ID
active	True	Your operating system shows this driver and port is    correctly configured and a device attached
available	False	It was not possible to open this port
description
description	USB Device - Vendor Motorola PCS, Product #2B44, (Interface #00)	.
libusb	True	This indicates if the usb library is in use to access this device. Operating system device drivers (if any) are bypassed when BitPim talks to the device
name	usb::001::002::0	This is the name the port is known to your operating system as
protocol	Vendor Specific Class / Vendor Specific Subclass / Vendor Specific Protocol	This is the protocol the USB device claims to speak
usb-productstring	Motorola W385
usb-vendorstring	Motorola Inc.

Not sure if this is of any more use.

                                                                       T     .                                                     
     
   

[nihil]

The W385 and W755 (my phone) seem to have the same product ID. For P2K mode in moto4lin, try these settings:

AT:
22b8
2b44

P2K:
22b8
2b41

And use the first device it creates. If you get a /dev/ttyUSB0 and ttyUSB1, use 0, if you get a 1 and 2, use 1, etc...

[cavit8]

Thanks, these were the first setting settings I used in moto4lin.  I've had no joy at all, but here's a stupid question for those using moto4lin and motorola phones, do you need a specific cable?  I'm using a generic USB cable and adapter. I saw mention recently that only the Motorola USB cable will work.  Which, if true, would explain my dilemma perhaps.