Subject: Re: Bluetooth any/bcsp/irda - msg#00052

Previous Message by Date: click to view message preview

RE: BlueTooth - hopefully the last story e-mail trail?FIGURED OUT!

Hi, see my inline comments below (tdh: ) -----Original Message----- From: h2200-port-bounces-CN5wO63fgwogsBAKwltoeQ@xxxxxxxxxxxxxxxx [mailto:h2200-port-bounces-CN5wO63fgwogsBAKwltoeQ@xxxxxxxxxxxxxxxx] On Behalf Of Matt Reimer Sent: Tuesday, November 08, 2005 1:35 AM To: Matt Reimer Cc: h2200-port-CN5wO63fgwogsBAKwltoeQ@xxxxxxxxxxxxxxxx; Thomas D. Hite Subject: Re: [H2200-port] BlueTooth - hopefully the last story e-mail trail?FIGURED OUT! On Nov 7, 2005, at 11:28 PM, Matt Reimer wrote: > On Nov 7, 2005, at 12:22 PM, Thomas D. Hite wrote: > >> On Tue, 2005-11-08 at 14:05 +1100, Marcus Brown wrote: >>> Hi, >>> I'm still testing, but these are the notes I have so far, >>> perhaps they'll be of some use: >>> BTW irda is running: >>> 2411 root 492 S irattach /dev/ttyS1 >>> >> >> I seem to have it figured. >> >> my device *will* work with bcsp as opposed to 'any' as follows: >> >> hciattach /dev/ttyS3 bcsp 921600 >> >> 'any' is not defaulting correctly for me. >> >> /sys/class/bluetooth/hci0/* gives this if I attach with 'bcsp': >> >> root@h2200:/sys/class/bluetooth/hci0# for i in *; do echo -n "$i: >> "; cat >> $i; done >> address: 00:05:16:5A:FB:72 >> flags: 0x7d >> inquiry_cache: name: hci0 >> type: 3 > > Interesting. This would imply that you have a different bluetooth > chip than the rest of us (Zeevo TC2001P). > > Thomas, two things: > > 1. Did you stop /etc/init.d/irattach from running? It will > certainly cause bluetooth problems. [tdh] Yes, and also no (tried both cases). Same response. > > 2. Please send the output of "hciconfig -a" for both the 'bcsp' and > 'any' cases. [tdh-start] 'hciattach with bcsp': hci0: Type: UART BD Address: 00:05:16:5A:FB:72 ACL MTU: 192:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN AUTH ENCRYPT RX bytes:313 acl:0 sco:0 events:15 errors:0 TX bytes:484 acl:0 sco:0 commands:14 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: 'h2200' Class: 0x120112 Service Classes: Networking Device Class: Computer, Handheld HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver: 0x20d Manufacturer: Cambridge Silicon Radio (10) 'hciattach with any': hci0: Type: UART BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN INIT RUNNING RX bytes:120 acl:0 sco:0 events:0 errors:120 TX bytes:4 acl:0 sco:0 commands:1 errors:0 [tdh-end] > > Matt The Zeevo will certainly not work in bcsp mode, so I'd like to verify whether or not you have a Zeevo chip. So two more ideas: 3. What does wince say about bluetooth? Look in the Asset Viewer under Radio. [tdh-start] ... - Version | Product Revision Level: B01 | ROM Date: 03/01/04 | ROM Revision: 1.10.07 ENG | OS Version: Windows CE 4.20 | Bootstrat Version: 0.39 | Bootloader Versin: 1.11 ... - BlueTooth | Module Type: 1 | Radio Revision: 525 | Radio Present: Y [tdh-end] 4. If you're up to it, open your h2200 and snap a picture of the front of the motherboard. For comparison, see http://opdenacker.org/ pda/h2210/photos/disassembled/front_Med.jpg.3.html where the Zeevo is visible as the light blue chip in the top right corner. [tdh]: I can later this week. Matt _______________________________________________ H2200-port mailing list H2200-port-CN5wO63fgwogsBAKwltoeQ@xxxxxxxxxxxxxxxx https://handhelds.org/mailman/listinfo/h2200-port

Next Message by Date: click to view message preview

Re: Bluetooth version

> > [tdh-start] > ... > - Version > | Product Revision Level: B01 > | ROM Date: 03/01/04 > | ROM Revision: 1.10.07 ENG > | OS Version: Windows CE 4.20 > | Bootstrat Version: 0.39 > | Bootloader Versin: 1.11 > ... > - BlueTooth > | Module Type: 1 > | Radio Revision: 525 > | Radio Present: Y > [tdh-end] My results are identical to Tom's, both on 'Version' and 'Bluetooth' > 4. If you're up to it, open your h2200 and snap a picture of the > front of the motherboard. For comparison, see http://opdenacker.org/ > pda/h2210/photos/disassembled/front_Med.jpg.3.html where the Zeevo is > visible as the light blue chip in the top right corner. > I would be happy to, but I don't have a torx that small - I am guessing a tx5 ?? I'll swing by the hardware store and see if I can do this tonight. HTH, j.

Previous Message by Thread: click to view message preview

Re: New rootfs posted... : Re: suspend/resume again

Ok, silly me :-P hehehe. I forgot about /sbin, thanks to both of you... I'll try later at home, after work. Regards: Bdk

Next Message by Thread: click to view message preview

Re: Bluetooth version

> > [tdh-start] > ... > - Version > | Product Revision Level: B01 > | ROM Date: 03/01/04 > | ROM Revision: 1.10.07 ENG > | OS Version: Windows CE 4.20 > | Bootstrat Version: 0.39 > | Bootloader Versin: 1.11 > ... > - BlueTooth > | Module Type: 1 > | Radio Revision: 525 > | Radio Present: Y > [tdh-end] My results are identical to Tom's, both on 'Version' and 'Bluetooth' > 4. If you're up to it, open your h2200 and snap a picture of the > front of the motherboard. For comparison, see http://opdenacker.org/ > pda/h2210/photos/disassembled/front_Med.jpg.3.html where the Zeevo is > visible as the light blue chip in the top right corner. > I would be happy to, but I don't have a torx that small - I am guessing a tx5 ?? I'll swing by the hardware store and see if I can do this tonight. HTH, j.