Category:How to - bluetooth - Revision history

Ashcharles: /* Configure extra GPIOs */

2016-04-01T23:23:19Z

‎Configure extra GPIOs

Jeremy Zafran: /* Essentials */ changed ipkg to opkg

2011-07-21T17:35:18Z

‎Essentials: changed ipkg to opkg

Jsarao at 20:51, 15 October 2009

2009-10-15T20:51:39Z

Jsarao at 20:49, 15 October 2009

2009-10-15T20:49:01Z

Donnay: undo

2009-04-30T05:13:12Z

undo

87.236.199.73: /* Essentials */

2009-04-30T02:54:52Z

‎Essentials

128.29.43.1: /* BlueZ utilities */

2009-04-02T17:17:44Z

‎BlueZ utilities

128.29.43.1: /* Configure extra GPIOs */

2009-04-02T17:17:02Z

‎Configure extra GPIOs

128.29.43.2: /* kick-start */

2009-04-01T21:09:10Z

‎kick-start

Donnay: add advice from Australia

2008-11-29T08:28:19Z

add advice from Australia

← Older revision		Revision as of 23:23, 1 April 2016
Line 303:		Line 303:
	</pre>		</pre>

−	~~The last two GPIOs (44/45) do not seem to be documented anywhere?- http://docwiki.gumstix.org/Gumstix_UARTs~~
	--------------------------------------------------------------------------------------------------------------------------------------------------------------		--------------------------------------------------------------------------------------------------------------------------------------------------------------

@@ Line 3: / Line 3: @@
 Install the basic bluetooth stuff with
-  ipkg install bluez-utils
+  opkg install bluez-utils
 First off, I had to move the "sleep 1" from after "sdptool add ..." to before the sdptool command. The startup script seemed to be failing to run to completion before I did that.

← Older revision		Revision as of 20:51, 15 October 2009
Line 312:		Line 312:

	Tomas Targownik		Tomas Targownik
−
−
−
−	.
−

	[[Category:How_to_-_general]]		[[Category:How_to_-_general]]

← Older revision		Revision as of 20:49, 15 October 2009
Line 316:		Line 316:

	.		.
		+
		+
		+	[[Category:How_to_-_general]]

← Older revision		Revision as of 05:13, 30 April 2009
Line 1:		Line 1:
−	~~EEnaDY <a href~~="~~http://fdnvyrxigfla.com/~~"~~>fdnvyrxigfla</a>, [url=http://qeqfpfbshatx~~.~~com/]qeqfpfbshatx[/url], [link=http://gjrtkrukwnhh~~.~~com/]gjrtkrukwnhh[/link], http://hrimnhlqvydz~~.~~com/~~	+	== Essentials ==
		+
		+	Install the basic bluetooth stuff with
		+
		+	ipkg install bluez-utils
		+
		+	First off, I had to move the "sleep 1" from after "sdptool add ..." to before the sdptool command. The startup script seemed to be failing to run to completion before I did that.

	== Networking: pan access point ==		== Networking: pan access point ==

@@ Line 1: / Line 1: @@
-== Essentials ==
+EEnaDY  <a href="http://fdnvyrxigfla.com/">fdnvyrxigfla</a>, [url=http://qeqfpfbshatx.com/]qeqfpfbshatx[/url], [link=http://gjrtkrukwnhh.com/]gjrtkrukwnhh[/link], http://hrimnhlqvydz.com/
-−
-Install the basic bluetooth stuff with
-−
- ipkg install bluez-utils
-−
-First off, I had to move the "sleep 1" from after "sdptool add ..." to before the sdptool command. The startup script seemed to be failing to run to completion before I did that.
 == Networking: pan access point ==

@@ Line 268: / Line 268: @@
 function of 'hciattach.c'-
 //system("echo clear > /proc/gpio/GPIO12");
 //system("echo set > /proc/gpio/GPIO12");
 We felt these were more appropriate in S30Bluetooth.
 --------------------------------------------------------------------------------------------------------------------------------------------------------------
 ===HCIATTACH commands===
 The Bluetooth appears to be on ttyS1, where previously it was present on ttyS3.

@@ Line 287: / Line 287: @@
 Lastly, some extra GPIOs needed to be configured as appropriate. We only discovered this when we looked at the Open Embedded version of /etc/init.d/bluetooth and discovered that it had some mysterious extra GPIOs being set, that were not present in the buildroot script or any documentation. These are the following-
 echo AF1 out > /proc/gpio/GPIO12
 sleep 1
@@ Line 293: / Line 294: @@
 echo GPIO out set >/proc/gpio/GPIO7
 sleep 1
-echo "AF1 in"  > /proc/gpio/GPIO42 (Not present in buildroot)
+echo "AF1 in"  > /proc/gpio/GPIO42      #(Not present in buildroot)
-echo "AF2 out" > /proc/gpio/GPIO43 (Not present in buildroot)
+echo "AF2 out" > /proc/gpio/GPIO43      #(Not present in buildroot)
-echo "AF1 in"  > /proc/gpio/GPIO44 (Not present in buildroot, not
+echo "AF1 in"  > /proc/gpio/GPIO44      #(Not present in buildroot, not documented)
-documented)
+echo "AF2 out" > /proc/gpio/GPIO45      #(Not present in buildroot, not documented)
-echo "AF2 out" > /proc/gpio/GPIO45 (Not present in buildroot, not
+</pre>
 documented)
 The last two GPIOs (44/45) do not seem to be documented anywhere?- http://docwiki.gumstix.org/Gumstix_UARTs

@@ Line 220: / Line 220: @@
 The kick-start procedure is as follows-
+<pre>
 /etc/init.d/S30bluetooth stop
 echo \"AF1 out\" > /proc/gpio/GPIO12
 echo \"GPIO out clear\" >/proc/gpio/GPIO7
@@ Line 242: / Line 243: @@
 echo \"AF1 in\"  > /proc/gpio/GPIO44
 echo \"AF2 out\" > /proc/gpio/GPIO45
-/usr/sbin/hciattach -s 115200 ttyS1 gumstix 921600  <-- (Infineon
+/usr/sbin/hciattach -s 115200 ttyS1 gumstix 921600  <-- (Infineon Manufacturer Mode is invoked here, within hciattach)
 Manufacturer Mode is invoked here, within hciattach)
 /etc/init.d/S30bluetooth stop
 echo \"AF1 out\" > /proc/gpio/GPIO12
@@ Line 254: / Line 254: @@
 echo \"AF1 in\"  > /proc/gpio/GPIO44
 echo \"AF2 out\" > /proc/gpio/GPIO45
-/usr/sbin/hciattach -s 921600 ttyS1 gumstix 921600 <-- (Will now
+/usr/sbin/hciattach -s 921600 ttyS1 gumstix 921600 <-- (Will now connect at 921600 using this command only)
-connect at 921600 using this command only)
+</pre>
 --------------------------------------------------------------------------------------------------------------------------------------------------------------
 ===BlueZ utilities===
 The BlueZ utilities version we were using was too old- V2.24, and it did not contain the appropriate 'infineon manufacturer mode' functions required to change the speed of the module. It gave the following output when trying to bring up the module-

← Older revision		Revision as of 08:28, 29 November 2008
Line 212:		Line 212:

	And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.		And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.
		+
		+
		+	==Bluetooth advice from Australia==
		+	===kick-start===
		+	The Infineon v1.01 modules require a once-only 'kick-start' to become operational at a speed of 921600.
		+	We have found the kick-start procedure below must be adhered to exactly, in order for the module to properly invoke the 'infineon manufacturer mode' function (that changes the speed) within hciattach.
		+
		+	The kick-start procedure is as follows-
		+
		+	/etc/init.d/S30bluetooth stop
		+	echo \"AF1 out\" > /proc/gpio/GPIO12
		+	echo \"GPIO out clear\" >/proc/gpio/GPIO7
		+	sleep 1
		+	echo \"GPIO out set\" >/proc/gpio/GPIO7
		+	sleep 1
		+	echo \"AF1 in\" > /proc/gpio/GPIO42
		+	echo \"AF2 out\" > /proc/gpio/GPIO43
		+	echo \"AF1 in\" > /proc/gpio/GPIO44
		+	echo \"AF2 out\" > /proc/gpio/GPIO45
		+	/usr/sbin/hciattach -s 115200 ttyS1 gumstix 115200
		+	/etc/init.d/S30bluetooth stop
		+	echo \"AF1 out\" > /proc/gpio/GPIO12
		+	echo \"GPIO out clear\" >/proc/gpio/GPIO7
		+	sleep 1
		+	echo \"GPIO out set\" >/proc/gpio/GPIO7
		+	sleep 1
		+	echo \"AF1 in\" > /proc/gpio/GPIO42
		+	echo \"AF2 out\" > /proc/gpio/GPIO43
		+	echo \"AF1 in\" > /proc/gpio/GPIO44
		+	echo \"AF2 out\" > /proc/gpio/GPIO45
		+	/usr/sbin/hciattach -s 115200 ttyS1 gumstix 921600 <-- (Infineon
		+	Manufacturer Mode is invoked here, within hciattach)
		+	/etc/init.d/S30bluetooth stop
		+	echo \"AF1 out\" > /proc/gpio/GPIO12
		+	echo \"GPIO out clear\" >/proc/gpio/GPIO7
		+	sleep 1
		+	echo \"GPIO out set\" >/proc/gpio/GPIO7
		+	sleep 1
		+	echo \"AF1 in\" > /proc/gpio/GPIO42
		+	echo \"AF2 out\" > /proc/gpio/GPIO43
		+	echo \"AF1 in\" > /proc/gpio/GPIO44
		+	echo \"AF2 out\" > /proc/gpio/GPIO45
		+	/usr/sbin/hciattach -s 921600 ttyS1 gumstix 921600 <-- (Will now
		+	connect at 921600 using this command only)
		+	--------------------------------------------------------------------------------------------------------------------------------------------------------------
		+	===BlueZ utilities===
		+	The BlueZ utilities version we were using was too old- V2.24, and it did not contain the appropriate 'infineon manufacturer mode' functions required to change the speed of the module. It gave the following output when trying to bring up the module-
		+
		+	----Read wrong response size: 4
		+	----0x04 0xff 0x01 0x00
		+
		+	We upgraded to BlueZ V3.24 and this solved the above problem, however
		+	we had to comment out the following lines in the 'gumstix_reset'
		+	function of 'hciattach.c'-
		+
		+	//system("echo clear > /proc/gpio/GPIO12");
		+	//system("echo set > /proc/gpio/GPIO12");
		+
		+	We felt these were more appropriate in S30Bluetooth.
		+	--------------------------------------------------------------------------------------------------------------------------------------------------------------
		+	===HCIATTACH commands===
		+	The Bluetooth appears to be on ttyS1, where previously it was present on ttyS3.
		+	Thus the following changes needed to be made to /etc/default/bluetooth-
		+
		+	HCIATTACH_TTY=ttyS1
		+
		+	...and we also had to put in new speed parameters to bring the module up properly after a kick-start-
		+
		+	HCIATTACH_START_SPEED=921600
		+	HCIATTACH_SPEED=921600
		+	--------------------------------------------------------------------------------------------------------------------------------------------------------------
		+	===Configure extra GPIOs===
		+	Lastly, some extra GPIOs needed to be configured as appropriate. We only discovered this when we looked at the Open Embedded version of /etc/init.d/bluetooth and discovered that it had some mysterious extra GPIOs being set, that were not present in the buildroot script or any documentation. These are the following-
		+
		+	echo AF1 out > /proc/gpio/GPIO12
		+	sleep 1
		+	echo GPIO out clear >/proc/gpio/GPIO7
		+	sleep 1
		+	echo GPIO out set >/proc/gpio/GPIO7
		+	sleep 1
		+	echo "AF1 in" > /proc/gpio/GPIO42 (Not present in buildroot)
		+	echo "AF2 out" > /proc/gpio/GPIO43 (Not present in buildroot)
		+	echo "AF1 in" > /proc/gpio/GPIO44 (Not present in buildroot, not
		+	documented)
		+	echo "AF2 out" > /proc/gpio/GPIO45 (Not present in buildroot, not
		+	documented)
		+
		+	The last two GPIOs (44/45) do not seem to be documented anywhere?- http://docwiki.gumstix.org/Gumstix_UARTs
		+	--------------------------------------------------------------------------------------------------------------------------------------------------------------
		+
		+	All of these changes were required to make the modules work properly.
		+
		+	We have also identified that the new v1.01 infineon module has improved pairing ability over its predecessor. Its predecessor required that a passkey be entered every time the unit connects to a paired device. The new module only requires a passkey once, and subsequent connection attempts are automatically connected, as they should be.
		+
		+
		+	Tomas Targownik
		+
		+
		+
		+	.