Setting up CMEM and DSPLINK modules

Matt,

I can only offer guesses...

I'm assuming the cmemk.ko and dsplinkk.ko were being loaded through a "loadmodules.sh" script, and that script uses modprobe to find the .ko's.  modprobe looks for .ko files starting in /lib/modules/`uname -r` (uname -r gives the kernel release name).  For example, for my board:
    % uname -r
    3.3.0-rc1+
which means modprobe will look for .ko files starting at:
    /lib/modules/3.3.0-rc1+

Since you mention that you had to update the PSP, I assume that it is of a different "release" than what came with your kit.

What is the output of 'uname -r' when running your new kernel, and do you have a directory named /lib/modules/<output of uname -r>?

Since you updated your kernel, and since kernel modules need to be built by the 'make' system of your running kernel, you will need to also rebuild cmemk.ko and dsplink.ko with the build pointing at your new kernel source tree.  I'm not familiar with the OMAP L138 eXperimenter kit, but usually it will be a complex process to get a "kit" to work with a new kernel, as the kit will have prebuilt stuff that depends on the kit's kernel, and the kit will have been validated with that kernel.

Then again, it could be as simple as your filesystem not having cmemk.ko or dsplinkk.ko at all, but my guess is that you have those files but just not in the right place.

Before going ahead and rebuilding cmemk.ko and dsplinkk.ko, you might want to try the prebuilt ones that worked with your previous settup.  If they're not right for your running kernel then the modprobe will fail and the console will have some message to the effect of "invalid module".

Regards,

- Rob

Otherwise just run the following commands:

host:

make cmem

sudo make cmem_install

make dsplink

sudo make dsplink_install

target:

depmod -a

reboot

(Assuming that you're using nfs fs)

HI, Have you solved the problem yet?I have the same question with you.