This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM365 "Invalid module format" problem

hi, everyone:

         I'm using DM365 BETA_board to working on 720P MPEG4 decode+display, as the BETA-board have the earliest kernel and system image, which haven't the demo I want , so, I update the flash_image system, but got an problem when excute "./loadmodules_hd.sh" like:

irqk: disagrees about version of symbol struct_module
insmod: error inserting 'cmemk.ko': -1 Invalid module format
insmod: error inserting 'irqk.ko': -1 Invalid module format
edmak: disagrees about version of symbol struct_module
dm365mmap: disagrees about version of symbol struct_module
insmod: error inserting 'edmak.ko': -1 Invalid module format
insmod: error inserting 'dm365mmap.ko': -1 Invalid module format

      someone knows this problem? By the way,  I use TFTP to download the uImage I maked which was the newest  "linux-2.6.18_pro500" and I haven't overwrite the board kernel, so, any suggest will be appreciate!

  • This normally means that there is software incompatibility between your linux kernel and your file-system.  Are you using both from the same software release (e.g. kernel via TFTP and file-system via NFS) or are you still using the older file-system?

     

  • I overwrite the file-system use "dm365_flash_image_2_10_01_18.tar" which I thank was the newest and haven't overwrite the kernel, so I use TFTP to downloard new kernel "linux-2.6.18_pro500" I maked, Is that any problem? or should I overwrite the kernel on the board? thanks

  • no need to overwrite kernel on board; however, not sure I trust the dm365_flash_image_2_10_01_18.tar; I normally follow the Getting Started Guide and use the file system included with the DVSDK install.  I can tell there are differences between the one in the tar file and the one installed per GSG. 

  • Juan,

        I download the software from  http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_2_10/latest/index_FDS.html,  you can see these just for DM365, and I overwrite the file-system use  "dm365_flash_image_2_10_01_18.tar" and use the new kernel build from "linux-2.6.18_pro500", I think all these would be right, but got an problem like that, so, how could I do next? rebuild cmemc.ko or overwrite the kernel? 

  • Are you using the file system located in /opt/mv_pro_5.0/montavista/pro/devkit/arm/v5t_le/target (see http://wiki.davincidsp.com/index.php/GSG:_DM365_DVEVM_Software_Setup  for details)?

    Also, no need to copy cmemk.ko; if you follow GSG and do 'make install' (setp 4 in Rebuilding the DVSDK Software for the Target), this will automatically copy demo files along with cmemk.ko from DVSDK tree to your NFS target file-system.

    No need to overwrite kernel in flash, simply configure your board to load kernel via TFTP and file-system via NFS, and you should be able to run these components off your host Linux station.

  • Eric,

    I got same problem. After rebuild DVSDK, the problem was solved.

     Your DVSDK package on your file system need to match with the kernel which you are running.  You'd better to run a NFS file system , and rebuild your DVSDK package under ../dvsdk_2_10_00_xx .

    Try run

    make clean,

     make,

     make install. 

    and see if this helps for you.

    Tong

  • I have same problem as that described by Eric, although I followed the online GSG and so am using the DVSDK downloaded from the TI site, and the kernel from the LSP DVD supplied with the EVM.

    I'm completely new to linux, so I don't have a good grasp of some of the explanations in the previous posts. However, I see that the DVSDK version I've used is 02_10_01_18 whereas the kernel is version 02_10_00_08. Is this the cause of the problem? Do I need to match these versions?

    Thanks

    aubrey

  • You should have the kernel (a.k.a. LSP/PSP) and DVSDK versions that are properly associated with each other, if they do not you can run into issues when you try to run the demos, starting with the failure to insert cmemk.ko.

    For DVSDK 2.10.01.18 you should be running LSP 2.10.00.14, both of these can be found here.

    The one piece I don't believe you need to change is the MVL 5.0 system tools installer, this contains the MVL build tools which should be constant (and happen to be the largest download).

  • Thanks Bernie! After using the suggested version of LSP and recompiling it (and the DVSDK, though I didn't change the MVL per your advice) the modules loaded perfectly and the demos work.

    aubrey

  • Make sure you are using the right .ko files.  The ones in "dvsdk/kernel libraries" had incompatibility issue.    Try this path instead:

     

    /home/<user account>/dvsdk_2_10_01_18/dm365_codecs_01_00_06/packages/ti/sdo/codecs/h264enc/apps/client/build/arm926

     

  • Thanks, llavacen, for this hint.I am running into the same problems as Eric Hou ans some other guys. It seems to me, that the "dm365_flash_image_2_10_01_18.tar" does not fit to the Linux kernel and sources, that are shipped together with the package on

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_2_10/latest/index_FDS.html

    But unfortunately i am so new to that stuff, that I dont know what you mean to "try" the path you mentioned in your posting:

    Shall I modify the Rules.make in dvsdk## in the line "# Where the Codec Engine package is installed" to "dm365_codecs_01_00_06"?

    Or shall I start the make in the mentioned path? With which parameters?

    Or does that mean to copy those *.ko files to dvsdk##/kernel_libraries?

    Or ... ?

    What is the favorite method?

    Thanks and best regards

    Ulrich

     

  • Ulrich:

         Just modify the Rules.make as the userguird tell you, rebuilt the kernel and the code under dvsdk and using the new kernel, copy the new built *.ko and decode/encode/…… instand of files already in the board, and everything will be ok 

  • what I mean is go to the directory where you installed dvsdk, then from there, change directory with the following command:

    cd dm365_codecs_01_00_06/packages/ti/sdo/codecs/h264enc/apps/client/build/arm926

    This will enable you to run the demo but I think you wont be able to run the encoder or decoder in it.   At least you will get to play with it before that point and learn a few things, but the hard way.   Rebuilding the dvsdk seems mandatory and will definitily solve alot of problems your having and going to have.

  • Eric Hou said:

    Ulrich:

         Just modify the Rules.make as the userguird tell you, rebuilt the kernel and the code under dvsdk and using the new kernel, copy the new built *.ko and decode/encode/…… instand of files already in the board, and everything will be ok 

      if you do your things right, the .ko files will be installed in your file system automaticaly when you do a make install

  • Thanks to all! it is running now. I also had to add  "video=davincifb:rotation=90" to the bootargs. Now I can see the demo.

    Best regards

    Ulrich