Difference between revisions of "SP VISION"
(→On the APF27_Dev) |
m (→On the APF*_Dev) |
||
(4 intermediate revisions by 2 users not shown) | |||
Line 8: | Line 8: | ||
This virtual component is available in [http://periphondemand.git.sourceforge.net/git/gitweb.cgi?p=periphondemand/periphondemand;a=tree;f=src/library/components/sp_vision_configure;h=babdb0b05178267c1a8d077b0a1c5737820dea0e;hb=HEAD POD library], but if you don't want to make special design just for configuration, a standard design is provided in armadeus tree. | This virtual component is available in [http://periphondemand.git.sourceforge.net/git/gitweb.cgi?p=periphondemand/periphondemand;a=tree;f=src/library/components/sp_vision_configure;h=babdb0b05178267c1a8d077b0a1c5737820dea0e;hb=HEAD POD library], but if you don't want to make special design just for configuration, a standard design is provided in armadeus tree. | ||
− | == On the | + | == On the APF*_Dev == |
* First select the driver for sp_vision_configuraton under linux-menuconfig : | * First select the driver for sp_vision_configuraton under linux-menuconfig : | ||
<pre class="host"> | <pre class="host"> | ||
− | [ ]$ make | + | [ ]$ make linux-menuconfig |
</pre> | </pre> | ||
Line 30: | Line 30: | ||
then | then | ||
<pre class="host"> | <pre class="host"> | ||
− | [ ]$ make | + | [ ]$ make linux |
[...] | [...] | ||
[ ]$ make | [ ]$ make | ||
Line 36: | Line 36: | ||
</pre> | </pre> | ||
− | + | The configuration bitstream can be found under the directory ''firmware/pod_scripts/'' and it's named '''apf27_spvision_loader.bit''' for APF27 and '''apf51_spvision_loader.bin''' for APF51. To configure the second (sp_vision) FPGA, first FPGA on APF* must be configured with this bitstream. | |
* Configure the first fpga (if you transfer files by nfs): | * Configure the first fpga (if you transfer files by nfs): | ||
<pre class="apf"> | <pre class="apf"> | ||
# modprobe fpgaloader | # modprobe fpgaloader | ||
− | # | + | </pre> |
+ | On APF27: | ||
+ | <pre class="apf"> | ||
+ | # load_fpga apf27_spvision_loader.bit | ||
+ | </pre> | ||
+ | On APF51: | ||
+ | <pre class="apf"> | ||
+ | # load_fpga apf51_spvision_loader.bin | ||
</pre> | </pre> | ||
Line 47: | Line 54: | ||
# modprobe sploader | # modprobe sploader | ||
# modprobe sploader_prober | # modprobe sploader_prober | ||
− | # dd if= | + | # dd if=your_sp_vision_bitstream.bit of=/dev/sp_loader |
</pre> | </pre> | ||
− | |||
− | |||
− | |||
= Communicate with sp_vision = | = Communicate with sp_vision = | ||
+ | {{Under_Construction}} |
Latest revision as of 17:18, 4 September 2013
Contents
Introduction
The SP_Vision board is an extension of APF27Dev and APF51Dev with a Spartan6 and two DDR. It is designed for real-time video processing.
Configure the sp_vision fpga
SP_Vision FPGA configuration is done through APF* FPGA, then to configure the SP_Vision FPGA you will need a configuration virtual component called sp_vision_configure under the APF*'s onboard FPGA. This virtual component is available in POD library, but if you don't want to make special design just for configuration, a standard design is provided in armadeus tree.
On the APF*_Dev
- First select the driver for sp_vision_configuraton under linux-menuconfig :
[ ]$ make linux-menuconfig
Device Drivers ---> Armadeus specific drivers ---> FPGA Drivers ---> [...] [*] virtual components [...] [*] Board designs [...] <M> board driver for sp_vision fpga loader
then
[ ]$ make linux [...] [ ]$ make [...]
The configuration bitstream can be found under the directory firmware/pod_scripts/ and it's named apf27_spvision_loader.bit for APF27 and apf51_spvision_loader.bin for APF51. To configure the second (sp_vision) FPGA, first FPGA on APF* must be configured with this bitstream.
- Configure the first fpga (if you transfer files by nfs):
# modprobe fpgaloader
On APF27:
# load_fpga apf27_spvision_loader.bit
On APF51:
# load_fpga apf51_spvision_loader.bin
- Once the first FPGA configured, just do :
# modprobe sploader # modprobe sploader_prober # dd if=your_sp_vision_bitstream.bit of=/dev/sp_loader
Communicate with sp_vision
Page under construction... Informations on this page are not guaranteed !!