blob: 79675634716396bce04b8e4f9681271110d8e52d [file] [log] [blame]
briansa39ed322013-02-14 23:00:51 +00001This file contains instructions on how to set up a computer to build the code.
2
3[Install Packages]
4First, you have to download and follow the directions in
5 <http://robotics.mvla.net/files/frc971/packages/frc971.list>.
6You also have to follow the directions at
7 <http://backports-master.debian.org/Instructions/>.
8Then, run `apt-get install subversion git g++-multilib gcc-multilib ruby patch \
9 make openjdk-6-jdk lib32event-dev`
10 and `apt-get install -t squeeze-backports swig` (package lists correct for
11 amd64 Squeeze; you might be able to get it to build on other
12 versions/platforms/distributions (Ubuntu, Mint, ...) if you can find the
13 right packages.
14 You will have to accept the
15 "WARNING: The following packages cannot be authenticated!" warning for the
16 "libevent-2.0-5 lib32event-2.0-5 libevent-core-2.0-5 lib32event-core-2.0-5 \
17 libevent-extra-2.0-5 libevent-pthreads-2.0-5 libevent-openssl-2.0-5 \
18 libevent-dev lib32event-extra-2.0-5 lib32event-pthreads-2.0-5 \
19 lib32event-openssl-2.0-5 lib32event-dev" packages.
20Also run `apt-get install powerpc-wrs-vxworks` if you want to be able to build
21 the cRIO code too.
22 NOTE: That is in *addition* to the above command.
23 You will have to accept the
24 "WARNING: The following packages cannot be authenticated!" warning for the
25 "powerpc-wrs-vxworks" package.
26If you want to actually download code to a robot (it will only work on amd64
michaela91ebd92013-02-23 06:01:00 +000027 Squeeze), then
28 (1) do `apt-get install ncftp rsync socat`.
29 socat is used for the netconsole.sh tool that is used to talk to the cRIO.
30 (2) Add robot and the following to the /etc/hosts file. This requirement
31 should go away in the future.
32 10.9.71.179 fitpc
33 10.9.71.2 robot
34 (3) Set the IP address of the downloading machine to be on the same subnet.
35 ifconfig eth0 10.9.71.22
36 This will need to be redone when the computer Ethernet connection is
37 reset. For example, it is reset by disconnecting and reconnecting
38 the Ethernet cable or power cycling the robot. Check it with
39 ifconfig eth0
briansa39ed322013-02-14 23:00:51 +000040
41[Running Locally]
42If you want to be able to run the realtime code on your development machine
43 without just disabling the realtime part (set the AOS_NO_REALTIME environment
44 variable), follow the directions in /src/aos/config/aos.conf.
michaela91ebd92013-02-23 06:01:00 +000045
46[Compiling and Downloading]
47Run `./build.sh` from src/frc971/atom_code/ and src/frc971/crio/.
48Use `./build.sh deploy` to download to a robot.
49
50[Communicating with the cRIO]
51Use netconsole.sh to communicate directly with the cRIO.
52frc971/2013/trunk/src/aos/crio/bin/netconsole.sh
53Use "reboot" from within netconsole.sh will reboot the cRIO. ^C will
54stop it the netconsole.sh command. "version" will tell you the the
55VxWorks and WIND versions and "help" will give you a list of VxWorks
56commands that you can use.