Re: Re: [bluetooth] LMP and Software interface

Hi,
Please try to look at figure 1 in the bluetoooth design document. This figure
shows the hardware moduels block diagram.
WB bus connects between the cores on the module only. the module is connected
to the host using either UART or USB where HCI and higher level protocols run
on the host.
the module itself has a uC and so an OS (does not need ot be complex) and the
firmware that implements LMP, HCI on the module and the Basband configuration
and control. this schem enable us to be compatable with any HCI interface and
allow our system to be plugged into nay system without the need to know how
to configure our baseband or LMP. We have to be complient with the HCI
standard interface.
So what I am focusing now is the firmware located on the module that includes
the baseband driver, LMP, USB/UART drivers and HCI part on teh miodule.

If you know anyone who can help us please invite him.

Please leet us know your comments
Jamil

On 6/13/2003, "Mike Rowehl" <[email protected]> wrote:

>    I realize that I may have made some mistaken assumptions.  Please excuse
me
>if I'm asking questions that have already been discussed.  I had assumed
that
>the primary goal of the project was to produce a bluetooth module (baseband
+
>microcontroller + firmware + host interface).  But based on your comment
about
>choosing an OS and CPU, I see that I may have been incorrect.  Is the plan
to
>create a baseband which will be manipulated directly across the WISHBONE
bus
>by the host controller, and including LMP, HCI, and all higher levels
within
>the drivers running on the host?  Or do you just mean that we should
determine
>what microcontroller and operating system to use to run just the firmware
>functions?
>
>    The work that I've done with Bluetooth has primarily been with BlueZ,
which
>is very heavily influenced by the PC world view of the bluetooth device as
a
>UART, USB, or CardBus device.  With the low level functions of HCI, link
>management, and baseband encapsulated within black box third party modules,
I
>have unfortunately never had a chance to work a bluetooth system at the
>register level you have specified.  I also don't currently have a resource
I
>could draw on who has worked at this level.  There is some discussion going
on
>the bluez developers list for a while about Bluetooth qualification using
the
>BlueZ stack.  Some of the people involved in those discussions seem like
they
>may have the necessary background to provide you with the feedback you're
>looking for.  Perhaps post some information about the project on that list. 
I
>would assume that something like a fully open bluetooth core would be the
type
>of project that everyone working with the technology would be interested in
>seeing (but I'm know to be a bit over enthusiastic about open projects also
:-)
>
>                                                          Mike
>
>On  0, Jamil Khatib <[email protected]> wrote:
>>
>> Hi,
>> In fact what I am looking for is to define the hardware and software
>> interface between the baseband core and the software and firmware layers.
>>
>> Currently there is set of registers needed to configure teh core and get
teh
>> status and data from it. These registers should be used in LPM and all
higer
>> layers.
>> I'd like to know if there are other registers must be added or operations
>> must be done by hardware.
>>
>> Operating system and CPU selection is one of the main important tasks. We
>> should define them.
>>
>> In short we need to get all informations needed for the software to
operate
>> correctly with teh core.
>>
>>
>> Mike, as Mohamed said you may also join us in OFOQ project and help us in
>> poriting uLinux to it.
>> If you have any software that you can share with us for bluetooth let us
>> know. We are planing to build and open source bluetooth module after we
get
>> everything ready.
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: nour-unsubscribe-bZJqt4gKw0dwc45b+y0WwMLKnirKmNT7@public.gmane.org
>For additional commands, e-mail: [email protected]
>Handasa Arabia, http://www.handasarabia.org

---------------------------------------------------------------------
To unsubscribe, e-mail: nour-unsubscribe-bZJqt4gKw0dwc45b+y0WwMLKnirKmNT7@public.gmane.org
For additional commands, e-mail: [email protected]
Handasa Arabia, http://www.handasarabia.org