Steve, Good suggestions. I will try that at my next opportunity. I do not believe it to be an issue with spacing or delimiter characters, because I have copied the halcmd exactly as it exists in the working .hal file (adding halcmd of course). I have tried fully qualified paths and symlinks and keep getting exactly the same error, so I strongly suspect it isn't the symlinks.
Regards, Eric Am I missing something here? Actually a better question would be "what am I missing here?" The section of code that looks at the config string does no checking of whether there's hardware to support the load-time options you use. You can say config="num_stepgens=102", and you won't get the "Unknown parameter ..." error you quoted. I think that error is printed by the module loader when it can't find the named symbols in the module. Which bitfile you use has no effect on this error, only the driver you load and the parameters you use do. One problem the module loader (sometimes) has is that it doesn't deal with spaces in the config strings very well. It may be separating the num_stepgens=xxx into a separate token (it does look like one after all), then erroring because it doesn't exist. The parport driver was made to accept underscores or spaces to work around this problem (you'd use cfg="0x378_OUT_0x278"). I don't recommend doing the same for this driver - I'd use the existing parameter infrastructure instead. ;) You could try loading the module once with the firmware file specified (but no stepgens), or using bfload to load the bitfile. Unload the module, then load it with only the config="num_stepgens=xx" parameter. It should leave the FPGA alone if you don't give it a firmware name to load. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
