July 2002 - Bluetooth-dev - lists.apple.com

Re: Jaguar broke my Bluetooth code!
by Bubba Giles 29 Jul '02

29 Jul '02

This is a good (but bad news) find -- looks like we have a bug in our parser that does not handle a zero-length name header properly. Unfortunately, we have never seen any device send a zero-length name, so we did not catch it. I can provide you with a new parser library that should fix the problem, just let me know if you would like to try it out. At least it will get you going again. jason bubba(a)apple.com > It is quite likely I have a memory problem somewhere, but as I know > Apple engineers are reading this, I am hoping for some inside > information on what could be going wrong. > > Basically, in my OBEX-get handler, I extract the OBEX-headers like this: > > CFDictionaryRef dictionaryRef = NULL; > dictionaryRef = OBEXGetHeaders( inOBEXSessionEventData->headerDataPtr, > inOBEXSessionEventData->headerDataLength ); > > This ends up crashing on Jaguar 6C106. Stack trace as follows: > > #0 0x90074e84 in memmove > #1 0x901bc84c in __CFStringCreateImmutableFunnel3 > #2 0x9014f9fc in CFStringCreateWithBytes > #3 0x96f20128 in OBEXGetHeaders > #4 0x002d177c in -[JSIrMCTransportImpl OBEXGetHandler:] > (JSIrMCTransportImpl.m:315) > > Now, it works fine the first time I'm doing a get, but crashes with a > SIGSEGV the second time (for a different file). Looking at the headers > before calling OBEXGetHeaders, I noticed that the second time around, > the device has passed an empty "name" header, like this: > > 0000: 01 00 03 49 01 bb 54 6f 74 61 6c 2d 52 65 63 6f > ...I..Total-Reco > > It is _possible_ (although not likely) that this is causing the problem > in OBEXGetHandler. Unless, of course I have messed up the heap before > all this happens. > > Any ideas? Most importantly, it would be really helpful to learn from > Apple developers what could be going wrong in OBEXGetHeaders; as far as > I can tell from using NSLog, the data I'm passing to OBEXGetHeaders is > ok. > > Cheers, > Jonas > > PS. Also. The received data fits in one frame. > PPS. If there is a better channel for discussing this, let me know. > _______________________________________________ > bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com > Help/Unsubscribe/Archives: > http://www.lists.apple.com/mailman/listinfo/bluetooth-dev > Do not post admin requests to the list. They will be ignored. _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0

Jaguar broke my Bluetooth code!
by Jonas Salling 28 Jul '02

28 Jul '02

It is quite likely I have a memory problem somewhere, but as I know Apple engineers are reading this, I am hoping for some inside information on what could be going wrong. Basically, in my OBEX-get handler, I extract the OBEX-headers like this: CFDictionaryRef dictionaryRef = NULL; dictionaryRef = OBEXGetHeaders( inOBEXSessionEventData->headerDataPtr, inOBEXSessionEventData->headerDataLength ); This ends up crashing on Jaguar 6C106. Stack trace as follows: #0 0x90074e84 in memmove #1 0x901bc84c in __CFStringCreateImmutableFunnel3 #2 0x9014f9fc in CFStringCreateWithBytes #3 0x96f20128 in OBEXGetHeaders #4 0x002d177c in -[JSIrMCTransportImpl OBEXGetHandler:] (JSIrMCTransportImpl.m:315) Now, it works fine the first time I'm doing a get, but crashes with a SIGSEGV the second time (for a different file). Looking at the headers before calling OBEXGetHeaders, I noticed that the second time around, the device has passed an empty "name" header, like this: 0000: 01 00 03 49 01 bb 54 6f 74 61 6c 2d 52 65 63 6f ...I..Total-Reco It is _possible_ (although not likely) that this is causing the problem in OBEXGetHandler. Unless, of course I have messed up the heap before all this happens. Any ideas? Most importantly, it would be really helpful to learn from Apple developers what could be going wrong in OBEXGetHeaders; as far as I can tell from using NSLog, the data I'm passing to OBEXGetHeaders is ok. Cheers, Jonas PS. Also. The received data fits in one frame. PPS. If there is a better channel for discussing this, let me know. _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0

RE: Unsolicited idea
by Hopkins, Bruce (B.E.) 26 Jul '02

26 Jul '02

Hi all, One quick note: iBooks don't have PCMCIA slots. Also, a USB interface (compared to PCMCIA) is a superior form factor because a USB slot is gauranteed to be on every Apple product until "kingdom come". This is really nice because I can still use my Bluetooth device on iMacs, eMacs, and PowerMacs. Ti Powerbooks are the ONLY macs that have PCMCIA. Bruce -----Original Message----- From: Gregory P. Perez [mailto:gpp7824@mac.com] Sent: Wednesday, July 24, 2002 11:12 PM To: bluetooth-dev(a)lists.apple.com Subject: Unsolicited idea Unsolicited Product Idea from student developer: I am a student ADC member and a Ti Powerbook user. With the heavy emphasis lately on bluetooth for iSync, the lack of internal bluetooth adapters for the powerbook is problematic. Although a USB-bluetooth adapter is currently available this is not really a practical product for mobile users. The prospect of a fragile, dangling USB adapter is simply contrary to the inherent product mobility. Lacking other available interfaces, a PCMCIA (PC-Card) solution would be ideal for powerbook and ibook users alike, so long as the dimensions of the external antenna were minimal. Future powerbook/ibook revisions may have an integrated bluetooth adapter but for the existing userbase, such a PCMCIA solution would be a natural solution and easily marketable given that generic PC adapters may not offer adequate OS integration. Thank you. Greg P. _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored. _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0

Unsolicited idea
by Gregory P. Perez 25 Jul '02

25 Jul '02

Unsolicited Product Idea from student developer: I am a student ADC member and a Ti Powerbook user. With the heavy emphasis lately on bluetooth for iSync, the lack of internal bluetooth adapters for the powerbook is problematic. Although a USB-bluetooth adapter is currently available this is not really a practical product for mobile users. The prospect of a fragile, dangling USB adapter is simply contrary to the inherent product mobility. Lacking other available interfaces, a PCMCIA (PC-Card) solution would be ideal for powerbook and ibook users alike, so long as the dimensions of the external antenna were minimal. Future powerbook/ibook revisions may have an integrated bluetooth adapter but for the existing userbase, such a PCMCIA solution would be a natural solution and easily marketable given that generic PC adapters may not offer adequate OS integration. Thank you. Greg P. _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0

Re: Compatible Hardware? (regarding Ericsson ROK101 007)
by Ragnar Sundblad 10 Jul '02

10 Jul '02

--On den 10 juli 2002 10:46 -0700 Bubba Giles <bubba(a)apple.com> wrote: Regarding the Ericsson USB dev kit - we have fixed a few problems in our stack related to this device (thanks to info provided by Ragnar), and it should be working much better in our next release. I might add that this is with recent firmware in the ROK 101 007, I have no idea what happens with older versions. I guess that many of those old (horribly expensive) eval kits have old firmware which is probably pre BT 1.1, and I think there are significant changes in the HCI spec that causes incompatibilites between the versions. Most probably older versions have bugs and are missing features too. If you are interrested in new firmware, talk to your distributor and get firmware R1C (current release), or talk to me off the list and I'll see what I can do. (I have no connection to ericsson, I just happened to have a ROK 101 007 that didn't work with apples driver which seemed silly, and a phone with BT that I wanted to backup (and another really boring project that I am supposed to work in instead :-).) /ragge _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0

Re: Compatible Hardware? (regarding Ericsson ROK101 007)
by Bubba Giles 10 Jul '02

10 Jul '02

Hi Erik (and everyone else), Regarding the Ericsson USB dev kit - we have fixed a few problems in our stack related to this device (thanks to info provided by Ragnar), and it should be working much better in our next release. Jason bubba(a)apple.com >> Anyhow, my question: Is there any available hardware that will work with >> the seed? Any possibility of tweaking drivers to make a PC-Card >> implementation work (this is actually preferable to USB for me anyway)? >> Any alternate source of the DLink hardware? I've been up and down the >> web looking for a way to put this software to use. > > Erik, > > All available USB dongles should work on our stack (TDK, Mitsumi, 3COM). As > others can attest to, the Ericsson Development kit may cause you grief, but > I think they are expensive so this probably won't be an issue for you. We do > not have a PC Card HCI driver, but would love it if someone wanted to take > it on. We have abstracted the HCI controller stuff as much as possible to > make this easy. All you would need to do is subclass our controller and > override the methods to send and receive data on the PC Card. > > Hope that helps, > > Jason > bubba(a)apple.com _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0

Re: HCI over USB with D-Link adapter
by Ragnar Sundblad 10 Jul '02

10 Jul '02

Hello Dmitri, Actually, I just did this myself the other day for a quick and dirty test program. I am by no means an expert on this! (This list maybe aren't really for those that are implementing their own HCI commanders, i guess the others will just have to suffer then. :-) --On den 9 juli 2002 18:17 -0700 Dmitri Moukhine <dmitrim(a)mac.com> wrote: ... bool write_command(void* data, int size) { bool ok = false; IOUSBDevRequestTO req; IOReturn err = 0; memset(&req, 0, sizeof(req)); // initialize request structure req.bmRequestType = USBmakebmRequestType(kUSBOut, kUSBClass, kUSBEndpoint); req.bRequest = BLUETOOTH_CONTROL_REQUEST_TYPE; //0x20 req.wValue = 0; req.wIndex = 0; req.wLength = size; req.pData = data; req.noDataTimeout = NO_DATA_TIMEOUT; // 5000 req.completionTimeout = NO_COMPLETION_TIMEOUT; // 5000 I used req.bmRequestType = 0x20 and req.bRequest = 0 and 1000 for both timeouts, and it worked fine. Don't ask me for the reason for this, I don't remember it anymore. :-) With that setup I can send for example a Read_BD_Addr with data = {0x09, 0x10, 0x00} and len = 3 and read the reply on the interrupt port. Good luck! /ragge PS. Mind telling us what you are writing? _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0

HCI over USB with D-Link adapter
by Dmitri Moukhine 10 Jul '02

10 Jul '02

Hi, I was asking about how to send HCI commands over USB to the Bluetooth adapter in yesterday post "D-Link bluetooth usb adapter". It looks like I'm initializing IOUSBDevRequest wrong. The best I can came up with is the code below. It still doesn't work. After I issue HCI_Read_Buffer_Size command there is no any data on event pipe. I think my bRequestType or/and bRequest wrong and data is not get interpreted as an HCI command. HCI_Read_Buffer_Size is the first command I send to the adapter. Could somebody give me a hand on that? Thank you, Dmitri. bool write_command(void* data, int size) { bool ok = false; IOUSBDevRequestTO req; IOReturn err = 0; memset(&req, 0, sizeof(req)); // initialize request structure req.bmRequestType = USBmakebmRequestType(kUSBOut, kUSBClass, kUSBEndpoint); req.bRequest = BLUETOOTH_CONTROL_REQUEST_TYPE; //0x20 req.wValue = 0; req.wIndex = 0; req.wLength = size; req.pData = data; req.noDataTimeout = NO_DATA_TIMEOUT; // 5000 req.completionTimeout = NO_COMPLETION_TIMEOUT; // 5000 err = (*gIntf)->ControlRequestTO(gIntf, 0, &req); if (kIOReturnSuccess == err) { ok = true; printf("write_command: %d bytes written.\n", req.wLenDone); dump(req.pData, req.wLenDone); // for HCI_Read_Buffer_Size it is 05 04 00 - bin : 01010000. 00 (ocf 0x05) 000100 (ogf 0x04) 00000000 (param size 0) } else printf("write_command: failed with System: %04x, subSystem %04x, code: %04x.\n", err_get_system(err), err_get_sub(err), err_get_code(err)); return ok; } _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0

Re: Compatible Hardware?
by Bubba Giles 10 Jul '02

10 Jul '02

> Anyhow, my question: Is there any available hardware that will work with > the seed? Any possibility of tweaking drivers to make a PC-Card > implementation work (this is actually preferable to USB for me anyway)? > Any alternate source of the DLink hardware? I've been up and down the > web looking for a way to put this software to use. Erik, All available USB dongles should work on our stack (TDK, Mitsumi, 3COM). As others can attest to, the Ericsson Development kit may cause you grief, but I think they are expensive so this probably won't be an issue for you. We do not have a PC Card HCI driver, but would love it if someone wanted to take it on. We have abstracted the HCI controller stuff as much as possible to make this easy. All you would need to do is subclass our controller and override the methods to send and receive data on the PC Card. Hope that helps, Jason bubba(a)apple.com _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0

Compatible Hardware?
by Erik Sea 09 Jul '02

09 Jul '02

Hi, I apologize if this has been answered before, but the lists.apple.com archive search doesn't allow searching of this list (should be somewhere between augd and carbon-development, yes?). When I worked at Palm, I was involved in the Bluetooth effort (developing sample HCI drivers for licensee use). Now that I'm at Sony, I still find myself involved in Bluetooth efforts from time to time (especially interesting with the first demo of a Clie to Mac Bluetooth HotSync at Macworld Tokyo). At WWDC, I attended Bluetooth and Wireless sessions, and got all psyched about doing Bluetooth stuff on Mac OS X. But, as of WWDC, the only "supported" Bluetooth hardware is the D-Link USB-Bluetooth dongle. And, from WWDC to date, this has been listed on the "Buy Now" linke from http://www.apple.com/bluetooth/ as "Temporarily Unavailable". It has been "temporarily unavailable" from WWDC to date; i.e., approximately two months now. I wrote in to dev seeding to see if there was any other supported hardware (since the only way I can use the seed is if I have some sort of hardware to play with), and it was suggested I try dlink directly, which I did. They gleefully accepted my order. Then they told me it was backordered two weeks. Then, after three weeks, they told me it was backordered another two weeks, but that they did not know when they would get product in (the upshot of this is that two weeks is the same as infinity, as far as they shipping department is concerned). Anyhow, my question: Is there any available hardware that will work with the seed? Any possibility of tweaking drivers to make a PC-Card implementation work (this is actually preferable to USB for me anyway)? Any alternate source of the DLink hardware? I've been up and down the web looking for a way to put this software to use. -- Erik Sea, CPM, CSDP, PPCD, MBA +1(775)224-5328 _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0