Easy to use framework for ROS2 FPGA-based hardware acceleration
based on ReconOS
You have to install ROS2 and ReconOS on your FPGA board. For getting started faster, there are preinstalled images:
The easiest way to burn the image on the sd card would be to use balena etcher. You can also use linux dd tool eg e.g.
dd if=/image.img of=/dev/<<yoursdcard>> bs=4M
you will also need an ethernet cable, and would need to configure your terminal to have a local ip in the range of 192.168.2.xx(Netmask 255.255.255.0) except 99; This is the ip of pynq board.
Configure the board to boot using SD card, using the jumper J4.
configure a serial terminal program. The COM port usually will be configured as
/dev/ttyUSB1 -serial -sercfg 115200,8,n,1,N
If everything works fine, you will see the device boot, and it will then automatically log you in as xilinx.
Since the generation of the hardware-mapped topics rely on raw message definition files, the mandatory submodules have to be updated after clone.
$ git submodule init && git submodule updateThe naming of standard message types is not consistant for ROS 2. Therefore, the naming of the message definition file must be changed for some cases (e.g. for the ReconROS Turtlebot 3 example, the UINT64 definition file (UInt64.msg to U_Int64.msg))
ReconROS uses an emulated docker container for the compilation of the application and building costum ROS message packages.
The first step for building ReconROS application is sourcing the environment by using the following command:
sudo apt install python3-colcon-common-extensions
This step is not only necessary for the installation process but also before compiling an application.
At the first time using ReconROS, the following command installs needed packages and builds the docker container for cross compiling.
$ bash tools/install.sh
Additionaly you might have to source
$ source /opt/ros/dashing/setup.bash
$ source /opt/Xilinx/Vivado/2017.1/settings64.sh
$ source <<ReconROSdir>>/tools/settings.sh
also, there might be some packages missing, you might have to enter the following command
$ sudo apt-get install g++-multilib
There are three sort demos available. The demo used in the following are based on pub/sub communication. The other two demos use ROS2 actions and services for the client server communication. Both demos require a preceding command for building the costum ROS2 message package.
$ rdk export_msg && rdk build_msg
ROS sort demo is based on pub/sub communication, and follows the same procedure as ROS sort demo services to build and run server and client applications. After client application is build, it will continually send unsorted data, and will receive sorted data back.
The other two demos use ROS2 actions and services for the client server communication. Both demos require a preceding command for building the custom ROS2 message package.
Navigate to /demos/ros_sort_demo_services/server_app/ and enter following commands
$ rdk export_msg && rdk build_msg
Navigate to the server demo folder. It contains the build.cfg file which is used by ReconROS. Before you can compile the application, you have to export the project:
$ rdk export_sw
and compile:
$ rdk build_sw
The hardware part is built analogously:
$ rdk export_hw
and synthesize:
$ rdk build_hw
navigate to server_app/build.msg, and copy custom message package to the fpga using scp
$ scp message_package.zip xilinx@192.168.2.99:/
it will ask for password, which is the same as username: xilinx
navigate to server_app/build.sw
before copying the application to the fpga, we have to make it executable and then copy it
$ sudo chmod +x sortdemo
$ scp sortdemo xilinx@192.168.2.99:/
navigate to server_app/build.hw/myReconOS.runs/impl_1
scp design_1_wrapper.bit xilinx@192.168.2.99:/
on the serial terminal
$ sudo su
then do cd/ and enter ls to check if if message_package.zip, design_1_wrapper.bit, and sortdemo have been copied on to the fpga
reconfigure the fpga using
$ cat design_1_wrapper.bit > /dev/xdevcfg
navigate to /opt/reconos and enter
./reconos_init.sh
then
$ source /opt/ros/dashing/setup.sh
navigate back, and create a directory mnt/project/build.msg/, and unzip message_package.zip
$ unzip message_package.zip -d /mnt/project/build.msg/
then in mnt/project/build.msg/ enter command
$ source install/local_setup.sh
then run the server application by
./sortdemo 0 1
where 0 1 are the hardware parameters.
if everything works fine, you should see server message that it is waiting for new data
The x86 client application can be compiled by using the colcon build command. Please note that ROS2 has to be installed on your machine.
first enter command
$ source /opt/ros/dashing/setup.sh
navigate to ros_sort_demo_service/client_app_x86/sorter_msgs and enter command
$ colcon build
$ source install/local_setup.bash
then do the same in ros_sort_demo_service/client_app_x86/sorter_client
and then finally
$ ros2 run sorter_client client
the client application on your machine which sends unsorted numbers to the server application and gets sorted data back.
For the ARM-based client application, the same procedure described for the server application have to be used.
this demo follows the same steps as services except for running of Client application.
first enter command
$ source /opt/ros/dashing/setup.sh
navigate to client_app_x86/sorter_msgs and enter command
$ colcon build
$ source install/local_setup.bash
then navigate back and enter command
$ python3 sort_action_client.py
you will see the progress messages both on server and client side.