The code 'fw_setenv maxcpus' worked for me if I remember correctly. Using the command: -
on the command line previously showed just processor 0, after running it showed processor 0 and processor 1, so I had both cpu's running. Do not expect processor 1 and processor 2. Unless that is things have changed with later revisions of Pluto hardware as numbers start with 0
On the frequency error using 'fw_setenv xo_correction' again I am making assumptions of how I read it all, that the normal clock frequency was 40000000, so if that is what you wanted then you do not put any number in there and just use fw_setenv xo_correction
fw_printenv prints all the system variables going.
The way I check this is as follows
from the pluto command prompt I use fw_printenv | grep correction
If I get no response then it is running at 40000000 but if I set it to be 39999900 then I get a response.
So for example: -
or removing the correction.
Perhaps someone with more knowledge can confirm what I am saying, I am happy to use this on my Pluto, but asking someone else with their own is a different matter. Caveatt emptor!