Pc104: Difference between revisions
(add link to Debian Live distro) |
m (minor rewrite) |
||
| Line 1: | Line 1: | ||
''See [[pc104/Archive]] for information on the Ubuntu Server installation and tests that we performed to get rid of the laptop dependency. There are a couple of unresolved issues with that method (dragonfly cameras and Canbus), therefore for | ''See [[pc104/Archive]] for information on the Ubuntu Server installation and tests that we performed to try in May 2009 to get rid of the laptop dependency. There are still a couple of unresolved issues with that method (dragonfly cameras and Canbus), therefore for the time being we went back to the original setup, explained below.'' | ||
== pc104, the iCub's CPU == | == pc104, the iCub's CPU == | ||
Revision as of 19:01, 26 May 2009
See pc104/Archive for information on the Ubuntu Server installation and tests that we performed to try in May 2009 to get rid of the laptop dependency. There are still a couple of unresolved issues with that method (dragonfly cameras and Canbus), therefore for the time being we went back to the original setup, explained below.
pc104, the iCub's CPU
The pc104 CPU board that is attached to our iCub boots from a read-only memory (it uses a Debian Live distribution).
After booting, it mounts a part of the hard-disk of icubsrv (the laptop, IP address 10.10.1.51).
After that, it runs the scripts that are found in /exports/code-pc104/pc104/hooks. You can use those scripts for making some configuration permanent on pc104 and/or to run programs. They set up the yarp namespace, start yarp run, configure the keys for passwordless log-ins, etc.