From: Jesse W. <jes...@gm...> - 2006-11-21 08:01:04
|
Hi I was trying to update my kernal from 2.6.16 to 2.6.18 and I ran into the PBA31308 vs PBA31307 problem and my BlueTooth no longer works. Some one mentioned a fix but it was kinda vague. It told me what to change in the bluez-something-something-PBA31308.patch (which I found) but not what to change it *to*... can any one enlighten me? IIRC resp[6], resp[7] and resp[9] was mentioned. Does any one know what those values should be? Here is the error: Starting Bluetooth subsystem:Trying baud rate 57600... > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > Set (GPIO,out,set) via /proc/gpio/GPIO7 > Got response after reset... gobbling > No response from BT module > Trying baud rate 921600... > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > Set (GPIO,out,set) via /proc/gpio/GPIO7 > Got response after reset... gobbling > Error reading response: Success > Trying baud rate 115200... > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > Set (GPIO,out,set) via /proc/gpio/GPIO7 > Got response after reset... gobbling > Detected bluetooth module at 115200 baud > Got: status=0x00, hci_ver=0x01, hci_rev=0x0750, lmp_ver=0x02, > manuf=0x0009, lmp_subver=0x0750 > Not a PBA31307 Thanks for the help! -- -Jesse W. |
From: Jesse W. <jes...@gm...> - 2006-11-21 10:08:28
|
Some more background on this: On 11/21/06, Jesse Welling <jes...@gm...> wrote: > > IIRC resp[6], resp[7] and resp[9] was mentioned. Does any one know what > those values should be? here is the offending line of code: if(resp[6] == 0x0 && (resp[7]&0xf) == 0x5 && resp[9] == 0x05) // PBA31307 confirmed And it is in this file http://svn.gumstix.com/gumstix-buildroot/trunk/package/bluez/bluez-utils-hciattach-pba31308.patch -- -Jesse W. |
From: Mario A. S. <ma...@ne...> - 2006-11-21 12:41:22
|
Jesse Welling wrote: > Hi I was trying to update my kernal from 2.6.16 to 2.6.18 and I ran > into the PBA31308 vs PBA31307 problem > and my BlueTooth no longer works. Some one mentioned a fix but it was > kinda vague. It told > me what to change in the bluez-something-something-PBA31308.patch > (which I found) but not what to change it *to*... > can any one enlighten me? IIRC resp[6], resp[7] and resp[9] was > mentioned. Does any one know what those values should be? > Here is the error: > > Starting Bluetooth subsystem:Trying baud rate 57600... > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > Set (GPIO,out,set) via /proc/gpio/GPIO7 > Got response after reset... gobbling > No response from BT module > Trying baud rate 921600... > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > Set (GPIO,out,set) via /proc/gpio/GPIO7 > Got response after reset... gobbling > Error reading response: Success > Trying baud rate 115200... > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > Set (GPIO,out,set) via /proc/gpio/GPIO7 > Got response after reset... gobbling > Detected bluetooth module at 115200 baud > Got: status=0x00, hci_ver=0x01, hci_rev=0x0750, lmp_ver=0x02, > manuf=0x0009, lmp_subver=0x0750 > Not a PBA31307 > > > Thanks for the help! > > > -- > -Jesse W. > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ------------------------------------------------------------------------ > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > Kernel you mean ? Did you include the modules for your hw ? If not recompile with your hw supported modules. M. |
From: Jesse W. <jes...@gm...> - 2006-11-21 18:25:01
|
Yes I recompiled the kernel but the *physical module* is the old PBA31307 and not the new (RoHS compliant) PBA31308. Problem is that the patch applied now makes the kernel complain that it can't find the right bluetooth *physical module*. I guess I'm going to side skirt the issue by using r1155 of the build root because it looks like the last one before the addition of the patch. To Craig: Would droping in an old buez package directory (/trunk/package/bluez/) from pre 1155 over the new buildroot break any thing? On 11/21/06, Mario A. Spinthiras <ma...@ne...> wrote: > > Jesse Welling wrote: > > Hi I was trying to update my kernal from 2.6.16 to 2.6.18 and I ran > > into the PBA31308 vs PBA31307 problem > > and my BlueTooth no longer works. Some one mentioned a fix but it was > > kinda vague. It told > > me what to change in the bluez-something-something-PBA31308.patch > > (which I found) but not what to change it *to*... > > can any one enlighten me? IIRC resp[6], resp[7] and resp[9] was > > mentioned. Does any one know what those values should be? > > Here is the error: > > > > Starting Bluetooth subsystem:Trying baud rate 57600... > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > Got response after reset... gobbling > > No response from BT module > > Trying baud rate 921600... > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > Got response after reset... gobbling > > Error reading response: Success > > Trying baud rate 115200... > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > Got response after reset... gobbling > > Detected bluetooth module at 115200 baud > > Got: status=0x00, hci_ver=0x01, hci_rev=0x0750, lmp_ver=0x02, > > manuf=0x0009, lmp_subver=0x0750 > > Not a PBA31307 > > > > > > Thanks for the help! > > > > > > -- > > -Jesse W. > > ------------------------------------------------------------------------ > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > > opinions on IT & business topics through brief surveys - and earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > Kernel you mean ? > > Did you include the modules for your hw ? > > If not recompile with your hw supported modules. > > M. > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > -- -Jesse W. |
From: Paul P. <mas...@gm...> - 2006-11-21 23:04:03
|
Jesse, I had the same question myself, so figured I'd investigate. Right after (er, may be downstream a few lines when booting) the "Not a PBA31307" message is a line showing all the bytes of the response. In the older thread, Ben had this in his line: 0x04 0x0e 0x08 0x01 0x05 0xfc 0x00 0x50 0x57 0x5b 0x05 ttyS3 hcidh4_recv: Mine said the same thing (rev 1170). so, resp[6] = 0x00 resp[7] = 0x50 resp[8] = 0x57 resp[9] = 0x5b resp[10] = 0x05 so, I changed that offending if statement (in the patch file) from if(resp[6] == 0x0 && (resp[7]&0xf) == 0x5 && resp[9] == 0x05) // PBA31307 confirmed To if(resp[6] == 0x0 && (resp[7]&0xf0) == 0x50 && resp[10] == 0x05) // PBA31307 confirmed This worked. Now, this is just guessing on my part on where the error is, and I'm not sure how minor revisions of the chip/firmware may affect these bytes. That may be why byte 7 was masked...? On that note, maybe the 'correct' fix would be: if(resp[6] == 0x0 && (resp[7]&0xf0) == 0x50 && (resp[9]&0xf0) == 0x50) // PBA31307 confirmed If anyone has more insight into this, that'd be great. I only know (from the comments in the patch) what the bytes represent (LM FW Version and BB FW Version). Regardless, it'd be nice to see this patched in the next revision. Now, if I could just figure out why the newer buildroot has much higher bluetooth latency than the older revisions... but, that's for another thread, after I get some more stats. --Paul Pigg On 11/21/06, Jesse Welling <jes...@gm... > wrote: > > Yes I recompiled the kernel but the *physical module* is the old > PBA31307 and not the new (RoHS compliant) PBA31308. > Problem is that the patch applied now makes the kernel > complain that it can't find the right bluetooth *physical module*. > > I guess I'm going to side skirt the issue by using r1155 of the build root > because it looks like the last one before the addition of the patch. > > To Craig: > Would droping in an old buez package directory (/trunk/package/bluez/) > from pre 1155 over the new > buildroot break any thing? > > On 11/21/06, Mario A. Spinthiras < ma...@ne...> wrote: > > > > Jesse Welling wrote: > > > Hi I was trying to update my kernal from 2.6.16 to 2.6.18 and I ran > > > into the PBA31308 vs PBA31307 problem > > > and my BlueTooth no longer works. Some one mentioned a fix but it was > > > kinda vague. It told > > > me what to change in the bluez-something-something-PBA31308.patch > > > (which I found) but not what to change it *to*... > > > can any one enlighten me? IIRC resp[6], resp[7] and resp[9] was > > > mentioned. Does any one know what those values should be? > > > Here is the error: > > > > > > Starting Bluetooth subsystem:Trying baud rate 57600... > > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > > Got response after reset... gobbling > > > No response from BT module > > > Trying baud rate 921600... > > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > > Got response after reset... gobbling > > > Error reading response: Success > > > Trying baud rate 115200... > > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > > Got response after reset... gobbling > > > Detected bluetooth module at 115200 baud > > > Got: status=0x00, hci_ver=0x01, hci_rev=0x0750, lmp_ver=0x02, > > > manuf=0x0009, lmp_subver=0x0750 > > > Not a PBA31307 > > > > > > > > > Thanks for the help! > > > > > > > > > -- > > > -Jesse W. > > > > > ------------------------------------------------------------------------ > > > > > > > > ------------------------------------------------------------------------- > > > Take Surveys. Earn Cash. Influence the Future of IT > > > Join SourceForge.net's Techsay panel and you'll get the chance to > > share your > > > opinions on IT & business topics through brief surveys - and earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > > > > > ------------------------------------------------------------------------ > > > > > > _______________________________________________ > > > gumstix-users mailing list > > > gum...@li... > > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > Kernel you mean ? > > > > Did you include the modules for your hw ? > > > > If not recompile with your hw supported modules. > > > > M. > > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net 's Techsay panel and you'll get the chance to share > > your > > opinions on IT & business topics through brief surveys - and earn cash > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > -- > -Jesse W. > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > |
From: Jesse W. <jes...@gm...> - 2006-11-21 23:39:16
|
hmmm.....I just compiled a current build root (r1174) but instead of using the patch form that revision I droped in the the bluez folder from r1155 and it built ok...so I'll test that tonight and see how it goes. On 11/21/06, Paul Pigg <mas...@gm...> wrote: > > Jesse, > > I had the same question myself, so figured I'd investigate. Right after > (er, may be downstream a few lines when booting) the "Not a PBA31307" > message is a line showing all the bytes of the response. In the older > thread, Ben had this in his line: > > 0x04 0x0e 0x08 0x01 0x05 0xfc 0x00 0x50 0x57 0x5b 0x05 ttyS3 hcidh4_recv: > Mine said the same thing (rev 1170). > > so, > resp[6] = 0x00 > resp[7] = 0x50 > resp[8] = 0x57 > resp[9] = 0x5b > resp[10] = 0x05 > > > so, I changed that offending if statement (in the patch file) from > > if(resp[6] == 0x0 && (resp[7]&0xf) == 0x5 && resp[9] == 0x05) // PBA31307 confirmed > > To > > if(resp[6] == 0x0 && (resp[7]&0xf0) == 0x50 && resp[10] == 0x05) // PBA31307 confirmed > > > This worked. > > Now, this is just guessing on my part on where the error is, and I'm not > sure how minor revisions of the chip/firmware may affect these bytes. That > may be why byte 7 was masked...? On that note, maybe the 'correct' fix > would be: > > if(resp[6] == 0x0 && (resp[7]&0xf0) == 0x50 && (resp[9]&0xf0) == 0x50) // PBA31307 confirmed > > > If anyone has more insight into this, that'd be great. I only know (from > the comments in the patch) what the bytes represent (LM FW Version and BB FW > Version). Regardless, it'd be nice to see this patched in the next > revision. Now, if I could just figure out why the newer buildroot has much > higher bluetooth latency than the older revisions... but, that's for another > thread, after I get some more stats. > > --Paul Pigg > > On 11/21/06, Jesse Welling <jes...@gm... > wrote: > > > > Yes I recompiled the kernel but the *physical module* is the old > > PBA31307 and not the new (RoHS compliant) PBA31308. > > Problem is that the patch applied now makes the kernel > > complain that it can't find the right bluetooth *physical module*. > > > > I guess I'm going to side skirt the issue by using r1155 of the build > > root > > because it looks like the last one before the addition of the patch. > > > > To Craig: > > Would droping in an old buez package directory (/trunk/package/bluez/) > > from pre 1155 over the new > > buildroot break any thing? > > > > On 11/21/06, Mario A. Spinthiras < ma...@ne...> wrote: > > > > > > Jesse Welling wrote: > > > > Hi I was trying to update my kernal from 2.6.16 to 2.6.18 and I ran > > > > into the PBA31308 vs PBA31307 problem > > > > and my BlueTooth no longer works. Some one mentioned a fix but it > > > was > > > > kinda vague. It told > > > > me what to change in the bluez-something-something-PBA31308.patch > > > > (which I found) but not what to change it *to*... > > > > can any one enlighten me? IIRC resp[6], resp[7] and resp[9] was > > > > mentioned. Does any one know what those values should be? > > > > Here is the error: > > > > > > > > Starting Bluetooth subsystem:Trying baud rate 57600... > > > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > > > Got response after reset... gobbling > > > > No response from BT module > > > > Trying baud rate 921600... > > > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > > > Got response after reset... gobbling > > > > Error reading response: Success > > > > Trying baud rate 115200... > > > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > > > Got response after reset... gobbling > > > > Detected bluetooth module at 115200 baud > > > > Got: status=0x00, hci_ver=0x01, hci_rev=0x0750, lmp_ver=0x02, > > > > manuf=0x0009, lmp_subver=0x0750 > > > > Not a PBA31307 > > > > > > > > > > > > Thanks for the help! > > > > > > > > > > > > -- > > > > -Jesse W. > > > > > > > ------------------------------------------------------------------------ > > > > > > > > > > > ------------------------------------------------------------------------- > > > > Take Surveys. Earn Cash. Influence the Future of IT > > > > Join SourceForge.net's Techsay panel and you'll get the chance to > > > share your > > > > opinions on IT & business topics through brief surveys - and earn > > > cash > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > > > _______________________________________________ > > > > gumstix-users mailing list > > > > gum...@li... > > > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > Kernel you mean ? > > > > > > Did you include the modules for your hw ? > > > > > > If not recompile with your hw supported modules. > > > > > > M. > > > > > > > > > ------------------------------------------------------------------------- > > > Take Surveys. Earn Cash. Influence the Future of IT > > > Join SourceForge.net 's Techsay panel and you'll get the chance to > > > share your > > > opinions on IT & business topics through brief surveys - and earn cash > > > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > _______________________________________________ > > > gumstix-users mailing list > > > gum...@li... > > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > > > > > -- > > -Jesse W. > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > > your > > opinions on IT & business topics through brief surveys - and earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > > > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > -- -Jesse W. |
From: Jesse W. <jes...@gm...> - 2006-11-22 10:29:45
|
OK replacing the new revision's bluez patching info with the old one's seems to work very well. That is to say, I haven't noticed any adverse effects yet. But I suspect it will only work as long as bluez doesn't change for the gumstix...so...it's a temp fix Any ways thanks for the info Paul. ps does this need to be wiki'd? On 11/21/06, Jesse Welling <jes...@gm...> wrote: > > hmmm.....I just compiled a current build root (r1174) but instead of using > the patch form that revision I droped in the > the bluez folder from r1155 and it built ok...so I'll test that tonight > and see how it goes. > > On 11/21/06, Paul Pigg <mas...@gm... > wrote: > > > > Jesse, > > > > I had the same question myself, so figured I'd investigate. Right after > > (er, may be downstream a few lines when booting) the "Not a PBA31307" > > message is a line showing all the bytes of the response. In the older > > thread, Ben had this in his line: > > > > 0x04 0x0e 0x08 0x01 0x05 0xfc 0x00 0x50 0x57 0x5b 0x05 ttyS3 > > hcidh4_recv: > > Mine said the same thing (rev 1170). > > > > so, > > resp[6] = 0x00 > > resp[7] = 0x50 > > resp[8] = 0x57 > > resp[9] = 0x5b > > resp[10] = 0x05 > > > > > > so, I changed that offending if statement (in the patch file) from > > > > if(resp[6] == 0x0 && (resp[7]&0xf) == 0x5 && resp[9] == 0x05) // PBA31307 confirmed > > > > To > > > > if(resp[6] == 0x0 && (resp[7]&0xf0) == 0x50 && resp[10] == 0x05) // PBA31307 confirmed > > > > > > > > > > This worked. > > > > Now, this is just guessing on my part on where the error is, and I'm not > > sure how minor revisions of the chip/firmware may affect these bytes. That > > may be why byte 7 was masked...? On that note, maybe the 'correct' fix > > would be: > > > > if(resp[6] == 0x0 && (resp[7]&0xf0) == 0x50 && (resp[9]&0xf0) == 0x50) // PBA31307 confirmed > > > > > > If anyone has more insight into this, that'd be great. I only know > > (from the comments in the patch) what the bytes represent (LM FW Version and > > BB FW Version). Regardless, it'd be nice to see this patched in the next > > revision. Now, if I could just figure out why the newer buildroot has much > > higher bluetooth latency than the older revisions... but, that's for another > > thread, after I get some more stats. > > > > --Paul Pigg > > > > On 11/21/06, Jesse Welling <jes...@gm... > wrote: > > > > > > Yes I recompiled the kernel but the *physical module* is the old > > > PBA31307 and not the new (RoHS compliant) PBA31308. > > > Problem is that the patch applied now makes the kernel > > > complain that it can't find the right bluetooth *physical module*. > > > > > > I guess I'm going to side skirt the issue by using r1155 of the build > > > root > > > because it looks like the last one before the addition of the patch. > > > > > > To Craig: > > > Would droping in an old buez package directory (/trunk/package/bluez/) > > > from pre 1155 over the new > > > buildroot break any thing? > > > > > > On 11/21/06, Mario A. Spinthiras < ma...@ne...> wrote: > > > > > > > > Jesse Welling wrote: > > > > > Hi I was trying to update my kernal from 2.6.16 to 2.6.18 and I > > > > ran > > > > > into the PBA31308 vs PBA31307 problem > > > > > and my BlueTooth no longer works. Some one mentioned a fix but it > > > > was > > > > > kinda vague. It told > > > > > me what to change in the bluez-something-something-PBA31308.patch > > > > > (which I found) but not what to change it *to*... > > > > > can any one enlighten me? IIRC resp[6], resp[7] and resp[9] was > > > > > mentioned. Does any one know what those values should be? > > > > > Here is the error: > > > > > > > > > > Starting Bluetooth subsystem:Trying baud rate 57600... > > > > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > > > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > > > > Got response after reset... gobbling > > > > > No response from BT module > > > > > Trying baud rate 921600... > > > > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > > > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > > > > Got response after reset... gobbling > > > > > Error reading response: Success > > > > > Trying baud rate 115200... > > > > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > > > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > > > > Got response after reset... gobbling > > > > > Detected bluetooth module at 115200 baud > > > > > Got: status=0x00, hci_ver=0x01, hci_rev=0x0750, lmp_ver=0x02, > > > > > manuf=0x0009, lmp_subver=0x0750 > > > > > Not a PBA31307 > > > > > > > > > > > > > > > Thanks for the help! > > > > > > > > > > > > > > > -- > > > > > -Jesse W. > > > > > > > > > ------------------------------------------------------------------------ > > > > > > > > > > > > > > ------------------------------------------------------------------------- > > > > > Take Surveys. Earn Cash. Influence the Future of IT > > > > > Join SourceForge.net's Techsay panel and you'll get the chance to > > > > share your > > > > > opinions on IT & business topics through brief surveys - and earn > > > > cash > > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > > > > > _______________________________________________ > > > > > gumstix-users mailing list > > > > > gum...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > > > Kernel you mean ? > > > > > > > > Did you include the modules for your hw ? > > > > > > > > If not recompile with your hw supported modules. > > > > > > > > M. > > > > > > > > > > > > ------------------------------------------------------------------------- > > > > Take Surveys. Earn Cash. Influence the Future of IT > > > > Join SourceForge.net 's Techsay panel and you'll get the chance to > > > > share your > > > > opinions on IT & business topics through brief surveys - and earn > > > > cash > > > > > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > > _______________________________________________ > > > > gumstix-users mailing list > > > > gum...@li... > > > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > > > > > > > > > > -- > > > -Jesse W. > > > > > > ------------------------------------------------------------------------- > > > Take Surveys. Earn Cash. Influence the Future of IT > > > Join SourceForge.net's Techsay panel and you'll get the chance to > > > share your > > > opinions on IT & business topics through brief surveys - and earn cash > > > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > > > > > > > _______________________________________________ > > > gumstix-users mailing list > > > gum...@li... > > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > > > > > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > > your > > opinions on IT & business topics through brief surveys - and earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > > > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > > > -- > -Jesse W. > -- -Jesse W. |
From: Craig H. <cr...@gu...> - 2006-11-23 01:06:42
|
My bad -- I misread the data sheet. It says that the response there should be: LM-FW-Version: 2 bytes -- 0xynnn where y=0x5 for bluemoon single cellular (ie the pba31307) and the 3 subsequent 'nnn' hex digits are revision number, subrev number, and subsubrev number. ie in this case, 0x5750 means version 7.5.0 of the bluemoon firmware. BB-FW-Version: 2 bytes -- 0xyynn where yy is chip revision number = 0x05 and nn is rev/subrev number. So this is showing revision 5.11 of the baseband firmware I think... So the correct test is: > if(resp[6] == 0x0 && (resp[8]&0xf0) == 0x50 && resp[10] == 0x05) // > PBA31307 confirmed I'll fix this in the buildroot now.... C On Nov 21, 2006, at 3:04 PM, Paul Pigg wrote: > Jesse, > > I had the same question myself, so figured I'd investigate. Right > after (er, may be downstream a few lines when booting) the "Not a > PBA31307" message is a line showing all the bytes of the response. > In the older thread, Ben had this in his line: > > 0x04 0x0e 0x08 0x01 0x05 0xfc 0x00 0x50 0x57 0x5b 0x05 ttyS3 > hcidh4_recv: > Mine said the same thing (rev 1170). > > so, > resp[6] = 0x00 > resp[7] = 0x50 > resp[8] = 0x57 > resp[9] = 0x5b > resp[10] = 0x05 > > > so, I changed that offending if statement (in the patch file) from > > if(resp[6] == 0x0 && (resp[7]&0xf) == 0x5 && resp[9] == 0x05) // > PBA31307 confirmed > > To > if(resp[6] == 0x0 && (resp[7]&0xf0) == 0x50 && resp[10] == 0x05) // > PBA31307 confirmed > > > This worked. > > Now, this is just guessing on my part on where the error is, and > I'm not sure how minor revisions of the chip/firmware may affect > these bytes. That may be why byte 7 was masked...? On that note, > maybe the 'correct' fix would be: > if(resp[6] == 0x0 && (resp[7]&0xf0) == 0x50 && (resp[9]&0xf0) == > 0x50) // PBA31307 confirmed > > If anyone has more insight into this, that'd be great. I only know > (from the comments in the patch) what the bytes represent (LM FW > Version and BB FW Version). Regardless, it'd be nice to see this > patched in the next revision. Now, if I could just figure out why > the newer buildroot has much higher bluetooth latency than the > older revisions... but, that's for another thread, after I get some > more stats. > > --Paul Pigg > > On 11/21/06, Jesse Welling <jes...@gm... > wrote: > Yes I recompiled the kernel but the *physical module* is the old > PBA31307 and not the new (RoHS compliant) PBA31308. > Problem is that the patch applied now makes the kernel > complain that it can't find the right bluetooth *physical module*. > > I guess I'm going to side skirt the issue by using r1155 of the > build root > because it looks like the last one before the addition of the patch. > > To Craig: > Would droping in an old buez package directory (/trunk/package/ > bluez/) from pre 1155 over the new > buildroot break any thing? > > > On 11/21/06, Mario A. Spinthiras < ma...@ne...> wrote: > Jesse Welling wrote: > > Hi I was trying to update my kernal from 2.6.16 to 2.6.18 and I ran > > into the PBA31308 vs PBA31307 problem > > and my BlueTooth no longer works. Some one mentioned a fix but it > was > > kinda vague. It told > > me what to change in the bluez-something-something-PBA31308.patch > > (which I found) but not what to change it *to*... > > can any one enlighten me? IIRC resp[6], resp[7] and resp[9] was > > mentioned. Does any one know what those values should be? > > Here is the error: > > > > Starting Bluetooth subsystem:Trying baud rate 57600... > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > Got response after reset... gobbling > > No response from BT module > > Trying baud rate 921600... > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > Got response after reset... gobbling > > Error reading response: Success > > Trying baud rate 115200... > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > Got response after reset... gobbling > > Detected bluetooth module at 115200 baud > > Got: status=0x00, hci_ver=0x01, hci_rev=0x0750, lmp_ver=0x02, > > manuf=0x0009, lmp_subver=0x0750 > > Not a PBA31307 > > > > > > Thanks for the help! > > > > > > -- > > -Jesse W. > > > ---------------------------------------------------------------------- > -- > > > > > ---------------------------------------------------------------------- > --- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > > opinions on IT & business topics through brief surveys - and earn > cash > > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > > > ---------------------------------------------------------------------- > -- > > > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > Kernel you mean ? > > Did you include the modules for your hw ? > > If not recompile with your hw supported modules. > > M. > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net 's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > -- > -Jesse W. > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV________________________________ > _______________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Jesse W. <jes...@gm...> - 2006-11-23 10:28:14
|
Tried the r1176 today and it still came up with this: Initializing random number generator... done. Starting 32kHz clock...Settled Set (AF1,out,set) via /proc/gpio/GPIO12 Starting Bluetooth subsystem:Trying baud rate 57600... Set (GPIO,out,clear) via /proc/gpio/GPIO7 Set (GPIO,out,set) via /proc/gpio/GPIO7 Got response after reset... gobbling No response from BT module Trying baud rate 921600... Set (GPIO,out,clear) via /proc/gpio/GPIO7 Set (GPIO,out,set) via /proc/gpio/GPIO7 Got response after reset... gobbling Error reading response: Success Trying baud rate 115200... Set (GPIO,out,clear) via /proc/gpio/GPIO7 Set (GPIO,out,set) via /proc/gpio/GPIO7 Got response after reset... gobbling Detected bluetooth module at 115200 baud Got: status=0x00, hci_ver=0x01, hci_rev=0x0750, lmp_ver=0x02, manuf=0x0009, lmp_subver=0x0750 Not a PBA31307 Bluetooth: Core ver 2.10 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: HCI UART driver ver 2.2 Bluetooth: HCI H4 protocol initialized 0x04 0x0e 0x08 0x01 0x05 0xfc 0x00 0x50 0x57 0x5b 0x05 ttyS3 hcidh4_recv: Unknown HCI packet type 00 h4_recv: Unknown HCI packet type 00 h4_recv: Unknown HCI packet type 00 h4_recv: Unknown HCI packet type 00 h4_recv: Unknown HCI packet type 80 h4_recv: Unknown HCI packet type 00 h4_recv: Unknown HCI packet type 80 h4_recv: Unknown HCI packet type 00 Bluetooth: L2CAP ver 2.8 Bluetooth: L2CAP socket layer initialized sdpd rfcommBluetooth: BNEP (Ethernet Emulation) ver 1.2 pand. Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.8 I'm not quite sure what the discrepancy is but my resp[9] is 0x5b (I'm assuming 0 bassed array) and this is what was commited: *if(resp[6] == 0x0 && (resp[7]&0xf0) == 0x50 && resp[9] == 0x05) // PBA31307 confirmed * I think you maybe meant to put in resp[10] ? Unless I jumped the gun and r1176 wasn't the fix i was hoping for? So by now I'm a little confused (without the datasheet to look at), which responses need checking and what should they be? I guess for now I'm just going to assume that resp[9]==0x05 needs to be resp[10]==0x05. ** ** On 11/22/06, Craig Hughes < cr...@gu...> wrote: > > My bad -- I misread the data sheet. It says that the response there > should be: > LM-FW-Version: 2 bytes -- 0xynnn where y=0x5 for bluemoon single cellular > (ie the pba31307) and the 3 subsequent 'nnn' hex digits are revision number, > subrev number, and subsubrev number. ie in this case, 0x5750 means version > 7.5.0 of the bluemoon firmware. > BB-FW-Version: 2 bytes -- 0xyynn where yy is chip revision number = 0x05 > and nn is rev/subrev number. So this is showing revision 5.11 of the > baseband firmware I think... > > So the correct test is: > > if(resp[6] == 0x0 && (resp[8]&0xf0) == 0x50 && resp[10] == 0x05) // PBA31307 confirmed > > I'll fix this in the buildroot now.... > > C > > On Nov 21, 2006, at 3:04 PM, Paul Pigg wrote: > > Jesse, > > I had the same question myself, so figured I'd investigate. Right after > (er, may be downstream a few lines when booting) the "Not a PBA31307" > message is a line showing all the bytes of the response. In the older > thread, Ben had this in his line: > > 0x04 0x0e 0x08 0x01 0x05 0xfc 0x00 0x50 0x57 0x5b 0x05 ttyS3 hcidh4_recv: > Mine said the same thing (rev 1170). > > so, > resp[6] = 0x00 > resp[7] = 0x50 > resp[8] = 0x57 > resp[9] = 0x5b > resp[10] = 0x05 > > > so, I changed that offending if statement (in the patch file) from > > if(resp[6] == 0x0 && (resp[7]&0xf) == 0x5 && resp[9] == 0x05) // PBA31307 confirmed > > To > > if(resp[6] == 0x0 && (resp[7]&0xf0) == 0x50 && resp[10] == 0x05) // PBA31307 confirmed > > > This worked. > > Now, this is just guessing on my part on where the error is, and I'm not > sure how minor revisions of the chip/firmware may affect these bytes. That > may be why byte 7 was masked...? On that note, maybe the 'correct' fix > would be: > > if(resp[6] == 0x0 && (resp[7]&0xf0) == 0x50 && (resp[9]&0xf0) == 0x50) // PBA31307 confirmed > > > If anyone has more insight into this, that'd be great. I only know (from > the comments in the patch) what the bytes represent (LM FW Version and BB FW > Version). Regardless, it'd be nice to see this patched in the next > revision. Now, if I could just figure out why the newer buildroot has much > higher bluetooth latency than the older revisions... but, that's for another > thread, after I get some more stats. > > --Paul Pigg > > On 11/21/06, Jesse Welling < jes...@gm... > wrote: > > > > Yes I recompiled the kernel but the *physical module* is the old > > PBA31307 and not the new (RoHS compliant) PBA31308. > > Problem is that the patch applied now makes the kernel > > complain that it can't find the right bluetooth *physical module*. > > > > I guess I'm going to side skirt the issue by using r1155 of the build > > root > > because it looks like the last one before the addition of the patch. > > > > To Craig: > > Would droping in an old buez package directory (/trunk/package/bluez/) > > from pre 1155 over the new > > buildroot break any thing? > > > > On 11/21/06, Mario A. Spinthiras < ma...@ne...> wrote: > > > > > > Jesse Welling wrote: > > > > Hi I was trying to update my kernal from 2.6.16 to 2.6.18 and I ran > > > > into the PBA31308 vs PBA31307 problem > > > > and my BlueTooth no longer works. Some one mentioned a fix but it > > > was > > > > kinda vague. It told > > > > me what to change in the bluez-something-something-PBA31308.patch > > > > (which I found) but not what to change it *to*... > > > > can any one enlighten me? IIRC resp[6], resp[7] and resp[9] was > > > > mentioned. Does any one know what those values should be? > > > > Here is the error: > > > > > > > > Starting Bluetooth subsystem:Trying baud rate 57600... > > > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > > > Got response after reset... gobbling > > > > No response from BT module > > > > Trying baud rate 921600... > > > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > > > Got response after reset... gobbling > > > > Error reading response: Success > > > > Trying baud rate 115200... > > > > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > > > > Set (GPIO,out,set) via /proc/gpio/GPIO7 > > > > Got response after reset... gobbling > > > > Detected bluetooth module at 115200 baud > > > > Got: status=0x00, hci_ver=0x01, hci_rev=0x0750, lmp_ver=0x02, > > > > manuf=0x0009, lmp_subver=0x0750 > > > > Not a PBA31307 > > > > > > > > > > > > Thanks for the help! > > > > > > > > > > > > -- > > > > -Jesse W. > > > > > > > ------------------------------------------------------------------------ > > > > > > > > > > > ------------------------------------------------------------------------- > > > > Take Surveys. Earn Cash. Influence the Future of IT > > > > Join SourceForge.net's Techsay panel and you'll get the chance to > > > share your > > > > opinions on IT & business topics through brief surveys - and earn > > > cash > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > > > _______________________________________________ > > > > gumstix-users mailing list > > > > gum...@li... > > > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > Kernel you mean ? > > > > > > Did you include the modules for your hw ? > > > > > > If not recompile with your hw supported modules. > > > > > > M. > > > > > > ------------------------------------------------------------------------- > > > > > > Take Surveys. Earn Cash. Influence the Future of IT > > > Join SourceForge.net 's Techsay panel and you'll get the chance to > > > share your > > > opinions on IT & business topics through brief surveys - and earn cash > > > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > _______________________________________________ > > > gumstix-users mailing list > > > gum...@li... > > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > > > > > -- > > -Jesse W. > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > > your > > opinions on IT & business topics through brief surveys - and earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > > > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV_______________________________________________ > > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > -- -Jesse W. |
From: Craig H. <cr...@gu...> - 2006-11-27 18:50:08
|
Hmm, you're quite right, it should be [10] not [9] -- I could swear I'd typed [10], and tested it; maybe I then "cleaned up" the line or something before committing the patch? In any case, I'll fix it. C On Nov 23, 2006, at 2:28 AM, Jesse Welling wrote: > Tried the r1176 today and it still came up with this: > > Initializing random number generator... done. > Starting 32kHz clock...Settled > Set (AF1,out,set) via /proc/gpio/GPIO12 > Starting Bluetooth subsystem:Trying baud rate 57600... > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > Set (GPIO,out,set) via /proc/gpio/GPIO7 > Got response after reset... gobbling > No response from BT module > Trying baud rate 921600... > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > Set (GPIO,out,set) via /proc/gpio/GPIO7 > Got response after reset... gobbling > Error reading response: Success > Trying baud rate 115200... > Set (GPIO,out,clear) via /proc/gpio/GPIO7 > Set (GPIO,out,set) via /proc/gpio/GPIO7 > Got response after reset... gobbling > Detected bluetooth module at 115200 baud > Got: status=0x00, hci_ver=0x01, hci_rev=0x0750, lmp_ver=0x02, > manuf=0x0009, lmp_subver=0x0750 > Not a PBA31307 > Bluetooth: Core ver 2.10 > NET: Registered protocol family 31 > Bluetooth: HCI device and connection manager initialized > Bluetooth: HCI socket layer initialized > Bluetooth: HCI UART driver ver 2.2 > Bluetooth: HCI H4 protocol initialized > 0x04 0x0e 0x08 0x01 0x05 0xfc 0x00 0x50 0x57 0x5b 0x05 ttyS3 > hcidh4_recv: Unknown HCI packet type 00 > h4_recv: Unknown HCI packet type 00 > h4_recv: Unknown HCI packet type 00 > h4_recv: Unknown HCI packet type 00 > h4_recv: Unknown HCI packet type 80 > h4_recv: Unknown HCI packet type 00 > h4_recv: Unknown HCI packet type 80 > h4_recv: Unknown HCI packet type 00 > Bluetooth: L2CAP ver 2.8 > Bluetooth: L2CAP socket layer initialized > sdpd rfcommBluetooth: BNEP (Ethernet Emulation) ver 1.2 > pand. > Bluetooth: RFCOMM socket layer initialized > Bluetooth: RFCOMM TTY layer initialized > Bluetooth: RFCOMM ver 1.8 > > > > I'm not quite sure what the discrepancy is but my resp[9] is 0x5b > (I'm assuming 0 bassed array) > and this is what was commited: > if(resp[6] == 0x0 && (resp[7]&0xf0) == 0x50 && resp[9] == 0x05) // > PBA31307 confirmed > I think you maybe meant to put in resp[10] ? > Unless I jumped the gun and r1176 wasn't the fix i was hoping for? > > So by now I'm a little confused (without the datasheet to look at), > which responses need checking and what should they be? > I guess for now I'm just going to assume that resp[9]==0x05 needs > to be resp[10]==0x05. > > On 11/22/06, Craig Hughes < cr...@gu...> wrote: > My bad -- I misread the data sheet. It says that the response > there should be: > > LM-FW-Version: 2 bytes -- 0xynnn where y=0x5 for bluemoon single > cellular (ie the pba31307) and the 3 subsequent 'nnn' hex digits > are revision number, subrev number, and subsubrev number. ie in > this case, 0x5750 means version 7.5.0 of the bluemoon firmware. > BB-FW-Version: 2 bytes -- 0xyynn where yy is chip revision number = > 0x05 and nn is rev/subrev number. So this is showing revision 5.11 > of the baseband firmware I think... > > So the correct test is: > >> if(resp[6] == 0x0 && (resp[8]&0xf0) == 0x50 && resp[10] == >> 0x05) // PBA31307 confirmed > I'll fix this in the buildroot now.... > > C > > On Nov 21, 2006, at 3:04 PM, Paul Pigg wrote: > >> Jesse, >> >> I had the same question myself, so figured I'd investigate. Right >> after (er, may be downstream a few lines when booting) the "Not a >> PBA31307" message is a line showing all the bytes of the >> response. In the older thread, Ben had this in his line: >> >> 0x04 0x0e 0x08 0x01 0x05 0xfc 0x00 0x50 0x57 0x5b 0x05 ttyS3 >> hcidh4_recv: >> Mine said the same thing (rev 1170). >> >> so, >> resp[6] = 0x00 >> resp[7] = 0x50 >> resp[8] = 0x57 >> resp[9] = 0x5b >> resp[10] = 0x05 >> >> >> so, I changed that offending if statement (in the patch file) from >> >> if(resp[6] == 0x0 && (resp[7]&0xf) == 0x5 && resp[9] == 0x05) // >> PBA31307 confirmed >> >> To >> if(resp[6] == 0x0 && (resp[7]&0xf0) == 0x50 && resp[10] == >> 0x05) // PBA31307 confirmed >> >> >> This worked. >> >> Now, this is just guessing on my part on where the error is, and >> I'm not sure how minor revisions of the chip/firmware may affect >> these bytes. That may be why byte 7 was masked...? On that note, >> maybe the 'correct' fix would be: >> if(resp[6] == 0x0 && (resp[7]&0xf0) == 0x50 && (resp[9]&0xf0) == >> 0x50) // PBA31307 confirmed >> >> If anyone has more insight into this, that'd be great. I only >> know (from the comments in the patch) what the bytes represent (LM >> FW Version and BB FW Version). Regardless, it'd be nice to see >> this patched in the next revision. Now, if I could just figure >> out why the newer buildroot has much higher bluetooth latency than >> the older revisions... but, that's for another thread, after I get >> some more stats. >> >> --Paul Pigg >> >> On 11/21/06, Jesse Welling < jes...@gm... > wrote: >> Yes I recompiled the kernel but the *physical module* is the old >> PBA31307 and not the new (RoHS compliant) PBA31308. >> Problem is that the patch applied now makes the kernel >> complain that it can't find the right bluetooth *physical module*. >> >> I guess I'm going to side skirt the issue by using r1155 of the >> build root >> because it looks like the last one before the addition of the patch. >> >> To Craig: >> Would droping in an old buez package directory (/trunk/package/ >> bluez/) from pre 1155 over the new >> buildroot break any thing? >> >> >> On 11/21/06, Mario A. Spinthiras < ma...@ne...> wrote: >> Jesse Welling wrote: >> > Hi I was trying to update my kernal from 2.6.16 to 2.6.18 and I ran >> > into the PBA31308 vs PBA31307 problem >> > and my BlueTooth no longer works. Some one mentioned a fix but >> it was >> > kinda vague. It told >> > me what to change in the bluez-something-something-PBA31308.patch >> > (which I found) but not what to change it *to*... >> > can any one enlighten me? IIRC resp[6], resp[7] and resp[9] was >> > mentioned. Does any one know what those values should be? >> > Here is the error: >> > >> > Starting Bluetooth subsystem:Trying baud rate 57600... >> > Set (GPIO,out,clear) via /proc/gpio/GPIO7 >> > Set (GPIO,out,set) via /proc/gpio/GPIO7 >> > Got response after reset... gobbling >> > No response from BT module >> > Trying baud rate 921600... >> > Set (GPIO,out,clear) via /proc/gpio/GPIO7 >> > Set (GPIO,out,set) via /proc/gpio/GPIO7 >> > Got response after reset... gobbling >> > Error reading response: Success >> > Trying baud rate 115200... >> > Set (GPIO,out,clear) via /proc/gpio/GPIO7 >> > Set (GPIO,out,set) via /proc/gpio/GPIO7 >> > Got response after reset... gobbling >> > Detected bluetooth module at 115200 baud >> > Got: status=0x00, hci_ver=0x01, hci_rev=0x0750, lmp_ver=0x02, >> > manuf=0x0009, lmp_subver=0x0750 >> > Not a PBA31307 >> > >> > >> > Thanks for the help! >> > >> > >> > -- >> > -Jesse W. >> > >> --------------------------------------------------------------------- >> --- >> > >> > >> --------------------------------------------------------------------- >> ---- >> > Take Surveys. Earn Cash. Influence the Future of IT >> > Join SourceForge.net's Techsay panel and you'll get the chance >> to share your >> > opinions on IT & business topics through brief surveys - and >> earn cash >> > http://www.techsay.com/default.php? >> page=join.php&p=sourceforge&CID=DEVDEV >> > >> --------------------------------------------------------------------- >> --- >> > >> > _______________________________________________ >> > gumstix-users mailing list >> > gum...@li... >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > >> Kernel you mean ? >> >> Did you include the modules for your hw ? >> >> If not recompile with your hw supported modules. >> >> M. >> >> --------------------------------------------------------------------- >> ---- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net 's Techsay panel and you'll get the chance to >> share your >> opinions on IT & business topics through brief surveys - and earn >> cash >> http://www.techsay.com/default.php? >> page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> >> -- >> -Jesse W. >> --------------------------------------------------------------------- >> ---- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to >> share your >> opinions on IT & business topics through brief surveys - and earn >> cash >> http://www.techsay.com/default.php? >> page=join.php&p=sourceforge&CID=DEVDEV >> >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> >> --------------------------------------------------------------------- >> ---- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to >> share your >> opinions on IT & business topics through brief surveys - and earn >> cash >> http://www.techsay.com/default.php? >> page=join.php&p=sourceforge&CID=DEVDEV_______________________________ >> ________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > -- > -Jesse W. > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV________________________________ > _______________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |