From: clairm <cla...@ho...> - 2008-02-26 22:53:43
|
OK, I downloaded the latest Open Embedded source code on 2/24 and flashed my basix 400xm-bt, including u-boot 1.2.0. Now I can't get bluetooth to work. During the boot sequence I see: Starting Bluetooth subsystem: Trying baud rate 921600... 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 My laptop no longer sees a Gumstix(0) bluetooth device. Am I missing something here? Clair -- View this message in context: http://www.nabble.com/No-Bluetooth-after-OE-flash-tp15701813p15701813.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Steve S. <sa...@gm...> - 2008-02-26 23:55:39
|
Clair, It seems the default script still has issues with some modules. Could you try editing your /etc/init.d/bluetooth script to test a fix? Your original file should have a section that looks like this: # if you have an older gumstix motherboard with a ROK bluetooth module # uncomment the following line # echo "GPIO out set" >/proc/gpio/GPIO7 echo "AF1 out" > /proc/gpio/GPIO12 Please change it to: # if you have an older gumstix motherboard with a ROK bluetooth module # uncomment the following 4 lines echo GPIO out clear >/proc/gpio/GPIO7 sleep 1 echo GPIO out set >/proc/gpio/GPIO7 sleep 1 echo "AF1 out" > /proc/gpio/GPIO12 Let me know whether this resolves your problem. Steve On Tue, Feb 26, 2008 at 2:53 PM, clairm <cla...@ho...> wrote: > > OK, I downloaded the latest Open Embedded source code on 2/24 and flashed my > basix 400xm-bt, including u-boot 1.2.0. Now I can't get bluetooth to work. > During the boot sequence I see: > > Starting Bluetooth subsystem: > Trying baud rate 921600... > 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 > > My laptop no longer sees a Gumstix(0) bluetooth device. Am I missing > something here? > > Clair > -- > View this message in context: http://www.nabble.com/No-Bluetooth-after-OE-flash-tp15701813p15701813.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: clairm <cla...@ho...> - 2008-02-27 17:35:09
|
That fixed it, thanks. -- View this message in context: http://www.nabble.com/No-Bluetooth-after-OE-flash-tp15701813p15718440.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Steve S. <sa...@gm...> - 2008-02-27 17:45:29
|
Clair, Glad to hear that it works now. Would you mind trying an experiment for me? I'd like to see if we can simplify things a bit. Could you change: # if you have an older gumstix motherboard with a ROK bluetooth module # uncomment the following 4 lines echo GPIO out clear >/proc/gpio/GPIO7 sleep 1 echo GPIO out set >/proc/gpio/GPIO7 sleep 1 echo "AF1 out" > /proc/gpio/GPIO12 To: # if you have an older gumstix motherboard with a ROK bluetooth module # uncomment the following 3 lines echo GPIO out clear >/proc/gpio/GPIO7 sleep 1 echo GPIO out set >/proc/gpio/GPIO7 echo "AF1 out" > /proc/gpio/GPIO12 Then, if that still works, try: # if you have an older gumstix motherboard with a ROK bluetooth module # uncomment the following 2 lines echo GPIO out clear >/proc/gpio/GPIO7 echo GPIO out set >/proc/gpio/GPIO7 Thanks! Steve On Tue, Feb 26, 2008 at 3:55 PM, Steve Sakoman <sa...@gm...> wrote: > Clair, > > It seems the default script still has issues with some modules. > > Could you try editing your /etc/init.d/bluetooth script to test a fix? > > Your original file should have a section that looks like this: > > # if you have an older gumstix motherboard with a ROK bluetooth module > # uncomment the following line > # echo "GPIO out set" >/proc/gpio/GPIO7 > echo "AF1 out" > /proc/gpio/GPIO12 > > Please change it to: > > # if you have an older gumstix motherboard with a ROK bluetooth module > # uncomment the following 4 lines > echo GPIO out clear >/proc/gpio/GPIO7 > sleep 1 > echo GPIO out set >/proc/gpio/GPIO7 > sleep 1 > echo "AF1 out" > /proc/gpio/GPIO12 > > Let me know whether this resolves your problem. > > Steve > > > > On Tue, Feb 26, 2008 at 2:53 PM, clairm <cla...@ho...> wrote: > > > > OK, I downloaded the latest Open Embedded source code on 2/24 and flashed my > > basix 400xm-bt, including u-boot 1.2.0. Now I can't get bluetooth to work. > > During the boot sequence I see: > > > > Starting Bluetooth subsystem: > > Trying baud rate 921600... > > 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 > > > > My laptop no longer sees a Gumstix(0) bluetooth device. Am I missing > > something here? > > > > Clair > > -- > > View this message in context: http://www.nabble.com/No-Bluetooth-after-OE-flash-tp15701813p15701813.html > > Sent from the Gumstix mailing list archive at Nabble.com. > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > |
From: clairm <cla...@ho...> - 2008-02-27 19:23:06
|
OK, I took one sleep out, then the other, and didn't have any trouble connecting via BT after warm boots. Then I cold booted and couldn't get BT to connect. I hooked up my terminal card and cold booted again, and this time I could connect via BT. So, it looks like removing the sleeps makes it less reliable. I'm going to leave them in on my machine. -- View this message in context: http://www.nabble.com/No-Bluetooth-after-OE-flash-tp15701813p15720917.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Steve S. <sa...@gm...> - 2008-02-29 15:51:43
|
This fix is incorporated in revision 260 Steve On Wed, Feb 27, 2008 at 11:23 AM, clairm <cla...@ho...> wrote: > > OK, I took one sleep out, then the other, and didn't have any trouble > connecting via BT after warm boots. Then I cold booted and couldn't get BT > to connect. I hooked up my terminal card and cold booted again, and this > time I could connect via BT. So, it looks like removing the sleeps makes it > less reliable. I'm going to leave them in on my machine. > -- > View this message in context: http://www.nabble.com/No-Bluetooth-after-OE-flash-tp15701813p15720917.html > > > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |