You probably need to use the 'loadusr -Wn name command...' form of
loadusr. For instance, if you run the command "python
/path/to/passthrough.py" to start your component, but it creates a
component named "passthrough", then your hal line would be:
loadusr -Wn passthrough python /path/to/passthrough.py
When loading a userspace component, 'halcmd -W' waits for a component
with a name that is the same as the first word of the command. In many
cases, this is appropriate (for example, the program called
'hal_manualtoolchange' creates a component named
'hal_manualtoolchange'). In other cases it's not (for instance when
your component has a name like "passthrough" but the first word of the
command is something else like '/usr/bin/example'), and you'll get the
'waiting for component' message forever.
Incidentally, if you really did replace the file /usr/bin/test with your
own python script, you have replaced an important standard shell command
and it's likely that as a result your whole system will behave oddly.
You can probably put back the real /usr/bin/test with this command in
the terminal:
sudo apt-get install --reinstall coreutils
Jeff
------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
