[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bluetooth] Re: crc
Hi,
I am so sorry for the delay.
Sudheer P v wrote:
> Hi Khatib,
> I have checked the bluetooth standard to know about
> the initialisation of crc register. It is given that
> the lower 8 bits are initilised to upper address bit
> of master or slave. But i don't what the address...so
> please help me.
it is hte upper address of the BD_ADDR in the standard, anyhow you do not need it it should be an input to the CRC block because it will change according to the system state which will be controlled by the sytem controller.
> Just to update you about what i did today..
> i have written a simple test bench for the crc code.
> i have initialized entire lfsr register to zero.
> i am attaching the code along with this mail. Using
> that test bench i have generated the crc for 16 bit
> data. Kindly inform me that whether i am going in
> right direction or not
I think we have to define a way to manage all of the files, blocks and coding style so as to enable others to join hte coding.
I put in hte CVS a vhdl package that defines hte system constants.
We should also agree on hte naming conventions of hte files and ports.
I suggest to follow the open cores vhdl coding style and to put the entity and architecture in different files.
Port names should start with Capital letter and names as in the bluetooth design document.
I'll depend on every one to test and verify his block and if possible to provide the logic resources and timing information after synthesis.
Please let me know your suggestions.
Jamil Khatib
>
> with regards
> Sudheer
>
>
>
>
--
To unsubscribe from bluetooth mailing list please visit http://www.opencores.org/mailinglists.shtml