• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 602 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.

Syslink Fatal Error inserting syslink

Joseph Furno
Intellectual 300 points

syslink: disagrees about version of symbol module_layout
FATAL: Error inserting syslink (/lib/modules/2.6.37/kernel/drivers/dsp/syslink.ko): Invalid module format

I have installed the new 5.03 SDK and trying to rebuild the kernel to support POSIX queues.

 Modified kernal configuration using:

$ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm ti8168_evm_defconfig

$ make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm menuconfig

Saves config changes to ti8168_evm_defconfig....
 
Then:
 
  cd ${EZSDK}

 $ make clean

$ make all

$ make install

 

I also tried:

 $ make clean

$ make components

 $ make syslink_clean

 $ make syslink

 $ make linux_clean

 $ make linux

$ make linux_install

Copied kernal uImage to SD Card

I then tried to run with the new kernel, but I encountered an error during boot:

 

  • 0
    TI__Mastermind 20245 points

    Hi,

    If you have rebuilt kernel, you have to build all dependent modules like syslink.ko, vpss.ko etc. You can refer to syslink install guide and video driver userguide on how to build syslink.ko and vpss.ko.

    Regards,

    Hardik Shah

  • 0 in reply to HardikShah
    Intellectual 300 points

    We did a complete recompile using "make clean" , "make all" , make "install" 

    We then scrubbed the SD card and recreated it following the directions

    in the SDG and seem to have gotten past the syslink issue.

    Unfortunately , it appears like it still did not build in the Posix Message Queue support we ere looking for.

    We verified in .config and ti8148_evm_defconfig files that it is turned on but its either not building it in

    or its not really using our new kernel image....  (We have a 814x evm and not 816x evm like prior post)

    Any ideas on this.....