Linux bluetooth development
 help / color / mirror / Atom feed
* [Bluez-devel] High speed serial connection (Was: Bluez article on OReillyNet)
@ 2006-10-03 14:46 Guylhem Aznar
  2006-10-03 15:33 ` Peter Wippich
  0 siblings, 1 reply; 4+ messages in thread
From: Guylhem Aznar @ 2006-10-03 14:46 UTC (permalink / raw)
  To: BlueZ development

Hello,

On 10/3/06, Peter Wippich <pewi@gw-instruments.de> wrote:
> Depending on your system it is most likely that the HW Uart extension is
> not realy supported by the serial driver. I currently only know for sure
> for PXA type system. You need a special HWUART driver to take advantage of
> the HWUART.

There are 4 ARM systems I can have access to :

- A Zaurus 6000, which is a PXA 255

- A Zaurus C860, which is also a PXA 255.

- An Acer N30, but it's a s3c2410, which is quite different.

- A Simpad - however it is a SA 1100, which has no HWUART. Moreover,
its bluetooth module needs some reflashing (which I can't do). It is
on ttySA1 - cf http://www.guylhem.net/r-hardware/simpad/bluetooth/ for
the hardware part, http://opensimpad.org/index.php/Simpad.c for the
software part.

> For a PXA system we may help you out if you insist.

Yes please. I would make a great base for the article.

> Further you may get problems with the RS232 driver chips usualy
> used. If you're able to connect the serial bluetooth module directly to
> the ARM UART lines (Rx / Tx / RTS /CTS) (3 Volt interface without RS232
> driver on both sides) this would be much better.

On the Zaurus 6000, I didn't add the module myself, but I think it's
on 3.3 V directly. It is also on the UART that can be rerouted to
HWUART (FTUART ?)

On the C860, it is directly soldered to the UART lines - yet to ones
of the standard serial port - ttyS0, which I think is STUART (will
check tonight) and which can not be rerouted to HWUART IIRC.

On the N30, it is on ttySAC2, MMIO 0x50008000.

The demo could use either a 2.4 or 2.6 kernel. There is a 2.4 on
the 6000 and the Simpad, and a 2.6 on the N30 and 860, but putting a
2.6 on the 6000 wouldn't be a problem.

Tell me if you need more information.

Guylhem

-------------------------------------------------------------------------
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
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bluez-devel] High speed serial connection (Was: Bluez article on OReillyNet)
  2006-10-03 14:46 [Bluez-devel] High speed serial connection (Was: Bluez article on OReillyNet) Guylhem Aznar
@ 2006-10-03 15:33 ` Peter Wippich
  2006-10-04  9:20   ` Guylhem Aznar
  0 siblings, 1 reply; 4+ messages in thread
From: Peter Wippich @ 2006-10-03 15:33 UTC (permalink / raw)
  To: BlueZ development

[-- Attachment #1: Type: TEXT/PLAIN, Size: 3402 bytes --]


Hi Guylhem,

On Tue, 3 Oct 2006, Guylhem Aznar wrote:

> Hello,
> 
> On 10/3/06, Peter Wippich <pewi@gw-instruments.de> wrote:
> > Depending on your system it is most likely that the HW Uart extension is
> > not realy supported by the serial driver. I currently only know for sure
> > for PXA type system. You need a special HWUART driver to take advantage of
> > the HWUART.
> 
> There are 4 ARM systems I can have access to :
> 
> - A Zaurus 6000, which is a PXA 255 
> - A Zaurus C860, which is also a PXA 255.
This two shall work with a HWUART driver. Make sure the BT Chip is 
connected to the BTUART, which is shared with the HWUART (/dev/ttyS1).  

> - An Acer N30, but it's a s3c2410, which is quite different.
Don't have an s3c2410 system anymore.... 

> - A Simpad - however it is a SA 1100, which has no HWUART. Moreover,
Never used this one .... 
 
> Yes please. I would make a great base for the article.

Ok, but be warned. It will not run out of the box and is only tested with 
2.6.14 kernel. I've attached the driver source and a modified Kconfig and 
Makefile. This will go to linux/drivers/bluetooth/ . You also have to edit 
the Kconfig to get the driver enabled for your machine type. 

Than you have to set up a platform device for the HWUART and disable the 
standard UART driver (to avoid conflicts). This must be somewhere within 
/linux/arch/arm/mach-pxa/ 

Where exactly depends on your machine type. For the standard kernel I 
think it is within generic.c. Look for something like 

static struct platform_device btuart_device = {
        .name           = "pxa2xx-uart",
        .id             = 1,
};

And replace this with 

#if defined(CONFIG_ROAD_S101_BTHWUART) || defined(CONFIG_ROAD_S101_BTHWUART_MODULE) 
//-----------------------------------------------------------------------------
// HW Uart for Bluetooth 
//-----------------------------------------------------------------------------
static struct platform_device hwuart_device = {
    .name   =           "road_btuart", 
    .id     =           -1 ,
} ;
#else
static struct platform_device btuart_device = {
        .name           = "pxa2xx-uart",
        .id             = 1,
};
#endif 

Finaly you need to make sure the driver gets initialized. 
Within the platform device structure

( static struct platform_device *platform_devices[] __initdata = ) 

look for btuart_device and replace it with
 
#if defined(CONFIG_ROAD_S101_BTHWUART) || defined(CONFIG_ROAD_S101_BTHWUART_MODULE)
        &hwuart_device,
#else
        &btuart_device,
#endif 

Further the driver itself defines a function bt_enable(..) which is 
hardware dependend. As a first attempt you may simply comment out 
everything in this function. The driver also assumes a fixed baud rate of 
921600. There is a command line switch to use 115200, but it will not 
switch to higher baud rates (115200 is fairly standard, so this may help 
testing). To get the higher baud rate you have to change the standard baud 
rate of your bluetooth module. If it is CSR based you can use the pstools 
supplied with the bluez utils. 

Good luck ! 

Peter 

|       Peter Wippich                   Voice: +49 30 46776411          |
|       G&W Instruments GmbH            fax:   +49 30 46776419          |
|       Gustav-Meyer-Allee 25, Geb. 12  Email: pewi@gw-instruments.de   |
|       D-13355 Berlin  / Germany                                       |

[-- Attachment #2: Type: APPLICATION/x-gtar, Size: 7885 bytes --]

[-- Attachment #3: Type: text/plain, Size: 348 bytes --]

-------------------------------------------------------------------------
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

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bluez-devel] High speed serial connection (Was: Bluez article on OReillyNet)
  2006-10-03 15:33 ` Peter Wippich
@ 2006-10-04  9:20   ` Guylhem Aznar
  2006-10-04 10:38     ` Peter Wippich
  0 siblings, 1 reply; 4+ messages in thread
From: Guylhem Aznar @ 2006-10-04  9:20 UTC (permalink / raw)
  To: BlueZ development

Hello

On 10/3/06, Peter Wippich <pewi@gw-instruments.de> wrote:
> > - A Zaurus 6000, which is a PXA 255
> > - A Zaurus C860, which is also a PXA 255.
> This two shall work with a HWUART driver. Make sure the BT Chip is
> connected to the BTUART, which is shared with the HWUART (/dev/ttyS1).

Not on the C860: /dev/ttyS0, and neither on the 6000 : /dev/ttyS2

But sharp gives weird names to their serial ports that do not reflect
the uart connection - I will check the addresses directly in the
sourcecode and guess the correct uart=E9

> Ok, but be warned. It will not run out of the box and is only tested with
> 2.6.14 kernel. I've attached the driver source and a modified Kconfig and
> Makefile. This will go to linux/drivers/bluetooth/ . You also have to edit
> the Kconfig to get the driver enabled for your machine type.

I'll try to tweak it and let you know my results. Can I put a kernel
sourcetree somewhere for you to see?

BTW I notice it comes from the ROAD S101. Any news on the device ?
I am eager to see it reaching the market to review it. Last seen on
press releases in Auguest.

Guylhem

-------------------------------------------------------------------------
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=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Bluez-devel] High speed serial connection (Was: Bluez article on OReillyNet)
  2006-10-04  9:20   ` Guylhem Aznar
@ 2006-10-04 10:38     ` Peter Wippich
  0 siblings, 0 replies; 4+ messages in thread
From: Peter Wippich @ 2006-10-04 10:38 UTC (permalink / raw)
  To: BlueZ development

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1464 bytes --]


Hi Guylhem, 

On Wed, 4 Oct 2006, Guylhem Aznar wrote:

> Not on the C860: /dev/ttyS0, and neither on the 6000 : /dev/ttyS2
> 
> But sharp gives weird names to their serial ports that do not reflect
> the uart connection - I will check the addresses directly in the
> sourcecode and guess the correct uarté
Ok, the driver assumes that the BTUART is used because this one shares the 
Pins with the HWUART. If the connection is different (HWUART pins can be 
used on other pins as well) it may be possible to change the driver, but 
in this case the schematics are needed. 
 
> I'll try to tweak it and let you know my results. Can I put a kernel
> sourcetree somewhere for you to see?
Just send me the /arch/arm/mach-pxa/ folder. This should contain 
everything needed. 
 
> BTW I notice it comes from the ROAD S101. Any news on the device ?
> I am eager to see it reaching the market to review it. Last seen on
> press releases in Auguest.
I can't tell you. I'm only doing development for this device and even if I 
would have some more detailed marketing information I would not be allowed 
to talk about ;-).  

Ciao, 

Peter 


|       Peter Wippich                   Voice: +49 30 46776411          |
|       G&W Instruments GmbH            fax:   +49 30 46776419          |
|       Gustav-Meyer-Allee 25, Geb. 12  Email: pewi@gw-instruments.de   |
|       D-13355 Berlin  / Germany                                       |

[-- Attachment #2: Type: text/plain, Size: 348 bytes --]

-------------------------------------------------------------------------
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

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2006-10-04 10:38 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-03 14:46 [Bluez-devel] High speed serial connection (Was: Bluez article on OReillyNet) Guylhem Aznar
2006-10-03 15:33 ` Peter Wippich
2006-10-04  9:20   ` Guylhem Aznar
2006-10-04 10:38     ` Peter Wippich

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox