Pc104: Difference between revisions

From ISRWiki
Jump to navigation Jump to search
mNo edit summary
Line 5: Line 5:
The pc104 CPU board that is attached to our iCub boots from a read-only memory (it uses a [http://debian-live.alioth.debian.org/ Debian Live distribution]).
The pc104 CPU board that is attached to our iCub boots from a read-only memory (it uses a [http://debian-live.alioth.debian.org/ Debian Live distribution]).


After booting, it mounts a part of the hard-disk of icubsrv (the laptop, IP address 10.10.1.51).
After booting, it mounts a part of the hard-disk of icubsrv (the laptop, IP address <code>10.10.1.51</code>).


After that, it runs the scripts that are found in /exports/code-pc104/pc104/hooks.
After that, it runs the scripts that are found in <code>/exports/code-pc104/pc104/hooks</code>.
You can use those scripts for making some configuration permanent on pc104 and/or to run programs.
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.
They set up the yarp namespace, start yarp run, configure the keys for passwordless log-ins, etc.


[[Category:Vislab]]
[[Category:Vislab]]

Revision as of 09:57, 10 August 2009

See pc104/Archive for information about the Ubuntu Server installation and tests that we performed in May 2009, to try 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.