This is an old revision of the document!
This server's IP should be 192.168.40.1
Packages
Required packages for cross platform development:
sudo yum install yum-plugin-fastestmirror sudo yum install bison flex gperf libtool texinfo gcc gcc-c++ gmp-devel gcc-java sudo yum install wget sudo yum install patch sudo yum install ncurses ncurses-libs sudo yum install ncurses-devel sudo yum install kernel-devel sudo yum install subversion git sudo yum install glibc-static sudo yum install libstdc++-staticr sudo yum install expat-devel.i686 expat-devel.x86_64 expat-static.i686 expat-static.x86_64 expat.i686 expat.x86_64
NFS Server
We will need to run an NFS server to host a NFS root file system for CoBo.
sudo yum install nfs-utils
edit /etc/idmapd.conf
# change domain Domain = cobo.serv
# edit exports /etc/exports and append
/home/attpc/dev/coborootfs 192.168.40.40(rw,insecure,no_root_squash,sync,fsid=0) /mnt/local/export/filesystem 192.168.40.45(rw,insecure,no_root_squash)
The second line in exports is just for ML507 Reduced CoBo compatibility.
Finally, run the following launch the nfs server:
sudo systemctl start rpcbind.service sudo systemctl start nfs-server.service sudo systemctl start nfs-lock.service sudo systemctl start nfs-idmap.service sudo systemctl enable rpcbind.service sudo systemctl enable nfs-server.service sudo systemctl enable nfs-lock.service sudo systemctl enable nfs-idmap.service
DHCP server
The DHCP server is required to allow different CoBo boards lease an IP. Currently, we are using static IPs based on the MAC address of each CoBo. This is a good practice for development, however, in deployment it might be just easier to assign random IPs, depending on the setup required.
sudo yum install dhcp
Then edit /etc/dhcp/dhcpd.conf
ddns-update-style none; option domain-name "cobo.serv"; option domain-name-servers 192.168.40.1; default-lease-time 600; max-lease-time 7200; authoritative; log-facility local7; subnet 192.168.0.0 netmask 255.255.0.0 { range 192.168.40.80 192.168.40.90; option routers 192.168.40.1; option subnet-mask 255.255.255.0; option broadcast-address 192.168.40.254; option domain-name-servers 192.168.40.1; option ntp-servers 192.168.40.1; } # CoBo host cobo02e0 { hardware ethernet 00:0A:35:00:00:00; fixed-address 192.168.40.40; option host-name "cobo02e0"; } host cobo02e1 { hardware ethernet 00:0A:35:00:00:01; fixed-address 192.168.40.41; option host-name "cobo02e1"; } host rcobo { hardware ethernet 00:0A:35:02:2A:C5; fixed-address 192.168.40.46; option host-name "rcobo"; } host vxcobo { hardware ethernet 00:0A:35:01:02:04; fixed-address 192.168.40.45; option host-name "cobovx"; } host dev-workstation { hardware ethernet 01:02:03:04:05:06:07; fixed-address 192.168.40.47; option host-name "dev-workstation"; }
The dev-workstation
entry in the DHCP config file is useful to have. This machine can be used to test or debug CoBo software that is network related.
Finally run the following to launch the dhcp daemon:
sudo service dhcpd enable sudo service dhcpd start
Xilinx Drivers
You have to install 3rd party Xilinx USB cable drivers, link if you want to flash or program the FPGA from Linux.