• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 1695 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 example - problem inserting new syslink.ko

Jane Perera78562
Intellectual 350 points

Trying to get the "syslink notify" example to work between the A8 and M3.  I have built the executables for each processor and successfully loaded, but there is a kernel error.  I decided to rebuild the kernel since I am using the prebuilt image.  I did follow the EZSDK guide and did

make linux_clean

make linux

make linux_install

 

Then I copied the uImage to /tftpboot and modified my boot environmental variables

setenv bootfile uImage

The syslink.ko driver is not loaded and the boot script prints out some errors

PRCM Initialization completed
FATAL: Module syslink not found.
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Loca
tion of Mem map bin file]
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.1.1
OsalDrv driver open: /dev/syslinkipc_Osal: No such file or directory
OsalDrv driver close: /dev/syslinkipc_Osal: Bad file descriptor
/dev/syslinkipc_MultiProc: No such file or directory
MultiProc driver close: : Bad file descriptor
SharedRegion driver open: : No such file or directory
SharedRegion driver close: : Bad file descriptor
/dev/syslinkipc_GateMP: No such file or directory
/dev/syslinkipc_MessageQ: No such file or directory
MessageQ driver close: : Bad file descriptor
Notify driver open: /dev/syslinkipc_Notify: No such file or directory
Notify driver close: /dev/syslinkipc_Notify: Bad file descriptor
ProcMgr driver open: /dev/syslinkipc_ProcMgr: No such file or directory
ProcMgr driver close: /dev/syslinkipc_ProcMgr: Bad file descriptor

 

but then completes other parts of the boot process and I can go to the file system.  I try to do "insmod syslink.ko" and get the following error:

root@dm816x-evm:/lib/modules/2.6.37/kernel/drivers/dsp# insmod syslink.ko
syslink: no symbol version for module_layout
insmod: error inserting 'syslink.ko': -1 Invalid module format

Since I already rebuilt the kernel I don't understand the error.....

 

 

  • 0
    TI__Mastermind 18260 points

    Jane Perera78562 said:

    root@dm816x-evm:/lib/modules/2.6.37/kernel/drivers/dsp# insmod syslink.ko
    syslink: no symbol version for module_layout
    insmod: error inserting 'syslink.ko': -1 Invalid module format

    This error means you need to rebuild syslink.ko while pointing the build at your rebuit kernel source code.  Loadable modules (as syslink.ko is) are picky about which kernel they will run with.

    There should be a file name products.mak in the root of your SysLink installation.  It contains 'make' variables that need to be defined for your build.  There are separate variables for each device, so modify the ones pertaining to your selected DEVICE.  The LINUXKERNEL variable is the one that needs to be set to your Linux kernel source location.

    Just wondering, what was your initial kernel error that prompted you to rebuild the kernel?

    Regards,

    - Rob

     

  • 0 in reply to Robert Tivy
    Intellectual 350 points

    Sorry I cannot remember the original kernel error.

    Have now got the syslink example working for 1 processor, either DSP or M3 (VPSS still crashes and more than 1 crashes).  I downloaded a newer version of syslink plus made sure to tear down the graphics plane after boot and re-insert syslink.ko.  I am using the original kernel and syslink.ko that came with the EVM. 

    Thanks for your advice.

  • 0 in reply to Jane Perera78562
    TI__Mastermind 18260 points

    So, are you still needing help?  Not sure from your response.

    If you need help running syslink examples on more than one processor (or whatever) please start a new forum thread.

    Regards,

    - Rob

  • 0 in reply to Robert Tivy
    Intellectual 350 points

    I am working through my TI rep. thanks