• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 462 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

[OMAP L138] insmod: error inserting 'dsplinkk.ko'

Abhishek Ranjan
Prodigy 50 points
Other Parts Discussed in Thread: OMAPL138

Hi !

I was building the OMAP L138 SDK as given in the wiki http://processors.wiki.ti.com/index.php/Building_The_OMAP-L1_SDK

For installing and running the DSP link examples it told to refer to the document  "InstallGuide_Linux_OMAPL138" given in "section 1.5.4 of the <InstallGuide_Linux_OMAPL1xx.pdf for OMAPL137> and <InstallGuide_Linux_OMAPL138.pdf for OMAPL138>located at /home/<useracct>/OMAPL13#_arm_1_##_##_##/DSPLINK_DIR/packages/dsplink/doc". (Although the document is present in "OMAP_L138_arm_1_00_00_08/dsplink_linux_1_65_00_01/dsplink/doc" in my case)

For loading the kernel module dsplinkk.ko, I gave the command :

insmod dsplinkk.ko

But the result was:  insmod: error inserting 'dsplinkk.ko': -1 Invalid module format

How to solve this problem and run the DSP link examples? My host is Fedora 12 (kernel 2.6.31.5-127.fc12.i686)

  • 0
    Genius 4120 points

    Hi,

    This happens when there's a mismatch in the kernel against which DSPLink was built, and the uImage being used. Are you sure you built DSPLink against the same kernel whose uImage is being used on the board?

    Regards,
    Mugdha

  • 0 in reply to MUGDHA ARORA
    Prodigy 50 points

    Hi Mugdha,

    Sorry for the late reply. I had built the DSPLink for the same kernel whose uImage has to be used on the board.

    I have a small question: do we have to boot the board and keep it running for doing "insmod" or can it be done without even connecting the board ? (I use NFS method to run the board)

  • 0 in reply to Abhishek Ranjan
    Genius 4120 points

    Abhishek,

    I'm not sure I correctly understand your question, but I'll try to answer ...

    You have to do insmod on the board itself, i.e. you would have some uart terminal opened (say TeraTerm or HyperTerminal), which is connected from your PC to the board over serial cable. When the board boots, you'll see prints on this terminal. You need to insmod the DSPLink kernel module on the board using this terminal application. The dsplinkk.ko file should be in your nfs mounted file system on the board.

    If you tried to do insmod on your build PC, you would definitely get this problem of mismatch, because you have to insmod on the board.

    Regards,

    Mugdha

     

  • 0 in reply to MUGDHA ARORA
    Intellectual 835 points

    Abhishek,

    If you don't want to connect to the board every time to insmod a module on poweron you can place the insmod command in the Linux starting script for your board, that is placed on your host machine most likely in: <your_nfs_path>/etc/init.d/rcS. It's good to connect to the board for the first boot and see if the module got loaded correctly.

    Regards
    Szymon