This was working fine for me last afternoon but I'm getting this error since. My output for running the pingpong app is
./rccerun -nue 2 -f hosts/rc.hosts apps/PINGPONG/pingpong
c 05:33:40 [FAILURE] rck00 Exited with error code 255
 05:33:40 [FAILURE] rck01 Exited with error code 255
pssh -h PSSH_HOST_FILE.12356 -t -1 -P -p 2 /home/keith_chapman/svn/apps/PINGPONG/pingpong 2 1.0 00 01 < /dev/null
 05:34:26 [FAILURE] rck00 Exited with error code 255
 05:34:26 [FAILURE] rck01 Exited with error code 255I'm trying this on marc010 in the SCC DC.
This usually results when the certificate is not working. Did you look at /etc/ssh/ssh_config?
Do you see Rock Creek information at the end of that file?
The file How to Set Up Your MCPC in the sub-community Your MCPC has some "Are-You-Alive" tests at the end that may give a clue.
Can you ping cores? ssh to a core ... using both its IP address and hostname. Sometimes when the system starts to act strange a retraining helps.
Yes I do see Rock Creek information in /etc/ssh/ssh_config. Seems like rocky is not alive cause it does not respond to pings or ssh by name or IP. Should I file a bug for this.
Sometimes retraining and reloading Linux is what is needed. Which you can do.
If that doesn't work, then the Rockly Lake should be power cycled and that requires root privilege and so if you file under Marc Administration Needed someone will do it. ANd they'll proabably do it right away.
You can retrain witht thecommand
and reload Linux on the cores with
or you can vnc into marc010 and use the sccGui.
You should put the sccKit command in your path if you haven't already. Please check out the SCC Programmers Guide.
sccBoot -l fails with,
INFO: Welcome to sccBoot 1.2.3 (build date Jun 29 2010 - 15:22:14)...
INFO: Starting to boot Linux: All cores!
INFO: Creating .mt file "/tmp/sccKit_keith_chapman/linux.mt"...
INFO: Nothing to copy as /opt/sccKit/1.2.3/resources/linux.obj and /tmp/sccKit_keith_chapman/linux.obj don't differ...
INFO: Merging objects with sccMerge:
INFO: -> sccMerge -broadcast -m 8 -n 12 -noimage linux.mt
INFO: Pulling resets and enabling L2 caches: All cores!
ERROR: Timeout while waiting for Read request answer (CMD=0x7) with TID 0! Cancelling request...
In the meantime I filed a bug.
So, to add, you can get an error code of 255, when one of your cores is unreachable. This can happen if they are physically not booted, or when the communication channels to them are not open.
In my example, I was getting error code 255 when I was trying to access the CRBs for some cores, and I had this line commented out (for PC-debug):
InitAPI(1); /* in SCC_API.h/c */
This function basically does all the heavy-lifting work of setting up communication structure, so that to you read or set configuration registers, or even mmap() 'em.
Hopefully this helps.
Thanks, I'll add that to the list of error code explanations.
I had time ago the same type like described here "error code 255" when tried to run any standard sample application included in iRCCE library. At the same time standard sample RCCE applications were worked correctly. (MARC014). (It was just before I posted bug 217). All the Best. Andrew