I have been setting up sccKit 1.2.2 on the MCPC according to the setup instructions an have run into a couple of issues. First a minor caveat: the instructions ask you to run "rm -rf ..." as root to delete files -- this is obviously very dangerous, and a simple typo can render the system useless. Be careful.
The first part (installing the two tarballs, setting up the config file) went smoothly. The installation of the driver and firmware using install.csh, had some issues. The install script tries to copy the driver kernel module to /lib/modules/.../kernel/drivers/mcedev, but this directory does not exist on a clean system. One needs to manually create this directory before running the script. Next, the script tries to download firmware files to the BMC. This failed with an insufficient space error.
It turns out that the usb memory stick was not mounted (actually, not even visible) on the BMC of the system here. It seems that the front panel USB ports are not working properly on our system. I tried other memory sticks, and nothing showed up in /proc/bus/usb/devices on the BMC. Finally, I opened up the chassis and used the USB port on the main board next to the BMC card -- this worked. After resetting the BMC, the USB drive was mounted. After this, the install script seems to run fine.
After doing the power off MCPC, power on SCC, power on MCPC sequence, the new driver is loaded, and a funny device shows up in the output of lspci (Intel memory controller id c148), so I assume the hardware and driver are working. The instructions then suggest either root or a user can run the sccBmc -i to train the interface. However, by default the device (/dev/crbif0rb0) is only accessible by root -- one needs to run "chmod a+rw /dev/crbif0rb0" to allow users access.
Now, I am having issues with the sccBmc -i command. It just runs and runs, spewing lots of unexpected packet and timeout waiting for read request messages. It keeps increasing "inc-delay" until 60, then says training unsuccessful, and starts again at 0. (Actually, the first time through, the MCPC crashed; I redid all of the setup, including firmware download, and the second run is looping right now). Any ideas what this could be?