On Sun, 17 Feb 2008 02:04:54 -0800 (PST), Narendra Sisodiya wrote:
>Hi, My Project title is "Serial RF Core for Multimedia Stream
>Transfer"
>I am using Xilinx Video Starter Kit, and I supposed to transfer a
>video stream over RF, using Bluetooth,
>I am totally confused
Thanks for being so honest :-)
I think your first and by far your most important task is
to have a long and open discussion with your prof about
what the real objectives of this project should be.
Like many technology tasks, it's something that you *could*
do with off-the-shelf components and software. Somewhere,
buried in all of it, there is an interesting project
trying to get out. But if you were to try to do *all*
of it as a project (undergraduate? masters?) then you are
sure to fail horribly, because there is simply far too
much in it. Let's look at the whole thing:
* video source
* video capture into memory
* video compression (Bluetooth data rate is
far too slow for raw video)
* buffering for streaming
* package the data in an appropriate form for
delivery over Bluetooth
* Bluetooth link
* reversing the above steps to recover a
useful video stream for display
Which parts of this do you plan to do yourself?
Bluetooth is pretty complicated at all levels,
and no-one in their right mind would try to do
it from scratch; you simply buy the modules.
Every one of the other parts of the chain is
similarly a solved problem. Some of it is best
done in software, some is best done in hardware.
Some parts of the problem make sense as an
FPGA
project (camera interface, compression) but are
so common that it's just a matter of tailoring
existing freely-available design examples.
For me, the really tough parts would be the
software (in particular, device drivers) but
other folk would find that straightforward and
would find other parts difficult.
Choose your project focus, in collaboration with
your prof. Agree with him/her what pre-built
components you can use as a starting point. Learn
about those pre-built components so that you can
see what to do around them - how to interface to
them, what data rates they support, that sort of
thing. Look at the overall architecture that is
required, and try to get an estimate of how much
work is involved in each piece. Whatever you try
to do first, make sure that you can test it stand-
alone so that your project has *some* useful outcome
even if it's never completed.
PLAN and DISCUSS. And, as a last resort, don't be
ashamed to ask your prof for a project that has a
somewhat narrower scope. (Actually, the very last
resort is a career change; but that's a bit drastic.)
Good luck.
--
Jonathan Bromley, Consultant
DOULOS - Developing Design Know-how
VHDL * Verilog * SystemC * e * Perl * Tcl/Tk * Project Services
Doulos Ltd., 22 Market Place, Ringwood, BH24 1AW, UK
[email protected]
http://www.MYCOMPANY.com
The contents of this message may contain personal views which
are not the views of Doulos Ltd., unless specifically stated.