Bluetooth On The Sl-3000?

[nein]

syslog:
Feb  2 12:45:31 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb  2 12:45:32 localhost kernel: bcsp_recv: Short BCSP packet
Feb  2 12:45:32 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb  2 12:45:32 localhost kernel: bcsp_recv: Short BCSP packet
Feb  2 12:45:33 localhost kernel: bcsp_recv: Short BCSP packet
Feb  2 12:45:33 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb  2 12:45:34 localhost last message repeated 7 times
Feb  2 12:45:34 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 7 expected 6
Feb  2 12:45:34 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 0 expected 6
Feb  2 12:45:34 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 1 expected 6
Feb  2 12:45:35 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb  2 12:45:36 localhost last message repeated 7 times
Feb  2 12:45:36 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 7 expected 6
Feb  2 12:45:36 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 0 expected 6
Feb  2 12:45:36 localhost kernel: bcsp_recv: Out-of-order packet arrived, got 1 expected 6
Feb  2 12:45:37 localhost kernel: bcsp_recv: Error in BCSP hdr checksum
Feb  2 12:45:37 localhost last message repeated 2 times
[div align=\"right\"][a href=\"index.php?act=findpost&pid=79424\"][{POST_SNAPBACK}][/a][/div]

i had a aimilar problem with the sharp rom. i had to do a
echo 1 > /proc/lock_fcs

which solved the problem for me.
anyway after i updated to cacko 3kb1 my card works without problems.

[Ragnorok]

FINALLY I'm on the right drivers/thread.  Many apologies for my blatant ignorance!!
  BUT it won't connect.  Here's the latest:

- Wipe everything done so far, except sudo. (grin)
- Install susp-resume
- Install alpha4 bluez for 2.4.20.
- Install susp-resume-bluez
- Set up everything as given in the BT HowTo that Tumnus so conveniently has a link to in his signature.  (cheshire grin)  sdptool shows the phone's services, mac, etc.  Network applet appears as expected.
- BUT it won't pair.  Issuing "dund -c <mac>", then retrying, says the device is not available, so I rebooted the Z, even though it just says to turn it off.
- Still nothing.  This keeps asking me for a password when I try to connect, even though I never put one in the profile.  It doesn't seem to matter what I put here, it still fails.  That shouldn't be necessary to pair, should it?  Just to connect to Sprint once the link is active?
- Here's my configuration:

Code: [Select]

# hciconfig -a
hci0:   Type: PCCARD
        BD Address: ACL MTU: 672:8  SCO MTU: 64:0
        UP RUNNING PSCAN ISCAN
        RX bytes:961 acl:34 sco:0 events:51 errors:1
        TX bytes:828 acl:32 sco:0 commands:15 errors:0
        Features: 0xff 0xfb 0x01 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'hiroshi'
        Class: 0x120114
        Service Classes: Networking
        Device Class: Computer, Palm
        HCI Ver: 1.1 (0x1) HCI Rev: 0x8103 LMP Ver: 1.1 (0x1) LMP Subver: 0x8b40
        Manufacturer: Ericsson Technology Licensing (0)

# rfcomm -a
rfcomm0: channel 4 closed
# rfcomm connect /dev/ttyS3
Can't connect RFCOMM socket: Connection refused
# rfcomm connect /dev/ttyS3 4
Can't create RFCOMM TTY: Address already in use
# /etc/rc.d/init.d/bluetooth restart
Shutting down Bluetooth... Done.
Starting Bluetooth... Done.
# rfcomm connect /dev/ttyS3 4
Can't connect RFCOMM socket: Resource temporarily unavailable

# cat uart
"AmbiCom BT2000E", "Bluetooth PC/CF Card", "", "":/dev/ttyS3 bt2000c flow
"CF Card", "GENERIC", "", "":/dev/ttyS3 bcsp
"Compact Flash", "Bluetooth Card", "", "":/dev/ttyS3 bcsp

# cat rfcomm.conf
#
# RFCOMM configuration file.
#
# $Id: rfcomm.conf,v 1.1 2002/10/07 05:58:18 maxk Exp $
#
rfcomm0 {
        # Automatically bind the device at startup
        bind yes;

        # Bluetooth address of the device
        device ;

        # RFCOMM channel for the connection
        channel 4;

        # Description of the connection
        comment "Diver Link";
}

# cat /etc/ppp/peers/IRD*
/dev/rfcomm0
noipdefault
115200
connect '/usr/sbin/chat -s -v -t 60 ABORT "NO CARRIER" ABORT "NO DIALTONE" ABORT
 "BUSY" "" "ATZ" OK "ATQ0V1S100=1" OK "ATDTLG PM325" CONNECT "\\d\\d"'
crtscts
lock
modem
usepeerdns
defaultroute
mtu 576
mru 576
connect-delay 1000
remotename IRDA1116159478
- After rebooting, hcitool no longer functions.  I used to be able to "cc" a connection, and "name" to at least get the BT Name of the phone.  Now it's down, even after restarting bluetooth.  (pout)  Ah.  Ejected the CF and reseated.  Now we're back in business:

Code: [Select]

# hcitool dev
Devices:
        hci0    
# hcitool cc --role m
# hcitool name
Diver
# hcitool inq
Inquiring ...
               clock offset: 0x5c2a    class: 0x400204- After doing the above, rfcomm shows /dev/ttyS3 is already in use, implying some sort of connecting, even though the Network Applet won't pair.  It just sits there at "Connecting" for a minute or so, then pops to "Network Offline".
- If I tell the phone to do "Searching and pairing" instead of "Waiting for pairing", and I do this when the Network Applet says "Connecting", I see "hiroshi" (Z's hostname) in the list of devices.  If I select that, and enter the PIN from hiroshi, the phone says "pairing".  Now as far as I know this isn't DUNS, so it fails to establish a network link, BUT it does show that, from the phone's standpoint, hiroshi is present and accounted for.  I *assume*  (eeeek!) that I need to use "Waiting for pairing" to get DUNS to work, but I haven't seen any real information to support that assumption, actually.
- So hiroshi can obviously talk to the phone just fine, and the phone can talk to hiroshi just fine, but it won't establish a faux IR link.  I'm sure I'm missing something patently simple, since I'm such a Noob.  If someone could point out that simple thing I'd really appreciate it!  (cheshire grin)

[tumnus]

You need to pair your Zaurus and Phone for any such connection. Read the bit about pins in the BlueZ Introduction and it should be clear what pin you need to enter in which file.

[Ragnorok]

- Thanks, Tumnus!
- Actually, I did all this.  I have 'pin' and 'givepin' setup as described.  When I do "Wait for pairing" I enter the PIN I put in each of those files.  If I don't, it fails instantly, so that part must be working to some degree.  After this post, I did in fact get it to work, sort of.  This post indicates the results.
- Since then, I've experienced very, very inconsistent results from BlueZ, and I started poking around with it.  I just put a bunch of echos in the ../init.d/bluetooth startup script, and took out all of the output redirections to /dev/null so I could see exactly what it's doing.  I also whipped up a script to run bits of BT init/shutdown individually, based on the contents of the bluetooth initialization script.  Here's the result:

Code: [Select]

# $HOME/bt restart
Shutting down Bluetooth...
- Releasing rfcomm binding...
- Killing hcid...
- Killing sdpd...
- Killing hciattach...
- Unloading modules...
bluez: Device or resource busy
Done.
Starting Bluetooth...
- Loading modules...
- Creating devices...
- Loading hcid...
- Loading sdpd...
- Finding uart settings for: "AmbiCom,Inc", "BT2000E", "Bluetooth PC/CF Card"
- Starting uart with: /dev/ttyS3 bt2000c flow
Can't get port settings: Input/output error
Can't initialize device: Input/output error
- Binding rfcomm...
Done.
#- It always says bluez is busy, and in fact I don't even know why it's trying to unload that.  It unloads when the BT card is ejected, and loads when it's put back in, so the startup script doesn't need to bother with it.  (shrug)  Minor, at best.
- Using this, I initially discovered that my /etc/bluetooth/uart file didn't have the right entry for an AmbiCom BT2000E (it says "AmbiCom" as shipped instead of "AmbiCom,Inc" in the first entry), so it wasn't finding it.  I fixed the line so it does find it now.  Despite this, it did work from time to time.  Go figure!  (grin)
- The "Starting uart with..." line appears just before the hciattach call to dump the parms it's passing to that.  So I tried:

Code: [Select]

# $HOME/bt attach /dev/ttyS2 bt2000c flow
Can't get port settings: Input/output error
Can't initialize device: Input/output error
#which just runs hciattach with the given parameters, mimicing what the bluetooth initialization script should be doing.
- I also stopped BT and manually entered the commands listed in the startup script.  No surprise, I get the *same* result!  (snicker)
- Are these input/output messages this normal?

- I found a post that indicates restarting pcmcia on a SL6000 fixed things.  Not so here ... doing that ejects the CF ... when I pop and reseat, then restart bluetooth, I get exactly the same results.

- That same post also indicates loading the hci_uart module helped.  When I stop bluetooth and manually run through the startup procedure, tossing in a "modprobe hci_uart", it still does the same thing when I get to hciattach.

- I haven't located how it "pairs".  I'd like to poke around with doing that manually as well.  Is hciattach supposed to do that?

- DESPITE the errors on load, running hcitools gives this:

Code: [Select]

# hcitool cc --role m
# hcitool name
Diver
# hcitool info
Requesting information ...
        BD Address:  
        Device Name: Diver
        LMP Version: 1.2 (0x2) LMP Subversion: 0xdb0
        Manufacturer: Texas Instruments Inc. (13)
        Features: 0xff 0xff 0x2d 0xf8 0x1b 0x18 0x00 0x80
                <3-slot packets> <5-slot packets>
                
                
                
                
                
                
                
                
#- Seems pretty wierd to me, that it apparently errors on restart, and hcitool works, but I don't claim to know what's happening here.  I do know it won't pair, and it won't connect unless my phone is in "full discover", and even then it's flakier than psoriasis.  (shrug)  Just information, mind you.  Just information.

- Here's some files, just 'cause I can:

Code: [Select]

# cat /etc/bluetooth/rfcomm.conf
#
# RFCOMM configuration file.
#
# $Id: rfcomm.conf,v 1.1 2002/10/07 05:58:18 maxk Exp $
#

rfcomm0 {
        # Automatically bind the device at startup
        bind yes;
        # Bluetooth address of the device
        device ;
        # RFCOMM channel for the connection
        channel 4;
        # Description of the connection
        comment "Diver modem";
}
# cat /etc/bluetooth/uart
"AmbiCom,Inc", "BT2000E", "Bluetooth PC/CF Card", "", "":/dev/ttyS3 bt2000c flow
"CF Card", "GENERIC", "", "":/dev/ttyS3 bcsp
"Compact Flash", "Bluetooth Card", "", "":/dev/ttyS3 bcsp

# cat /etc/bluetooth/pin


# cat /etc/bluetooth/givepin
##############givepin#########
#!/bin/sh
echo "PIN:"
################
#- /etc/bluetooth/hcid.conf has not been touched from the default, so far.
- Could you advise?  Thanks for your time!

[Ragnorok]

FOUND IT.

- I found a post that mentioned /etc/apm.d/bluetooth, so I looked in there, and found out what it does on resume from suspend.  I do those steps:

Code: [Select]

rfcomm bind all
cardctl eject
cardctl insert
hciconfig hci0 up*POOF*  Connects like a charm, stays connected, works fine.  Googe maps loads *really* slow!  (foolish giggle)  So I updated my bt script to do this for me ... if I stick in the card and it won't work, I drop to the command line, run "sudo bt fix", and try to connect again.  Works every time!

- So, what I'd like to know, is how do I just run these commands (i figured the bind isn't really needed, but it doesn't seem to hurt) each time I try to connect with the Network Applet?  Can I just stick them into the /etc/ppp/peers/IRDA<blah> file?  That doesn't seem like it's a script file to me, but it may be possible to run some script from there, and that would certainly do the trick.  Since it actually seems to be necessary *each* time I stick the BT card in, I may as well just make it do that anyway.

- BTW, it seems it was actually "paired", but hiroshi just doesn't appear in the list of paired connections on the phone.  (shrug)  During this latest little stint, I didn't make sure the phone was set to "Show always" (it keeps reverting to 'hide' all the time, which is *good*), and even though it was set to "Hide", it linked up and surfed without any troubles.  Didn't expect it to do a "stealth pairing".  (chuckle)

- Thanks for your time...

[albertr]

i had a aimilar problem with the sharp rom. i had to do a
echo 1 > /proc/lock_fcs

which solved the problem for me.
anyway after i updated to cacko 3kb1 my card works without problems.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=79477\"][{POST_SNAPBACK}][/a][/div]

Could you please elaborate on what /proc/lock_fcs precisely does?
-albertr

[jettie1767]

Hi-

I recently traded up to a C3k from a C860.  I used the Bluez pkg from this thread to connect the C3k with my Moto V635 (Cingular).  I have successfully paired the two but everytime I try to BT connect from the C3k, I see the BT session starting on the cellphone, but it dies after a minute or so.

How can I debug what's going on?

Thanks in advance!

[jettie1767]

Just an update....I just removed all the init strings in the setup and it connects to Cingular GPRS now!  Thanks, Tumnus for the package!

[byland3]

Yes, I am sorry that I forgot to mention what bit hasn't worked...
I am able to pair the devices. But I am not able to connect or send files between them. The network application (with bluetooth applet installed) has been set, but when I try to dial it, the phone does not respond at all. The zaurus just continues to say "initializing modem" but it never gets beyond that point.

I checked in /tmp/ and there was a file called "bluetooth-pppd-log". Inside the file was only the following line:
"Failed to open /dev/rfcomm1: Host is down".

----

Well which bit hasn't worked?

Has your phone paired?

Did the GPRS connection fail? If it did fail, please post the contents of /tmp/qpe-ppp-log .

You don't need any extra packages to get basic Bluetooth working. The qtopia--bluetoothnetworkapplet package doesn't need Java.

You do need to to a 'sdptool browse' to find the actual channel of the DUN profile of your phone as this can differ from model to model.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=78862\"][{POST_SNAPBACK}][/a][/div]

[Stilgar]

Hey,
I've been trying to get my bluetooth keyboard working.
The hidp module exists, but not the hidd server.
Can anyone please post a compiled version of the hidd server?

Thanks.

[tumnus]

I checked in /tmp/ and there was a file called "bluetooth-pppd-log". Inside the file was only the following line:
"Failed to open /dev/rfcomm1: Host is down".
[div align=\"right\"][a href=\"index.php?act=findpost&pid=81742\"][{POST_SNAPBACK}][/a][/div]

The Bluetooth link is not being established. You need to enable syslogging to /var/log/messages to see what is going on.

[Bob Dobolina]

Has anyone gotten the Bluetake card (DLink clone, I think) working with the SL-C3000?
I installed the alpha 4 ipk.  The card is now somewhat recognized when inserted (light turns on, cf icon displays).  However:

hcitool dev

displays nothing.

cardctl ident displays:

Socket 0:
     product info: "Bluetooth BT0100M", "",""
     function: 2 (serial)


Any help is greatly appreciated.

[Cresho]

who is hosting bluez-zaurus_2.12_2.4.20_alpha4_arm.ipk?

Never mind I found it in a link that wasnt even a link.

update!

here is that link for that one file.  the rest should be around..somewhere

{https://www.oesf.org/forums/index.php?act=Attach&type=post&id=279}

just copy that along the address bar without parenthesis.

the rest are here

http://www.zaurususergroup.org/modules.php...ename=Bluetooth


for easier use, i used su zeditor for the files and konsole for executing commands (sl5500 version programs).  or held click the icon and changed it to execute with root privalage.



Hey tumnus!  thanks.  I don't know how to pay you for this man but you did a good job here.

[ashikase]

I didn't see this elsewhere, so I thought I'd post it in case it might help someone else.

Zaurus C3100
Socket Bluetooth CF Rev. H

Using susp_resume_bluez_0.9.3_arm.ipk (the current version?), my card would not resume properly after suspending. By looking at /etc/rc.d/init.d/bluetooth, I found that the trick was to call hciattach (in the init script, it is part of the 'start_uarts()' function).

My modified version of /etc/apm.d/bluetooth contains the following:

Code: [Select]

resume)
   if ... # this part is unchanged
      cardctl resume
      /usr/sbin/hciattach /dev/ttyS3 bcsp 230400
      rfcomm bind all
      hciconfig hci0 up
   else
      ...
Note that the hciattach line listed above is specific to my card, and was found by looking at the file /etc/bluetooth/uart. You could look up the same info for your own card, or make the resume portion generic by pasting the code from start_uarts().

Also note that the rfcomm and hciconfig lines do not seem to be necessary - at least, I am still able to resume and reconnect PAN without those lines. I left them in just to be safe.

- ashikase
- anpachi, gifu, japan

[polito]

Thanks for your post ashikase! That fixed my problem as well. I also have a Zaurus C3100 and am using the Socket Bluetooth CF Rev. H and was really getting sick and tired of having to stop and restart bluetooth all the time by hand. With your changes, I can suspend and resume and everything just works.  

I wonder if perhaps a check for Socket Bluetooth CF Cards should be added to the bluetooth suspend/resume script to do the hciattach if it's needed? I wonder if it's only needed for certain cards or if it causes problems for anyone using a different card? Hmm...