Re: What is the status of stack HCI and above?

On  0, Mohamed Salem <[email protected]> wrote:
> Hi Shrirang,
> Thanks for your interest to work in the stack layers that might be a
> part of our development in NOUR. 
> The attached document compiled by "Mike Rowehl" would help you in
> understanding the development organization for the bluetooth overall
> system from a perspective that might be close to yours , as I guess you
> are more into software development ..
> please, review the document and feel free to post your queries ..This
> would be so helpful to get you a place for the upcoming development
> cycle of the project...
> 
> Best Regards,
> 
> Mohamed A.Salem
> 
> On Mon, 2003-08-25 at 11:12, Shrirang Bhagwat wrote:
> > Hi,
> > 
> >   I work in bluetooth and would like to contribute something in upper layers 
> > of the stack... What is the current status of the stack?

If you work with Bluetooth currently, we could certainly use your insight 
regarding the work we've done so far.  I've only worked with Bluetooth as a 
hobbyist, and I think there might be some important details that I've missed
which would be instantly apparent to someone with more familiarity.

Just as a brief recap, we started out with a NOUR specification document.
That gives some overview of the structure of the baseband components and the
registers used to interface with them.  What we have been doing is trying to
validate that document, ensuring that the low level register interface is
sufficient to provide the firmware with the control it would need.  
Unfortunately, none of us has ever worked with Bluetooth modules at the
firmware level before.  So this step has been taking us a while to get through.
The idea that I had put forth was something I hope will get us over this 
hurdle, but we're certainly open to suggestions.  Especially if you've worked
doing firmware before and have any idea how this design is normally done.

The NOUR project files are available at:

http://www.handasarabia.org/folder.php?id=18

Definitely take a look at the specification, there's lot of info in there.
(I'm assuming you already have the Bluetooth 1.1 specification if you've been 
working in the field).  The RF Link daemon posted there is a snippet of code
I wrote to provide a concrete implementation of shuffling bits from one place 
to another using some operations we had discussed on the mailing list.  At
present it doesn't do anything NOUR specific.  We should be able to use it if
we want to run a simulation, but depending on what environment we pick up it
might not be necessary.

And that's pretty much where it stands as a whole.  We have a specification for
some hardware and need to make sure it's correct, preferably without just
building the stuff and starting work.  Simulation seems like the natural
answer, but I haven't found any tools which specificly model this operation.
There are tools which model Bluetooth, but they model at the network level for
the most part - modeling the interaction between devices.  What we need is a 
subsystem modeler, so that we can treat different components within the module
seperatly.  At least that's what we think we need.  If you have any ideas, 
either of how to get the simulation working, or ideas of things we should be
doing instead of simulation, please let us know.

                                                    Mike


--------------------------
NOUR Mailing List
Handasa Arabia Organization
http://www.handasarabia.org

Message number 49