Re: [NOUR] Re: [bluetooth] LMP and Software interface

["Jamil Khatib" <khatib@opencores.org>]

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.


Regards,
Jamil Khatib

On 6/12/2003, "Mike Rowehl" <mike@unrooted.net> wrote:

>    I can tell you about the projects I've worked on before. 
Professionaly,
>I'm an embedded systems programmer working with Linux.  I've done a bunch
of
>work porting drivers in particular, mostly ARM and x86 work.  The drivers
are
>just about everything from simple UART style interfaces to video encoders.
>Most recently I've been working with BlueZ for a couple of demo projects,
and
>I got involved with this project specifically to get some more exposure to
the
>lower level operations of Bluetooth.  I'm not all that hardware handy in
terms
>of design or fabrication, but I can sit down with a schematic and an
>oscilloscope and figure out where problems are.  I've done some basic 8051
and
>6502 firmware work, but nothing too noteworthy there.
>    That said, I don't have enough background yet to make any informed
comments
>about the register level interface described in the NOUR specification. 
I'm
>just starting to develope my understanding of the HCI layer, and haven't
looked
>down into the baseband layer at all.  So I'm sorry, I don't believe I could
>help immediately in this regard.
>    I was actually wondering in general how someone like myself would start
>contributing given the state that the project is in so far.  Are there some
>modeling or simulation tools we could start taking advantage of to prove
out
>this design before attempting to fabricate?  Or should I just dig into the
spec
>some more and wait till this lower level work is completed?
>
>                                                     Mike
>
>On  0, Mohamed Salem <mohamed.salem@handasarabia.org> wrote:
>> I think  "Mike Rowehl" would provide us with his done work. hey Mike,
>> You can consider this as a trigger to show project members what you have
>> developed before and what you can add to NOUR ...
>> Thanks ..
>>
>> Best Regards,
>> Mohamed Salem
>> Handasa Arabia Organization
>> www.handasarabia.org
>>
>> ps. Please all ACTIVE members of the project move toward the NOUR list
>> on Handasa Arabia Project.
>>
>>
>> On Wed, 2003-06-11 at 16:15, Jamil Khatib wrote:
>> > Hi all,
>> >
>> > I am looking for someone who has experience in bluetooth software and
>> > firmware who can give us his feedbacks about the registers and the
system
>> > configuration.
>> > We need feedback about this issue before we can make a new release of
the
>> > project design document.
>> >
>> >
>> >
>> > Note: I am going to continue sending emails to bluetooth@opencores.org
till
>> > we move completely to nour@lists.handasarabia.org
>> >
>> > Regards,
>> > Jamil Khatib
>> >
>> > ps. Do you have any available blocks for integration?
>> >
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: nour-unsubscribe@lists.handasarabia.org
>For additional commands, e-mail: nour-help@lists.handasarabia.org
>Handasa Arabia, http://www.handasarabia.org

--
To unsubscribe from bluetooth mailing list please visit http://www.opencores.org/mailinglists.shtml