Messages

1

Sharp ROMs / Howto For Coompiling Cacko Rom

« on: January 05, 2006, 12:54:11 pm »

Could someone point me to a HOWTO for compiling the Cacko ROM for the SL-C3000.

Specially, I'm trying to port zinf.

2

Security and Networking / Bluetooth Cf Works Only If Usb Cable Connected

« on: October 03, 2005, 10:33:13 am »

I'm have no need to support IP over Bluetooth, and therefore I have not looked into PAN or PPP (over RFCOMM).

My Zaurus is communicating via bluetooth to a Bluetooth Serial Port Adapter (connectBlue). On the Zaurus, I have rfcomm configured and am running a C program that opens /dev/rfcomm0 and starts sending and receiving bytes to/from the connectBlue device. The C program runs fine for a few seconds but then stops working. Because the communications using /dev/rfcomm0 wasn't reliable I started debugging the problem using l2ping to verify that the bluetooth communications was working between the Zaurus and the connectBlue device. This is when I reported my initial problem that l2ping wasn't working with my configuration. And then by accident I realized that the Bluetooth communication became reliable when I connected the completely unrelated USB cable.

I don't want to give up on this configuration, but I'm starting to consider switching to OpenZaurus or Cacko.

3

Security and Networking / Bluetooth Cf Works Only If Usb Cable Connected

« on: September 30, 2005, 10:53:54 am »

what does "ifconfig -a" and "netstat -r" say?

could it be simply the default route is not being set?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=97206\"][{POST_SNAPBACK}][/a][/div]

Thanks for the suggestion. I've tried a few things, but haven't made any progress.

When the USB is connected ifconfig -a lists two interfaces:
  lo inet addr: 127.0.0.1 ...
  usbd0 inet addr: 192.168.129.201 ...

And netstat -r lists 192.168.129.0 as the default gateway.

I don't fully understand how the IP routes are used by l2ping which takes as input a bluetooth MAC address.  My end application is to associate a TTY using rfcomm and then interface to the Bluetooth device as I would any serial device.

So I tried the following just to verify that the default routes are not being used by l2ping.

1. Connected the USB cable.
2. Checked the routing table. 192.168.129.0 was there.
3. Verified the l2ping to the Bluetooth device works without problem.
4. Removed the default route using:  route delete -net 192.168.129.0/24 usdb0
5. Verified the routing table was empty.
6. Repeated the l2ping. Which works flawlessly. l2ping didn't care that there was no default route.

I then tried the following:
1. With the USB cable still connected, started the l2ping to the Bluetooth device. Works flawlessly with response times around 40 ms.
2. While the l2ping was in progress, disconnected the USB cable. The l2ping starts reporting response times around 2-3 seconds.
3. After 3 or 4 slow responses, I reconnect the USB cable. The l2ping returns to normal with response times around 40 ms.

Any further suggestions would be appreciated.

4

Security and Networking / Bluetooth Cf Works Only If Usb Cable Connected

« on: September 12, 2005, 04:14:06 pm »

I was having trouble getting my D-Link BCF-650BT CF card to work and discovered that it works flawlessly if the USB cable is connected between my Zaurus and my Windows PC.

I need this to work without the USB cable. Does anyone have any ideas.

I posted a description of my original problem here:

Bluez On Sl-c3000 Using Dcf-650bt

5

Security and Networking / Bluez On Sl-c3000 Using Dcf-650bt

« on: September 12, 2005, 04:06:09 pm »

It works. . . but only if the USB cable is connected to my Windows PC.

If I try the steps to reproduce the described problem with the USB cable connected to my Windows box every thing works as it should. l2ping has been going for 15 minutes with response times right around 45 ms.

If I try the steps to reproduce the described problem without the USB cable connected then the problem occurs every time.

Does anyone have an idea why having the USB cable would make my bluetooth CF card work? This is a PDA, so I can't have this only working when my Zaurus is connected to a Windows PC via USB.

6

Security and Networking / Bluez On Sl-c3000 Using Dcf-650bt

« on: September 12, 2005, 01:27:31 pm »

Summary

I am having problems with the D-Link DCF-650BT CF card on SL-C3000 and would appreicate any assistance in debugging the problem.

Everything looks fine; however after a few pings, l2ping timeouts out and dmesg has the following entries:

bcsp_pkt_cull: Peer acked invalid packet
bcsp_handle_le_pkt: Found a LE sync pkt, card has reset
bcsp_pkt_cull: Peer acked invalid packet
bcsp_handle_le_pkt: Found a LE sync pkt, card has reset
bcsp_pkt_cull: Peer acked invalid packet
bcsp_handle_le_pkt: Found a LE sync pkt, card has reset
. . .


Detailed Description

1. Reboot the Zaurus w/ the D-Link CF card installed.

2. After the reboot, the card is recognized.

cardctl ident gives:

Socket 0:
  product info: "Bluetooth BT0100M", "", ""
  function: 2 (serial)
Socket 1:
  product info: "HITACHI", "microdrive"
  manfid: 0x0319, 0x0000
  function: 4 (fixed disk)

3. hci also appears to be ok.

hciconfig -a gives:

hci0:   Type: UART
   BD Address: 00:40:05:D4:A4:6D ACL MTU: 192:8  SCO MTU: 64:8
   UP RUNNING PSCAN ISCAN
   RX bytes:584 acl:0 sco:0 events:16 errors:0
   TX bytes:500 acl:0 sco:0 commands:16 errors:0
   Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
   Link policy: RSWITCH HOLD SNIFF PARK
   Link mode: SLAVE ACCEPT
   Name: 'zaurus'
   Class: 0x120104
   Service Classes: Networking
   Device Class: Computer, Desktop workstation
   HCI Ver: 1.1 (0x1) HCI Rev: 0x110 LMP Ver: 1.1 (0x1) LMP Subver: 0x110
   Manufacturer: Cambridge Silicon Radio (10)

hcitool dev gives:

Devices:
   hci0   00:40:05:D4:A4:6D

4. Can successfully scan for neighboring devices:

hcitool scan gives:

Scanning ...
   00:12:F3:00:51:8A   BD2

5. However the l2ping fails after a few seconds:

Ping: 00:12:f3:00:51:8a from 00:40:05:D4:A4:6D (data size 20) ...
20 bytes from 00:12:f3:00:51:8a id 0 time 39.24ms
20 bytes from 00:12:f3:00:51:8a id 1 time 74.83ms
no response from 00:12:f3:00:51:8a: id 201
no response from 00:12:f3:00:51:8a: id 202
no response from 00:12:f3:00:51:8a: id 203
no response from 00:12:f3:00:51:8a: id 204
. . .


Configuration

I'm using the Sharp ROM and have the following packages installed:

sudo_0.1_arm.ipk
susp-resume_0.9-3.1.ipk
bluez-zaurus_2.12-2.4.20-alpha4_arm.ipk
susp-resume-bluez_0.9.3_arm.ipk

cat /etc/bluetooth/uart
"Bluetooth BT0100M", "", "":/dev/ttyS3 bcsp
. . .

cat /etc/bluetooth/hcid.conf
#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.3 2002/07/18 18:12:46 maxk Exp $
#

# HCId options
options {
   # Automatically initialize new devices
   autoinit yes;

   # Security Manager mode
   #   none - Security manager disabled
   #   auto - Use local PIN for incoming connections
   #   user - Always ask user for a PIN
   #
   security auto;

   # Pairing mode
   #   none  - Pairing disabled
   #   multi - Allow pairing with already paired devices
   #   once  - Pair once and deny successive attempts
   pairing multi;

   # PIN helper
   pin_helper /etc/bluetooth/givepin;
}

# Default settings for HCI devices
device {
   # Local device name
   #   %d - device id
   #   %h - host name
   name "%h";

   # Local device class
   #class 0x120114;
   class 0x120104;

   # Default packet type
   #pkt_type DH1,DM1,HV1;

   # Inquiry and Page scan
   iscan enable; pscan enable;

   # Default link mode
   #   none   - no specific policy
   #   accept - always accept incoming connections
   #   master - become master on incoming connections,
   #            deny role switch on outgoing connections
   #
   #lm accept,master;
   #
   lm accept;

   # Default link policy
   #   none    - no specific policy
   #   rswitch - allow role switch
   #   hold    - allow hold mode
   #   sniff   - allow sniff mode
   #   park    - allow park mode
   #
   #lp hold,sniff;
   #
   lp rswitch,hold,sniff,park;

   # Authentication and Encryption
   #auth enable;
   #encrypt enable;
}