cmem driver minor version

Raymond Boswel

Dear TI,

I am running a c6runlib application on angstrom with kernel 2.6.32. The dsp-side library was compiled using the C6Run_0_98_01_01 set of tools and was linked to the rest of the program on the Beagleboard itself. The loadmodules.sh script runs without any problems. When I try to run my program however, I get the message :

CMEM Error: init: minor version mismatch between interface and driver

CMEM Error: needs driver minor version 0x100 or greater.

got minor version 0 (full version 0x3000000)

CMEM_init() failed!

segmentation fault

Could you please advise me on how to solve this problem?

Kind regards,

Raymond Boswel

over 14 years ago

0 Robert Tivy over 14 years ago

TI__Mastermind 18260 points

Raymond Boswel said:

CMEM Error: init: minor version mismatch between interface and driver

CMEM Error: needs driver minor version 0x100 or greater.

got minor version 0 (full version 0x3000000)

You are apparently linking against a CMEM user library from a different Linux Utils release than the one from which the kernel module cmemk.ko was created. You will need to either:
- install the cmemk.ko from the same Linux Utils release as that to which you're linking your user app, or
- point your user app build to the same Linux Utils from which cmemk.ko came.

Regards,

- Rob

0 Rock shi over 13 years ago in reply to Robert Tivy

Prodigy 60 points

Hello Robert Tivy,

I have the same problem. The cmemk.ko is provided by AM/DM37x EVM Ti-Android-Froyo-Dsp SDcard. App is changed from DVSDK-4-02-00-06. Which Linux Utils is needed to pointing my app build to the same of the cmemk.ko?

Thanks

0 Rock shi over 13 years ago in reply to Rock shi

Prodigy 60 points

I have solved this problem,thanks

0 eric eric1 over 9 years ago in reply to Rock shi

Prodigy 70 points

hi Rock,

would you mind to share your experience about how you fit this problem?I met the same issue now and I had no idea about it.

I've tried like this:

1. buid my app and cmemk.ko in the same linux utils (Linux version 2.6.32-38-generic)

2. then I replace cmemk.ko in my devices and run ./loadmodules.sh, in this step, no error occurs

3. then I run my app whick made in the same environment with cmem, but the same error occurs,like this:

by the way,my uImage was made in linux 2.6.37，and my app and cmemk made in 2.6.32? Would it matter?

0 Titusrathinaraj Stalin over 9 years ago in reply to eric eric1

TI__Guru** 116100 points

by the way,my uImage was made in linux 2.6.37，and my app and cmemk made in 2.6.32? Would it matter?

Yes, it may cause the problem.
You need to use the same kernel version which has released for CMEM.

0 eric eric1 over 9 years ago in reply to Titusrathinaraj Stalin

Prodigy 70 points

Thank you very much for your replaying, I upgraded my linux kernel but it didn't work.But I fitted it by replacing my dvsdk version while my cmemk.ko was pre-builded in dvsdk4.00 but my app was builded in dvsdk4.03 by myself. My issue was accused by the mismatched dvsdk version.

0 Titusrathinaraj Stalin over 9 years ago in reply to eric eric1

TI__Guru** 116100 points

Sounds good.
Thanks for the update.

Processors

Processors forum

cmem driver minor version