Difference between revisions of "FPGA loader"

From ArmadeusWiki
Jump to: navigation, search
(Driver usage)
m (Driver usage)
 
(52 intermediate revisions by 6 users not shown)
Line 1: Line 1:
On this page, you will find all the informations needed to use the FPGA loader driver.
+
[[Category: FPGA]]
  
== Module compilation & installation==
+
On this page, you will find all the informations needed to use the Linux FPGA loader driver.
The first thing you have to do is to compile the driver. The only way to do that actually is to compile it as a module:
+
This driver allows you to load the FPGA of your APF board from Linux userspace/shell (ie FPGA reprogrammation after Linux boot).
# cd target/linux/modules/fpga_devtools
+
Compile it:
+
# make ARCH=arm CROSS_COMPILE=/local/Armadeus/buildroot/build_arm_nofpu/staging_dir/bin/arm-linux-
+
  
When compiled, you will obtain 1 module and one progam:
+
== Driver installation==
* fpgaloader.ko: this is the driver.
+
Driver is installed in default Armadeus rootfs.
* fpgaregs: this is a small tool which allows accessing the FPGA from the user space without driver. This is especially usefull during development phases.
+
  
Then, you have to:
+
For the hackers, code is located in ''target/linux/modules/fpga/dev_tools/fpga_devtools/''.
* copy the module on your rootfs in /lib/modules/drivers/
+
After that you can launch:
+
# insmod /lib/modules/drivers/fpgaloader.ko
+
The default FPGA version is the spartan3 200k.
+
The version can be changed when installing the module (insmod /lib/modules/drivers/fpgaloader.ko 0 or 1). These informations are given by the proc interface.
+
  
 
== Driver usage ==
 
== Driver usage ==
The FPGA loader driver is usable through 1 interface:
 
# use /proc/drivers/fpga/loader to read the available configurations
 
To upload a new firmware, write:
 
# dd if=fpga_test.bit of=/dev/fpga/loader
 
  
== FPGARegs usage ==
+
*To upload a new firmware, use the small helper script that can do all the job for you (load driver and then firmware). Just call it with the bitfile (.rbf for APF6SP and .bin for the other boards) as parameter. For example:
Write to a FPGA address
+
<pre class="apf">
* fpgareg addr value
+
# load_fpga bramtest_top_apf.bin
ex: fpgaregs 0x1000 0xabcd
+
</pre>
this will write 0xabcd (16bits only interface) at the FPGA internal address 0x1000
+
  
Read a FPGA address
+
* For APF6_SP a periph.rbf must be [[Target_Software_Installation#APF6_SP | loaded in U-Boot]] before, the core.rbf can then be loaded under linux with load_fpga:
* fpgareg addr
+
<pre class="apf">
ex: fpgaregs 0x1000
+
# load_fpga firmware.core.rbf
this will read the address 0x1000
+
</pre>
 +
* [[Simple_blinking_LED |  You can find some ready to use bitfiles in ''firmware/leds/blinking_led/bin/'' (blinking LED).]]
 +
 
 +
{{Note| On '''APF6_SP''' the command load_fpga work only throught PCIe, see [[PCIe fpga load]] to know how it works}}
 +
 
 +
==Troubleshots==
 +
=== APF51 ===
 +
* Use binary format '''.bin''', bitstream format '''.bit''' doesn't work.
 +
 
 +
All the troubleshots are handled by the ''/usr/bin/load_fpga'' utility, mentionned above.
 +
 
 +
[[Category:FPGA]]

Latest revision as of 07:41, 27 August 2015


On this page, you will find all the informations needed to use the Linux FPGA loader driver. This driver allows you to load the FPGA of your APF board from Linux userspace/shell (ie FPGA reprogrammation after Linux boot).

Driver installation

Driver is installed in default Armadeus rootfs.

For the hackers, code is located in target/linux/modules/fpga/dev_tools/fpga_devtools/.

Driver usage

  • To upload a new firmware, use the small helper script that can do all the job for you (load driver and then firmware). Just call it with the bitfile (.rbf for APF6SP and .bin for the other boards) as parameter. For example:
 # load_fpga bramtest_top_apf.bin
  • For APF6_SP a periph.rbf must be loaded in U-Boot before, the core.rbf can then be loaded under linux with load_fpga:
 # load_fpga firmware.core.rbf
Note Note: On APF6_SP the command load_fpga work only throught PCIe, see PCIe fpga load to know how it works


Troubleshots

APF51

  • Use binary format .bin, bitstream format .bit doesn't work.

All the troubleshots are handled by the /usr/bin/load_fpga utility, mentionned above.