Re: [bluetooth] RF (our interface)

[Jamil Khatib <jamilkhatib75@yahoo.com>]

--- Ling Su <lingsu@palmmicro.com> wrote:
> > As a result of previouse discussion, we can define
> our
> > simple RF interface that can be mapped to any
> exteranl
> > RF interfaces (SPI, JTAG or any other interface)
> >
> > here are some pins that I recall to be added
> > . Tx Enable
> > . Rx Enable
> > . Tx Data bit
> > . Rx Data Bit
> > . Hop bus
> > . RF Register address
> > . RF Regsiter data in
> > . RF Register Data out
> > . BT state bus ??? this to define sommunication
> > between RF and baseband state machines such as
> power
> > mode
> [Ling] The hop bus should be mergerd with Register
> bus, since it is just an
> register to be set. 
OK but should baseband control all RF registers? I
think there are some that can be controllered or at
least read from higher layers such as status
registers.


Some other like clk should be
> taken into account, RF
> chip usually proivde accurate close for data
> sampling and transmission,
> usually (13MHz and 1MHz both).
> 
Also there is low power clock but should we be the
source of these clocks. may be we can leave such
clocks variables and supplied from external
oscillators and provide the internal logic for them??


> >
> > Do you have any comment on this interaface? do you
> > think that it is easy to add a bridge to SPI or
> JTAG
> > interfaces?
> >
> SPI and JTAG can be two types of Register bus, using
> very simliar protocol.
> We can definitely use a bridge.
> 
good

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


__________________________________________________
Do You Yahoo!?
Spot the hottest trends in music, movies, and more.
http://buzz.yahoo.com/
--
To unsubscribe from bluetooth mailing list please visit http://www.opencores.org/mailinglists.shtml