From: Linus C. <li...@li...> - 2007-09-05 00:08:01
|
It was working until I reboot. # /etc/init.d/S30bluetooth start Starting 32kHz clock...Settled Starting Bluetooth subsystem:Trying baud rate 115200... Got response after reset... gobbling No response from BT module Trying baud rate 921600... Got response after reset... gobbling No response from BT module Trying baud rate 115200... Got response after reset... gobbling No response from BT module Trying baud rate 57600... Got response after reset... gobbling No response from BT module Can't initialize device: Success # What can I do? |
From: Linus C. <li...@li...> - 2007-09-05 02:08:57
|
Sorry for the pore information. I have 2 verdex with a tweener each. In both verdex I had: Starting 32kHz clock...Settled Starting Bluetooth subsystem:Trying baud rate 115200... No response after reset No response from BT module Trying baud rate 921600... No response after reset No response from BT module Trying baud rate 115200... No response after reset No response from BT module Trying baud rate 57600... No response after reset No response from BT module Can't initialize device: Success So I put in /etc/init.d/S30bluetooth in the start section: echo "AF1 in" >/proc/gpio/GPIO42 echo "AF2 out" >/proc/gpio/GPIO43 echo "AF1 in" >/proc/gpio/GPIO44 echo "AF2 out" >/proc/gpio/GPIO45 In one verdex (lets name it verdex A) I get: # /etc/init.d/S30bluetooth start Starting 32kHz clock...Settled Starting Bluetooth subsystem:Trying baud rate 115200... No response after reset Read wrong response size: 5 0x04 0xff 0x02 0x05 0x01 Trying baud rate 921600... No response after reset No response from BT module Trying baud rate 115200... No response after reset Read wrong response size: 5 0x04 0xff 0x02 0x05 0x01 Trying baud rate 57600... No response after reset Initialization timed out. And in verdex B it work very well yesterday. I could enter the console with ssh without any problems. And today when I turn it on: # /etc/init.d/S30bluetooth start Starting 32kHz clock...Settled Starting Bluetooth subsystem:Trying baud rate 115200... Got response after reset... gobbling No response from BT module Trying baud rate 921600... Got response after reset... gobbling No response from BT module Trying baud rate 115200... Got response after reset... gobbling No response from BT module Trying baud rate 57600... Got response after reset... gobbling No response from BT module Can't initialize device: Success :/ I tried building r1482 and I get the same thing. Sorry about my English. On 9/4/07, Mark Ahlenius - comcast <m_a...@co...> wrote: > > Hi, > > question - how did you get BT to start working in the first place? What proc card, a verdex? > > thx > > 'mark > > Linus Casassa wrote: > > > It was working until I reboot. > > # /etc/init.d/S30bluetooth start > Starting 32kHz clock...Settled > Starting Bluetooth subsystem:Trying baud rate 115200... > Got response after reset... gobbling > No response from BT module > Trying baud rate 921600... > Got response after reset... gobbling > No response from BT module > Trying baud rate 115200... > Got response after reset... gobbling > No response from BT module > Trying baud rate 57600... > Got response after reset... gobbling > No response from BT module > Can't initialize device: Success > # > > > What can I do? > ________________________________ > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ________________________________ > _______________________________________________ > gumstix-users mailing list > gum...@li... > > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Tim R. <gu...@ec...> - 2007-09-05 09:36:05
|
hello.. I just made buildroot 1420 to try and get a working bluetooth setup. I'm a bit baffled by the fact that no uImage file has been created- so I can't follow the instructions for replacing the filing system- and now I have flashed the file system I am getting a 'bad magic number' as the kernel and filing system mismatch. Is there an older system for replacing the kernel that predates the 'uImage' file method? Thanks... |
From: Dave H. <dhy...@gm...> - 2007-09-05 14:19:02
|
HI Tim, > I just made buildroot 1420 to try and get a working bluetooth setup. > > I'm a bit baffled by the fact that no uImage file has been created- so I > can't follow the instructions for replacing the filing system- and now I > have flashed the file system I am getting a 'bad magic number' as the > kernel and filing system mismatch. > > Is there an older system for replacing the kernel that predates the > 'uImage' file method? Prior to the verdex merge, there were only two files - u-boot.bin and rootfs. The uImage file is contained within the rootfs. This means that the u-boot command to boot the kernel is a little different (IIRC it used fsload whereas the new one uses katload). The older instructions go something like this: Load the rootfs into memory (This example uses MMC card) mmcinit fatload mmc 0 a2000000 rootfs.arm_nofpu.jffs2 Then you erase the flash, and copy the image in memory into flash: protect on 1:0-1 jerase all cp.b a2000000 40000 ${filesize} I normally use the reset command. Depending on which version of buildroot you had installed prior to installing 1421, you may need to tweak the bootargs environment variable in u-boot as well. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Tim R. <gu...@ec...> - 2007-10-15 13:47:01
|
Hi all, I wonder if anyone has any success stories using bluetooth with a version of the buildroot newer than 1161 (the one that currently ships). A gumstix newbie., I am trying to build an application for connex 400, that uses bluetooth and audio. I made the initial mistake of flashing the gumstix to a new buildroot- before realising that bluez is unconfigured at the moment. Craig from gumstix advised me to use buildroot 1161 (the one that currently ships with gumstix), all fine, OSS audio & bluetooth work here, I thought this was the solution. However buildroot 1161 has something weird with the ALSA libraries, they are not downloaded into the root even when selected... so I'm back looking to use or make a buildroot with audio and bluetooth. I looked at the change log and I though that 1499 might be a good one, as changes were make to fold in a new bluez on 1500 and 1504 I think I've built 1499, all good, alsa libraries are there... However when I install it I'm back to the bluetooth hardware not being detected. The familiar old: Starting Bluetooth subsystem:Trying baud rate 115200... Got response after reset... gobbling No response from BT module Trying baud rate 921600... No response after reset No response from BT module Trying baud rate 115200... No response after reset No response from BT module Trying baud rate 57600... No response after reset No response from BT module Does anyone know what causes this? I know my bluetooth hardware is ok, it works with buildroot 1161. Does anyone know how to reconfigure bluez in the newer buildroots, or is anyone using bluetooth who could tell me what buildroot they are using? (1161 is the ONLY buildroot I've found where the bluetooth is configured to work). Regards Tim |
From: Dan G. <djg...@go...> - 2007-10-15 14:30:05
|
I am using buildroot 1482, on 3 different boards and have managed to get bluetooth working on all. The boards are * Old Connex (PBA...7 Bluetooth Module) * New Connex (PBA...8 Bluetooth Module) * Verdex. The fix was eventually reasonably simple (after much pi**ing around with GPIO settings etc), someone suggested this solution. put these four lines echo "AF1 in" >/proc/gpio/GPIO42 echo "AF2 out" >/proc/gpio/GPIO43 echo "AF1 in" >/proc/gpio/GPIO44 echo "AF2 out" >/proc/gpio/GPIO45 in this file: /etc/init.d/S30bluetooth , in the start "stanza" after the modprobe of gumstix_bluetooth and proc_gpio. This has appeared to fix all my bluetooth problems. On 10/15/07, Tim Redfern <gu...@ec...> wrote: > Hi all, I wonder if anyone has any success stories using bluetooth with > a version of the buildroot newer than 1161 (the one that currently ships). > > A gumstix newbie., I am trying to build an application for connex 400, > that uses bluetooth and audio. I made the initial mistake of flashing > the gumstix to a new buildroot- before realising that bluez is > unconfigured at the moment. > > Craig from gumstix advised me to use buildroot 1161 (the one that > currently ships with gumstix), all fine, OSS audio & bluetooth work > here, I thought this was the solution. > > However buildroot 1161 has something weird with the ALSA libraries, they > are not downloaded into the root even when selected... so I'm back > looking to use or make a buildroot with audio and bluetooth. > > I looked at the change log and I though that 1499 might be a good one, > as changes were make to fold in a new bluez on 1500 and 1504 I think > > I've built 1499, all good, alsa libraries are there... > > However when I install it I'm back to the bluetooth hardware not being > detected. The familiar old: > > Starting Bluetooth subsystem:Trying baud rate 115200... > Got response after reset... gobbling > No response from BT module > Trying baud rate 921600... > No response after reset > No response from BT module > Trying baud rate 115200... > No response after reset > No response from BT module > Trying baud rate 57600... > No response after reset > No response from BT module > > Does anyone know what causes this? I know my bluetooth hardware is ok, > it works with buildroot 1161. Does anyone know how to reconfigure bluez > in the newer buildroots, or is anyone using bluetooth who could tell me > what buildroot they are using? (1161 is the ONLY buildroot I've found > where the bluetooth is configured to work). > > Regards > > Tim > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Tim R. <gu...@ec...> - 2007-10-15 15:48:09
|
hi. thanks.. tried that... no joy. same error messages and # hcitool dev Devices: # I will try 1482. I actually went throught the S30bluetooth startup script from build 1161 and the one difference that I could find is this: as you say, in the stanza 'start' it says: echo AF1 out > /proc/gpio/GPIO12 I tried this as well, no joy. Does anyone know what else would be different in the bluetooth subsystems between 1161 and any of these newer buildroots? Or is it a different version of the software altogether? Could there be a difference between my gumstix and the ones that these GPIO settings work for? Is there a way to find out what GPIO line is actually connected to your bluetooth chip? Tim >I am using buildroot 1482, on 3 different boards and have managed to >get bluetooth working on all. > >The boards are > * Old Connex (PBA...7 Bluetooth Module) > * New Connex (PBA...8 Bluetooth Module) > * Verdex. > >The fix was eventually reasonably simple (after much pi**ing around >with GPIO settings etc), someone suggested this solution. > >put these four lines > >echo "AF1 in" >/proc/gpio/GPIO42 >echo "AF2 out" >/proc/gpio/GPIO43 >echo "AF1 in" >/proc/gpio/GPIO44 >echo "AF2 out" >/proc/gpio/GPIO45 > >in this file: /etc/init.d/S30bluetooth , in the start "stanza" after >the modprobe of gumstix_bluetooth and proc_gpio. > >This has appeared to fix all my bluetooth problems. > >On 10/15/07, Tim Redfern <gu...@ec...> wrote: > > >>Hi all, I wonder if anyone has any success stories using bluetooth with >>a version of the buildroot newer than 1161 (the one that currently ships). >> >>A gumstix newbie., I am trying to build an application for connex 400, >>that uses bluetooth and audio. I made the initial mistake of flashing >>the gumstix to a new buildroot- before realising that bluez is >>unconfigured at the moment. >> >>Craig from gumstix advised me to use buildroot 1161 (the one that >>currently ships with gumstix), all fine, OSS audio & bluetooth work >>here, I thought this was the solution. >> >>However buildroot 1161 has something weird with the ALSA libraries, they >>are not downloaded into the root even when selected... so I'm back >>looking to use or make a buildroot with audio and bluetooth. >> >>I looked at the change log and I though that 1499 might be a good one, >>as changes were make to fold in a new bluez on 1500 and 1504 I think >> >>I've built 1499, all good, alsa libraries are there... >> >>However when I install it I'm back to the bluetooth hardware not being >>detected. The familiar old: >> >>Starting Bluetooth subsystem:Trying baud rate 115200... >>Got response after reset... gobbling >>No response from BT module >>Trying baud rate 921600... >>No response after reset >>No response from BT module >>Trying baud rate 115200... >>No response after reset >>No response from BT module >>Trying baud rate 57600... >>No response after reset >>No response from BT module >> >>Does anyone know what causes this? I know my bluetooth hardware is ok, >>it works with buildroot 1161. Does anyone know how to reconfigure bluez >>in the newer buildroots, or is anyone using bluetooth who could tell me >>what buildroot they are using? (1161 is the ONLY buildroot I've found >>where the bluetooth is configured to work). >> >>Regards >> >>Tim >> >> >> >> >> >> |
From: Dan G. <djg...@go...> - 2007-10-15 16:09:45
|
What Gumstix version are you using, Is it connex If so it should do you know if it is the old or new bluetooth chip. The old is perfectly square , whilst the new is a rectangle with a chunk missing in the bottom edge Part number PBA 313308. As for the GPIO lines, there is information somewhere, My collegue had some data sheets on which was supposed to be connected where. Unfortunatly she is in spain attending a conference at the moment so i dont have access to her files. I will reply with the information when she gets back. iirc it is GPIO7 though. Regards. Dan On 10/15/07, Tim Redfern <gu...@ec...> wrote: > hi. thanks.. tried that... no joy. > > same error messages and > > # hcitool dev > Devices: > # > > I will try 1482. > > I actually went throught the S30bluetooth startup script from build 1161 > and the one difference that I could find is this: as you say, in the > stanza 'start' it says: > > echo AF1 out > /proc/gpio/GPIO12 > > I tried this as well, no joy. > > Does anyone know what else would be different in the bluetooth > subsystems between 1161 and any of these newer buildroots? Or is it a > different version of the software altogether? > > Could there be a difference between my gumstix and the ones that these > GPIO settings work for? Is there a way to find out what GPIO line is > actually connected to your bluetooth chip? > > Tim > > >I am using buildroot 1482, on 3 different boards and have managed to > >get bluetooth working on all. > > > >The boards are > > * Old Connex (PBA...7 Bluetooth Module) > > * New Connex (PBA...8 Bluetooth Module) > > * Verdex. > > > >The fix was eventually reasonably simple (after much pi**ing around > >with GPIO settings etc), someone suggested this solution. > > > >put these four lines > > > >echo "AF1 in" >/proc/gpio/GPIO42 > >echo "AF2 out" >/proc/gpio/GPIO43 > >echo "AF1 in" >/proc/gpio/GPIO44 > >echo "AF2 out" >/proc/gpio/GPIO45 > > > >in this file: /etc/init.d/S30bluetooth , in the start "stanza" after > >the modprobe of gumstix_bluetooth and proc_gpio. > > > >This has appeared to fix all my bluetooth problems. > > > >On 10/15/07, Tim Redfern <gu...@ec...> wrote: > > > > > >>Hi all, I wonder if anyone has any success stories using bluetooth with > >>a version of the buildroot newer than 1161 (the one that currently ships). > >> > >>A gumstix newbie., I am trying to build an application for connex 400, > >>that uses bluetooth and audio. I made the initial mistake of flashing > >>the gumstix to a new buildroot- before realising that bluez is > >>unconfigured at the moment. > >> > >>Craig from gumstix advised me to use buildroot 1161 (the one that > >>currently ships with gumstix), all fine, OSS audio & bluetooth work > >>here, I thought this was the solution. > >> > >>However buildroot 1161 has something weird with the ALSA libraries, they > >>are not downloaded into the root even when selected... so I'm back > >>looking to use or make a buildroot with audio and bluetooth. > >> > >>I looked at the change log and I though that 1499 might be a good one, > >>as changes were make to fold in a new bluez on 1500 and 1504 I think > >> > >>I've built 1499, all good, alsa libraries are there... > >> > >>However when I install it I'm back to the bluetooth hardware not being > >>detected. The familiar old: > >> > >>Starting Bluetooth subsystem:Trying baud rate 115200... > >>Got response after reset... gobbling > >>No response from BT module > >>Trying baud rate 921600... > >>No response after reset > >>No response from BT module > >>Trying baud rate 115200... > >>No response after reset > >>No response from BT module > >>Trying baud rate 57600... > >>No response after reset > >>No response from BT module > >> > >>Does anyone know what causes this? I know my bluetooth hardware is ok, > >>it works with buildroot 1161. Does anyone know how to reconfigure bluez > >>in the newer buildroots, or is anyone using bluetooth who could tell me > >>what buildroot they are using? (1161 is the ONLY buildroot I've found > >>where the bluetooth is configured to work). > >> > >>Regards > >> > >>Tim > >> > >> > >> > >> > >> > >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Tim R. <gu...@ec...> - 2007-10-15 16:34:21
|
well its a connex bt-400, its pretty new and the chip is PBA31308 v1.01 (i think! the writing is about 1mm high) It works in buildroot 1161, when the gpio setup in S30bluetooth is: echo AF1 out > /proc/gpio/GPIO12 this doesnt work in 1499. does the fact that this works in 1161 though mean i need to use GPIO12 rather than the GPIO42-45 you are using? hmm. i think i need to know more about this but i'm not asking the right questions. > What Gumstix version are you using, Is it connex If so it should do > you know if it is the old or new bluetooth chip. The old is perfectly > square , whilst the new is a rectangle with a chunk missing in the > bottom edge Part number PBA 313308. > > As for the GPIO lines, there is information somewhere, My collegue > had some data sheets on which was supposed to be connected where. > Unfortunatly she is in spain attending a conference at the moment so i > dont have access to her files. I will reply with the information when > she gets back. iirc it is GPIO7 though. > > Regards. > > Dan > > |
From: Dan G. <djg...@go...> - 2007-10-15 17:31:38
|
Excellent. That is the new bluetooth chip and I do have a working version. When i get back into the office tomorrow morning (approx 10am GMT) i will go through my notes and work out how i got everything working. Until then. On 10/15/07, Tim Redfern <gu...@ec...> wrote: > well its a connex bt-400, its pretty new and the chip is PBA31308 v1.01 > (i think! the writing is about 1mm high) > > It works in buildroot 1161, when the gpio setup in S30bluetooth is: > > echo AF1 out > /proc/gpio/GPIO12 > > this doesnt work in 1499. does the fact that this works in 1161 though > mean i need to use GPIO12 rather than the GPIO42-45 you are using? > > hmm. i think i need to know more about this but i'm not asking the right > questions. > > > > What Gumstix version are you using, Is it connex If so it should do > > you know if it is the old or new bluetooth chip. The old is perfectly > > square , whilst the new is a rectangle with a chunk missing in the > > bottom edge Part number PBA 313308. > > > > As for the GPIO lines, there is information somewhere, My collegue > > had some data sheets on which was supposed to be connected where. > > Unfortunatly she is in spain attending a conference at the moment so i > > dont have access to her files. I will reply with the information when > > she gets back. iirc it is GPIO7 though. > > > > Regards. > > > > Dan > > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Chris M. <ch...@mc...> - 2007-10-16 02:25:53
|
Dan, I am also interested in a working version of bluetooth. I have the verdex xm4-bt, but have been unable to get bluetooth working above 1482. Somewhere shortly after it was upgraded to integrate with dbus. Chris Dan Goldsmith wrote: > Excellent. That is the new bluetooth chip and I do have a working version. > When i get back into the office tomorrow morning (approx 10am GMT) i > will go through my notes and work out how i got everything working. > > Until then. > > On 10/15/07, Tim Redfern <gu...@ec...> wrote: > >> well its a connex bt-400, its pretty new and the chip is PBA31308 v1.01 >> (i think! the writing is about 1mm high) >> >> It works in buildroot 1161, when the gpio setup in S30bluetooth is: >> >> echo AF1 out > /proc/gpio/GPIO12 >> >> this doesnt work in 1499. does the fact that this works in 1161 though >> mean i need to use GPIO12 rather than the GPIO42-45 you are using? >> >> hmm. i think i need to know more about this but i'm not asking the right >> questions. >> >> >> >>> What Gumstix version are you using, Is it connex If so it should do >>> you know if it is the old or new bluetooth chip. The old is perfectly >>> square , whilst the new is a rectangle with a chunk missing in the >>> bottom edge Part number PBA 313308. >>> >>> As for the GPIO lines, there is information somewhere, My collegue >>> had some data sheets on which was supposed to be connected where. >>> Unfortunatly she is in spain attending a conference at the moment so i >>> dont have access to her files. I will reply with the information when >>> she gets back. iirc it is GPIO7 though. >>> >>> Regards. >>> >>> Dan >>> >>> >>> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: LachelnKind <Lac...@gm...> - 2007-10-16 02:57:18
|
I just got the newest revision, 1541, and put those 4 echo lines in the /etc/init.d/S30bluetooth file, but when I rebooted I got an error: Starting Bluetooth subsystem: hcid/etc/init.d/S30bluetooth: /etc/init.d/S30bluetooth: 53: cannot create /proc/gpio/GPIO42: Directory nonexistent Than I noticed that the /proc/gpio/ directory doesn't exist... Did this change recently? cause I thought i remember it existing in a previous revision. My start stanza: start) echo -n "Starting $DESC:" if $DAEMON_ENABLE && [ -x "$DAEMON_EXEC" ] && [ -f "$DAEMON_CONFIG" ] ; $DAEMON_EXEC -s -f $DAEMON_CONFIG echo -n " $DAEMON_NAME" fi if $HID2HCI_ENABLE && [ -x "$HID2HCI_EXEC" ] ; then $HID2HCI_EXEC --tohci > /dev/null 2>&1 || true echo -n " $HID2HCI_NAME" fi echo "AF1 in" >/proc/gpio/GPIO42 echo "AF2 out" >/proc/gpio/GPIO43 echo "AF1 in" >/proc/gpio/GPIO44 echo "AF2 out" >/proc/gpio/GPIO45 echo "." ;; Also, when I start my gumstix I get this: U-Boot 1.2.0 (Aug 26 2007 - 14:45:24) - 400 MHz - 1513 *** Welcome to Gumstix *** DRAM: 64 MB Flash: 16 MB SMC91C1111-0 Can't overwrite "serial#" Can't overwrite "ethaddr" Net: SMC91C1111-0 Are those two Can't overwrite "serial#" and "ethaddr" normal? If they aren't how can I fix them? Thanks in advance for any help anyone can provide... Chris McClenaghan wrote: > > Dan, > > I am also interested in a working version of bluetooth. I have the > verdex xm4-bt, but have been unable to get bluetooth working above 1482. > Somewhere shortly after it was upgraded to integrate with dbus. > > Chris > > Dan Goldsmith wrote: >> Excellent. That is the new bluetooth chip and I do have a working >> version. >> When i get back into the office tomorrow morning (approx 10am GMT) i >> will go through my notes and work out how i got everything working. >> >> Until then. >> >> On 10/15/07, Tim Redfern <gu...@ec...> wrote: >> >>> well its a connex bt-400, its pretty new and the chip is PBA31308 v1.01 >>> (i think! the writing is about 1mm high) >>> >>> It works in buildroot 1161, when the gpio setup in S30bluetooth is: >>> >>> echo AF1 out > /proc/gpio/GPIO12 >>> >>> this doesnt work in 1499. does the fact that this works in 1161 though >>> mean i need to use GPIO12 rather than the GPIO42-45 you are using? >>> >>> hmm. i think i need to know more about this but i'm not asking the right >>> questions. >>> >>> >>> >>>> What Gumstix version are you using, Is it connex If so it should do >>>> you know if it is the old or new bluetooth chip. The old is perfectly >>>> square , whilst the new is a rectangle with a chunk missing in the >>>> bottom edge Part number PBA 313308. >>>> >>>> As for the GPIO lines, there is information somewhere, My collegue >>>> had some data sheets on which was supposed to be connected where. >>>> Unfortunatly she is in spain attending a conference at the moment so i >>>> dont have access to her files. I will reply with the information when >>>> she gets back. iirc it is GPIO7 though. >>>> >>>> Regards. >>>> >>>> Dan >>>> >>>> >>>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Splunk Inc. >>> Still grepping through log files to find problems? Stop. >>> Now Search log events and configuration files using AJAX and a browser. >>> Download your FREE copy of Splunk now >> http://get.splunk.com/ >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/Bluetooth-stop-working-tf4381204.html#a13225995 Sent from the Gumstix mailing list archive at Nabble.com. |
From: Tim R. <gu...@ec...> - 2007-10-16 09:34:55
|
Hi Chris, that's interesting, do you know which buildroots you tried? I see that the change log says: 1483 <http://websvn.gumstix.com/listing.php?repname=Buildroot&path=%2F&rev=1483&sc=1> Fix symlink and 1499 <http://websvn.gumstix.com/listing.php?repname=Buildroot&path=%2F&rev=1499&sc=1> Add python modules: pybluez, pysqlite, pexpect 1500 <http://websvn.gumstix.com/listing.php?repname=Buildroot&path=%2F&rev=1500&sc=1> Update expat for new bluez 1501 <http://websvn.gumstix.com/listing.php?repname=Buildroot&path=%2F&rev=1501&sc=1> Add dbus user for dbus package whereas nothing from 1483-1500 seems to relate to bluetooth (or dbus, whatever that is), but bluetooth definately doesnt work in 1499 (for my connex bt400 with the 'new' bluetooth module anyway) --general question-- if there was a database of the useable status of different versions of the buildroot would that be useful to people? Tim >Dan, > >I am also interested in a working version of bluetooth. I have the >verdex xm4-bt, but have been unable to get bluetooth working above 1482. >Somewhere shortly after it was upgraded to integrate with dbus. > >Chris > >Dan Goldsmith wrote: > > >>Excellent. That is the new bluetooth chip and I do have a working version. >>When i get back into the office tomorrow morning (approx 10am GMT) i >>will go through my notes and work out how i got everything working. >> >>Until then. >> >>On 10/15/07, Tim Redfern <gu...@ec...> wrote: >> >> >> >>>well its a connex bt-400, its pretty new and the chip is PBA31308 v1.01 >>>(i think! the writing is about 1mm high) >>> >>>It works in buildroot 1161, when the gpio setup in S30bluetooth is: >>> >>>echo AF1 out > /proc/gpio/GPIO12 >>> >>>this doesnt work in 1499. does the fact that this works in 1161 though >>>mean i need to use GPIO12 rather than the GPIO42-45 you are using? >>> >>>hmm. i think i need to know more about this but i'm not asking the right >>>questions. >>> >>> >>> >>> >>> >>>>What Gumstix version are you using, Is it connex If so it should do >>>>you know if it is the old or new bluetooth chip. The old is perfectly >>>>square , whilst the new is a rectangle with a chunk missing in the >>>>bottom edge Part number PBA 313308. >>>> >>>>As for the GPIO lines, there is information somewhere, My collegue >>>>had some data sheets on which was supposed to be connected where. >>>>Unfortunatly she is in spain attending a conference at the moment so i >>>>dont have access to her files. I will reply with the information when >>>>she gets back. iirc it is GPIO7 though. >>>> >>>>Regards. >>>> >>>>Dan >>>> >>>> >>>> >>>> >>>> >>>------------------------------------------------------------------------- >>>This SF.net email is sponsored by: Splunk Inc. >>>Still grepping through log files to find problems? Stop. >>>Now Search log events and configuration files using AJAX and a browser. >>>Download your FREE copy of Splunk now >> http://get.splunk.com/ >>>_______________________________________________ >>>gumstix-users mailing list >>>gum...@li... >>>https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >>> >>> >>------------------------------------------------------------------------- >>This SF.net email is sponsored by: Splunk Inc. >>Still grepping through log files to find problems? Stop. >>Now Search log events and configuration files using AJAX and a browser. >>Download your FREE copy of Splunk now >> http://get.splunk.com/ >>_______________________________________________ >>gumstix-users mailing list >>gum...@li... >>https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> >> > >------------------------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. >Still grepping through log files to find problems? Stop. >Now Search log events and configuration files using AJAX and a browser. >Download your FREE copy of Splunk now >> http://get.splunk.com/ >_______________________________________________ >gumstix-users mailing list >gum...@li... >https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Dan G. <djg...@go...> - 2007-10-16 15:06:24
|
Sorry about the wait. But i have retraced my steps and created a second working version of the buildroot. Here are the steps i took. 1) Download revision 1482. This apparently works correctly 'out of the box' For Verdex this is semi True, Requireing only the addition of the Echo... Lines on /etc/init.d/S30 bluetooth For Connex I also downloaded 1161. This is a version i know works with a connex board. I then replaced the 1482 buildroots bluez make direcotry buildroot/packages/bluez With the one from 1161. After that Bluetooth worked like a charm. > --general question-- > > if there was a database of the useable status of different versions of > the buildroot would that be useful to people? I think that is a most excellent idea. Here is a list of Buildroot revisions That i have got bluetooth working on. 773 - Connex 1161 - Connex 1321 - Verdex 1482 - Verdex (With modification) 1482 - Connex (WIth modification) On 10/16/07, Tim Redfern <gu...@ec...> wrote: > Hi Chris, that's interesting, do you know which buildroots you tried? > > I see that the change log says: > > 1483 > <http://websvn.gumstix.com/listing.php?repname=Buildroot&path=%2F&rev=1483&sc=1> > Fix symlink > > and > > 1499 > <http://websvn.gumstix.com/listing.php?repname=Buildroot&path=%2F&rev=1499&sc=1> > Add python modules: pybluez, pysqlite, pexpect > 1500 > <http://websvn.gumstix.com/listing.php?repname=Buildroot&path=%2F&rev=1500&sc=1> > Update expat for new bluez > 1501 > <http://websvn.gumstix.com/listing.php?repname=Buildroot&path=%2F&rev=1501&sc=1> > Add dbus user for dbus package > > whereas nothing from 1483-1500 seems to relate to bluetooth (or dbus, > whatever that is), but bluetooth definately doesnt work in 1499 (for my > connex bt400 with the 'new' bluetooth module anyway) > > --general question-- > > if there was a database of the useable status of different versions of > the buildroot would that be useful to people? > > Tim > > >Dan, > > > >I am also interested in a working version of bluetooth. I have the > >verdex xm4-bt, but have been unable to get bluetooth working above 1482. > >Somewhere shortly after it was upgraded to integrate with dbus. > > > >Chris > > > >Dan Goldsmith wrote: > > > > > >>Excellent. That is the new bluetooth chip and I do have a working version. > >>When i get back into the office tomorrow morning (approx 10am GMT) i > >>will go through my notes and work out how i got everything working. > >> > >>Until then. > >> > >>On 10/15/07, Tim Redfern <gu...@ec...> wrote: > >> > >> > >> > >>>well its a connex bt-400, its pretty new and the chip is PBA31308 v1.01 > >>>(i think! the writing is about 1mm high) > >>> > >>>It works in buildroot 1161, when the gpio setup in S30bluetooth is: > >>> > >>>echo AF1 out > /proc/gpio/GPIO12 > >>> > >>>this doesnt work in 1499. does the fact that this works in 1161 though > >>>mean i need to use GPIO12 rather than the GPIO42-45 you are using? > >>> > >>>hmm. i think i need to know more about this but i'm not asking the right > >>>questions. > >>> > >>> > >>> > >>> > >>> > >>>>What Gumstix version are you using, Is it connex If so it should do > >>>>you know if it is the old or new bluetooth chip. The old is perfectly > >>>>square , whilst the new is a rectangle with a chunk missing in the > >>>>bottom edge Part number PBA 313308. > >>>> > >>>>As for the GPIO lines, there is information somewhere, My collegue > >>>>had some data sheets on which was supposed to be connected where. > >>>>Unfortunatly she is in spain attending a conference at the moment so i > >>>>dont have access to her files. I will reply with the information when > >>>>she gets back. iirc it is GPIO7 though. > >>>> > >>>>Regards. > >>>> > >>>>Dan > >>>> > >>>> > >>>> > >>>> > >>>> > >>>------------------------------------------------------------------------- > >>>This SF.net email is sponsored by: Splunk Inc. > >>>Still grepping through log files to find problems? Stop. > >>>Now Search log events and configuration files using AJAX and a browser. > >>>Download your FREE copy of Splunk now >> http://get.splunk.com/ > >>>_______________________________________________ > >>>gumstix-users mailing list > >>>gum...@li... > >>>https://lists.sourceforge.net/lists/listinfo/gumstix-users > >>> > >>> > >>> > >>> > >>------------------------------------------------------------------------- > >>This SF.net email is sponsored by: Splunk Inc. > >>Still grepping through log files to find problems? Stop. > >>Now Search log events and configuration files using AJAX and a browser. > >>Download your FREE copy of Splunk now >> http://get.splunk.com/ > >>_______________________________________________ > >>gumstix-users mailing list > >>gum...@li... > >>https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> > >> > >> > >> > > > >------------------------------------------------------------------------- > >This SF.net email is sponsored by: Splunk Inc. > >Still grepping through log files to find problems? Stop. > >Now Search log events and configuration files using AJAX and a browser. > >Download your FREE copy of Splunk now >> http://get.splunk.com/ > >_______________________________________________ > >gumstix-users mailing list > >gum...@li... > >https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Chris M. <ch...@mc...> - 2007-10-16 16:47:43
|
All, I'm guessing this list is primarily community driven. There are a couple of respondents who may or may not have specific responsibilities with Gumstix. Given the "size" of Gumstix, the ability to support this kind of useful information may not be possible. Further, it is not always clear what drives change in buildroot - hardware, features, bugs ...? I think a community build with useful what works and what doesn't and why information would be useful. Perhaps Gumstix could supply some communications about it's internal activities that would align with the community build in useful ways. This is a non trivial effort, even if only as described below, and I suppose for most of us, the day job takes most of the available cycles. $0.02, Chris Dan Goldsmith wrote: >> --general question-- >> >> if there was a database of the useable status of different versions of >> the buildroot would that be useful to people? >> > > I think that is a most excellent idea. > > Here is a list of Buildroot revisions That i have got bluetooth working on. > > 773 - Connex > 1161 - Connex > 1321 - Verdex > 1482 - Verdex (With modification) > 1482 - Connex (WIth modification) > > > On 10/16/07, Tim Redfern <gu...@ec...> wrote: > >> Hi Chris, that's interesting, do you know which buildroots you tried? >> >> I see that the change log says: >> >> 1483 >> <http://websvn.gumstix.com/listing.php?repname=Buildroot&path=%2F&rev=1483&sc=1> >> Fix symlink >> >> and >> >> 1499 >> <http://websvn.gumstix.com/listing.php?repname=Buildroot&path=%2F&rev=1499&sc=1> >> Add python modules: pybluez, pysqlite, pexpect >> 1500 >> <http://websvn.gumstix.com/listing.php?repname=Buildroot&path=%2F&rev=1500&sc=1> >> Update expat for new bluez >> 1501 >> <http://websvn.gumstix.com/listing.php?repname=Buildroot&path=%2F&rev=1501&sc=1> >> Add dbus user for dbus package >> >> whereas nothing from 1483-1500 seems to relate to bluetooth (or dbus, >> whatever that is), but bluetooth definately doesnt work in 1499 (for my >> connex bt400 with the 'new' bluetooth module anyway) >> >> --general question-- >> >> if there was a database of the useable status of different versions of >> the buildroot would that be useful to people? >> >> Tim >> >> >>> Dan, >>> >>> I am also interested in a working version of bluetooth. I have the >>> verdex xm4-bt, but have been unable to get bluetooth working above 1482. >>> Somewhere shortly after it was upgraded to integrate with dbus. >>> >>> Chris >>> >>> Dan Goldsmith wrote: >>> >>> >>> >>>> Excellent. That is the new bluetooth chip and I do have a working version. >>>> When i get back into the office tomorrow morning (approx 10am GMT) i >>>> will go through my notes and work out how i got everything working. >>>> >>>> Until then. >>>> >>>> On 10/15/07, Tim Redfern <gu...@ec...> wrote: >>>> >>>> >>>> >>>> >>>>> well its a connex bt-400, its pretty new and the chip is PBA31308 v1.01 >>>>> (i think! the writing is about 1mm high) >>>>> >>>>> It works in buildroot 1161, when the gpio setup in S30bluetooth is: >>>>> >>>>> echo AF1 out > /proc/gpio/GPIO12 >>>>> >>>>> this doesnt work in 1499. does the fact that this works in 1161 though >>>>> mean i need to use GPIO12 rather than the GPIO42-45 you are using? >>>>> >>>>> hmm. i think i need to know more about this but i'm not asking the right >>>>> questions. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>> What Gumstix version are you using, Is it connex If so it should do >>>>>> you know if it is the old or new bluetooth chip. The old is perfectly >>>>>> square , whilst the new is a rectangle with a chunk missing in the >>>>>> bottom edge Part number PBA 313308. >>>>>> >>>>>> As for the GPIO lines, there is information somewhere, My collegue >>>>>> had some data sheets on which was supposed to be connected where. >>>>>> Unfortunatly she is in spain attending a conference at the moment so i >>>>>> dont have access to her files. I will reply with the information when >>>>>> she gets back. iirc it is GPIO7 though. >>>>>> >>>>>> Regards. >>>>>> >>>>>> Dan >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> ------------------------------------------------------------------------- >>>>> This SF.net email is sponsored by: Splunk Inc. >>>>> Still grepping through log files to find problems? Stop. >>>>> Now Search log events and configuration files using AJAX and a browser. >>>>> Download your FREE copy of Splunk now >> http://get.splunk.com/ >>>>> _______________________________________________ >>>>> gumstix-users mailing list >>>>> gum...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>> >>>>> >>>>> >>>>> >>>>> >>>> ------------------------------------------------------------------------- >>>> This SF.net email is sponsored by: Splunk Inc. >>>> Still grepping through log files to find problems? Stop. >>>> Now Search log events and configuration files using AJAX and a browser. >>>> Download your FREE copy of Splunk now >> http://get.splunk.com/ >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>>> >>>> >>>> >>>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Splunk Inc. >>> Still grepping through log files to find problems? Stop. >>> Now Search log events and configuration files using AJAX and a browser. >>> Download your FREE copy of Splunk now >> http://get.splunk.com/ >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >>> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Jonathan W. <jon...@cl...> - 2007-10-16 20:26:00
|
> Sorry about the wait. But i have retraced my steps and created a > second working version of the buildroot. > > Here are the steps i took. > > 1) Download revision 1482. This apparently works correctly 'out of the box' > > For Verdex this is semi True, Requireing only the addition of the > Echo... Lines on /etc/init.d/S30 bluetooth > > For Connex I also downloaded 1161. This is a version i know works > with a connex board. > > I then replaced the 1482 buildroots bluez make direcotry > buildroot/packages/bluez > With the one from 1161. > > After that Bluetooth worked like a charm. > >> --general question-- >> >> if there was a database of the useable status of different versions of >> the buildroot would that be useful to people? > > I think that is a most excellent idea. > > Here is a list of Buildroot revisions That i have got bluetooth working on. > > 773 - Connex > 1161 - Connex > 1321 - Verdex > 1482 - Verdex (With modification) > 1482 - Connex (WIth modification) Copying the bluez directory from 1161 to the current svn buildroot (1541) also seems to work fine on Connex, Jonathan -- Jonathan Wood jon...@cl... |
From: LachelnKind <Lac...@gm...> - 2007-10-17 02:10:38
|
I just downloaded revision 1541 and replaced the /package/bluez/ folder with the one from revision 1161 and it worked perfectly! Thanks for the tip!!! :) Jonathan Wood-2 wrote: > >> Sorry about the wait. But i have retraced my steps and created a >> second working version of the buildroot. >> >> Here are the steps i took. >> >> 1) Download revision 1482. This apparently works correctly 'out of the >> box' >> >> For Verdex this is semi True, Requireing only the addition of the >> Echo... Lines on /etc/init.d/S30 bluetooth >> >> For Connex I also downloaded 1161. This is a version i know works >> with a connex board. >> >> I then replaced the 1482 buildroots bluez make direcotry >> buildroot/packages/bluez >> With the one from 1161. >> >> After that Bluetooth worked like a charm. >> >>> --general question-- >>> >>> if there was a database of the useable status of different versions of >>> the buildroot would that be useful to people? >> >> I think that is a most excellent idea. >> >> Here is a list of Buildroot revisions That i have got bluetooth working >> on. >> >> 773 - Connex >> 1161 - Connex >> 1321 - Verdex >> 1482 - Verdex (With modification) >> 1482 - Connex (WIth modification) > > Copying the bluez directory from 1161 to the current svn buildroot > (1541) also seems to work fine on Connex, > > Jonathan > > -- > Jonathan Wood > jon...@cl... > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/Bluetooth-stop-working-tf4381204.html#a13245980 Sent from the Gumstix mailing list archive at Nabble.com. |
From: Tim R. <gu...@ec...> - 2007-10-17 13:36:02
|
Yes I tried thid with 1482 and it worked. So it would seem that the bluez folder from 1161 works in any buildroot! Thats made my day. >I just downloaded revision 1541 and replaced the /package/bluez/ folder with >the one from revision 1161 and it worked perfectly! Thanks for the tip!!! :) > > > >Jonathan Wood-2 wrote: > > >>>Sorry about the wait. But i have retraced my steps and created a >>>second working version of the buildroot. >>> >>>Here are the steps i took. >>> >>>1) Download revision 1482. This apparently works correctly 'out of the >>>box' >>> >>>For Verdex this is semi True, Requireing only the addition of the >>>Echo... Lines on /etc/init.d/S30 bluetooth >>> >>>For Connex I also downloaded 1161. This is a version i know works >>>with a connex board. >>> >>>I then replaced the 1482 buildroots bluez make direcotry >>>buildroot/packages/bluez >>>With the one from 1161. >>> >>>After that Bluetooth worked like a charm. >>> >>> >>> >>>>--general question-- >>>> >>>>if there was a database of the useable status of different versions of >>>>the buildroot would that be useful to people? >>>> >>>> >>>I think that is a most excellent idea. >>> >>>Here is a list of Buildroot revisions That i have got bluetooth working >>>on. >>> >>>773 - Connex >>>1161 - Connex >>>1321 - Verdex >>>1482 - Verdex (With modification) >>>1482 - Connex (WIth modification) >>> >>> >>Copying the bluez directory from 1161 to the current svn buildroot >>(1541) also seems to work fine on Connex, >> >>Jonathan >> >>-- >>Jonathan Wood >>jon...@cl... >> >>------------------------------------------------------------------------- >>This SF.net email is sponsored by: Splunk Inc. >>Still grepping through log files to find problems? Stop. >>Now Search log events and configuration files using AJAX and a browser. >>Download your FREE copy of Splunk now >> http://get.splunk.com/ >>_______________________________________________ >>gumstix-users mailing list >>gum...@li... >>https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> >> > > > |
From: Chris M. <ch...@mc...> - 2007-10-17 17:03:54
|
This appears to be a reasonable strategy. Is this working for both verdex and connex boards? Only one respondent seems to have identified connex, I have a verdex. Also, at the same time can the dbus package be removed or are other packages dependent on dbus? Chris Tim Redfern wrote: > Yes I tried thid with 1482 and it worked. So it would seem that the > bluez folder from 1161 works in any buildroot! Thats made my day. > > >> I just downloaded revision 1541 and replaced the /package/bluez/ folder with >> the one from revision 1161 and it worked perfectly! Thanks for the tip!!! :) >> >> >> >> Jonathan Wood-2 wrote: >> >> >> >>>> Sorry about the wait. But i have retraced my steps and created a >>>> second working version of the buildroot. >>>> >>>> Here are the steps i took. >>>> >>>> 1) Download revision 1482. This apparently works correctly 'out of the >>>> box' >>>> >>>> For Verdex this is semi True, Requireing only the addition of the >>>> Echo... Lines on /etc/init.d/S30 bluetooth >>>> >>>> For Connex I also downloaded 1161. This is a version i know works >>>> with a connex board. >>>> >>>> I then replaced the 1482 buildroots bluez make direcotry >>>> buildroot/packages/bluez >>>> With the one from 1161. >>>> >>>> After that Bluetooth worked like a charm. >>>> >>>> >>>> >>>> >>>>> --general question-- >>>>> >>>>> if there was a database of the useable status of different versions of >>>>> the buildroot would that be useful to people? >>>>> >>>>> >>>>> >>>> I think that is a most excellent idea. >>>> >>>> Here is a list of Buildroot revisions That i have got bluetooth working >>>> on. >>>> >>>> 773 - Connex >>>> 1161 - Connex >>>> 1321 - Verdex >>>> 1482 - Verdex (With modification) >>>> 1482 - Connex (WIth modification) >>>> >>>> >>>> >>> Copying the bluez directory from 1161 to the current svn buildroot >>> (1541) also seems to work fine on Connex, >>> >>> Jonathan >>> >>> -- >>> Jonathan Wood >>> jon...@cl... >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Splunk Inc. >>> Still grepping through log files to find problems? Stop. >>> Now Search log events and configuration files using AJAX and a browser. >>> Download your FREE copy of Splunk now >> http://get.splunk.com/ >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >>> >>> >>> >> >> >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: <soj...@fr...> - 2007-10-22 14:11:01
|
Hi all, I am trying to record sound on my verdex XM4 using an audiostix2. It works perfectly with line in, when sound is sourced from my computer through a stereo mini-jack/mini-jack cable, but I just get silence when pluging in a dynamic microphone. I noticed on the audiostix2 schematics that MICP (mic_in, I guess) is connected to the right signal on the mini-jack plug, so my microphone has to be connected. Is there something I have to do on the software side in order to enable MICP (and disable LINE_IN_L, I suppose)? Best, Julien |
From: Linus C. <li...@li...> - 2007-09-05 17:08:21
|
So I understand that u-boot turns on the 32 kHz clock for the bluetooth clock. Where is the 32kHz clock pad-test? or in with pin is it? I would like to limit the possibilities of that is maiking the bluetooth fail. Is there guaranty in a verdex? How much time does it last? Thanks! On 9/4/07, Linus Casassa <li...@li...> wrote: > Sorry for the pore information. > > I have 2 verdex with a tweener each. > > In both verdex I had: > > Starting 32kHz clock...Settled > Starting Bluetooth subsystem:Trying baud rate 115200... > No response after reset > No response from BT module > Trying baud rate 921600... > No response after reset > No response from BT module > Trying baud rate 115200... > No response after reset > No response from BT module > Trying baud rate 57600... > No response after reset > No response from BT module > Can't initialize device: Success > > So I put in /etc/init.d/S30bluetooth in the start section: > > echo "AF1 in" >/proc/gpio/GPIO42 > echo "AF2 out" >/proc/gpio/GPIO43 > echo "AF1 in" >/proc/gpio/GPIO44 > echo "AF2 out" >/proc/gpio/GPIO45 > > In one verdex (lets name it verdex A) I get: > > # /etc/init.d/S30bluetooth start > Starting 32kHz clock...Settled > Starting Bluetooth subsystem:Trying baud rate 115200... > No response after reset > Read wrong response size: 5 > 0x04 0xff 0x02 0x05 0x01 Trying baud rate 921600... > No response after reset > No response from BT module > Trying baud rate 115200... > No response after reset > Read wrong response size: 5 > 0x04 0xff 0x02 0x05 0x01 Trying baud rate 57600... > No response after reset > Initialization timed out. > > And in verdex B it work very well yesterday. I could enter the console > with ssh without any problems. And today when I turn it on: > > # /etc/init.d/S30bluetooth start > Starting 32kHz clock...Settled > Starting Bluetooth subsystem:Trying baud rate 115200... > Got response after reset... gobbling > No response from BT module > Trying baud rate 921600... > Got response after reset... gobbling > No response from BT module > Trying baud rate 115200... > Got response after reset... gobbling > No response from BT module > Trying baud rate 57600... > Got response after reset... gobbling > No response from BT module > Can't initialize device: Success > > :/ > > I tried building r1482 and I get the same thing. > > Sorry about my English. > > > > > On 9/4/07, Mark Ahlenius - comcast <m_a...@co...> wrote: > > > > Hi, > > > > question - how did you get BT to start working in the first place? > What proc card, a verdex? > > > > thx > > > > 'mark > > > > Linus Casassa wrote: > > > > > > It was working until I reboot. > > > > # /etc/init.d/S30bluetooth start > > Starting 32kHz clock...Settled > > Starting Bluetooth subsystem:Trying baud rate 115200... > > Got response after reset... gobbling > > No response from BT module > > Trying baud rate 921600... > > Got response after reset... gobbling > > No response from BT module > > Trying baud rate 115200... > > Got response after reset... gobbling > > No response from BT module > > Trying baud rate 57600... > > Got response after reset... gobbling > > No response from BT module > > Can't initialize device: Success > > # > > > > > > What can I do? > > ________________________________ > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > > > > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > ________________________________ > > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > |
From: LachelnKind <Lac...@gm...> - 2007-09-05 17:36:47
|
Are all these fixes to get bluetooth working only for the verdex? or will it work with the basix-xm-bt also? I noticed my bluetooth hasn't been working recently (When I type hcitool scan on my laptop, it cant find my gumstix). Linus Casassa-2 wrote: > > It was working until I reboot. > > # /etc/init.d/S30bluetooth start > Starting 32kHz clock...Settled > Starting Bluetooth subsystem:Trying baud rate 115200... > Got response after reset... gobbling > No response from BT module > Trying baud rate 921600... > Got response after reset... gobbling > No response from BT module > Trying baud rate 115200... > Got response after reset... gobbling > No response from BT module > Trying baud rate 57600... > Got response after reset... gobbling > No response from BT module > Can't initialize device: Success > # > > > What can I do? > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/Bluetooth-stop-working-tf4381204.html#a12507130 Sent from the Gumstix mailing list archive at Nabble.com. |
From: Linus C. <li...@li...> - 2007-09-05 18:14:17
|
I don't know if its the same for the basix. I only have verdex 400 MHz with 64M of ram and 16M of flash. Everybody has the bluetooth working without problems? I think the hardware is bad but why both of my gumstix :( On 9/5/07, LachelnKind <Lac...@gm...> wrote: > > Are all these fixes to get bluetooth working only for the verdex? or will it > work with the basix-xm-bt also? I noticed my bluetooth hasn't been working > recently (When I type hcitool scan on my laptop, it cant find my gumstix). > > > > Linus Casassa-2 wrote: > > > > It was working until I reboot. > > > > # /etc/init.d/S30bluetooth start > > Starting 32kHz clock...Settled > > Starting Bluetooth subsystem:Trying baud rate 115200... > > Got response after reset... gobbling > > No response from BT module > > Trying baud rate 921600... > > Got response after reset... gobbling > > No response from BT module > > Trying baud rate 115200... > > Got response after reset... gobbling > > No response from BT module > > Trying baud rate 57600... > > Got response after reset... gobbling > > No response from BT module > > Can't initialize device: Success > > # > > > > > > What can I do? > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > -- > View this message in context: http://www.nabble.com/Bluetooth-stop-working-tf4381204.html#a12507130 > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: LachelnKind <Lac...@gm...> - 2007-09-05 18:24:44
|
Well I have noticed a few threads with ppl saying the bluetooth isn't working. It looks like I am getting the same messages as some other ppl who are having problems. I have revision 1482 on my basix gumstix and will try and go through some of the tips people gave. The only tip I saw was to put these four lines echo "AF1 in" >/proc/gpio/GPIO42 echo "AF2 out" >/proc/gpio/GPIO43 echo "AF1 in" >/proc/gpio/GPIO44 echo "AF2 out" >/proc/gpio/GPIO45 in this file: /etc/init.d/S30bluetooth , in the start "stanza" after the modprobe of gumstix_bluetooth and proc_gpio. and also make sure that the ttyl in /etc/default/bluetooth is ttyS1 and not ttyS2 (which it is ttyS1, I checked before) Linus Casassa-2 wrote: > > I don't know if its the same for the basix. I only have verdex 400 MHz > with 64M of ram and 16M of flash. > > Everybody has the bluetooth working without problems? I think the > hardware is bad but why both of my gumstix :( > > On 9/5/07, LachelnKind <Lac...@gm...> wrote: >> >> Are all these fixes to get bluetooth working only for the verdex? or will >> it >> work with the basix-xm-bt also? I noticed my bluetooth hasn't been >> working >> recently (When I type hcitool scan on my laptop, it cant find my >> gumstix). >> >> >> >> Linus Casassa-2 wrote: >> > >> > It was working until I reboot. >> > >> > # /etc/init.d/S30bluetooth start >> > Starting 32kHz clock...Settled >> > Starting Bluetooth subsystem:Trying baud rate 115200... >> > Got response after reset... gobbling >> > No response from BT module >> > Trying baud rate 921600... >> > Got response after reset... gobbling >> > No response from BT module >> > Trying baud rate 115200... >> > Got response after reset... gobbling >> > No response from BT module >> > Trying baud rate 57600... >> > Got response after reset... gobbling >> > No response from BT module >> > Can't initialize device: Success >> > # >> > >> > >> > What can I do? >> > >> > >> ------------------------------------------------------------------------- >> > This SF.net email is sponsored by: Splunk Inc. >> > Still grepping through log files to find problems? Stop. >> > Now Search log events and configuration files using AJAX and a browser. >> > Download your FREE copy of Splunk now >> http://get.splunk.com/ >> > _______________________________________________ >> > gumstix-users mailing list >> > gum...@li... >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Bluetooth-stop-working-tf4381204.html#a12507130 >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/Bluetooth-stop-working-tf4381204.html#a12508041 Sent from the Gumstix mailing list archive at Nabble.com. |
From: Brad M. <bmi...@gm...> - 2007-09-05 20:18:31
|
Linus Clair's suggestion was to rename the startup script to make it happen last. Brad |