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.

c6A8168 syslink samples error

Hello,

I am using the C6A8168 evm and the ezsdk (with syslink_02_00_00_56). By following the user's guide of syslink software, I have well built the rtos and hlos applications and copied it in the target file system. Nevertheless, when I try to run these samples, I have one error with 'insmod' :

# /opt/syslink/procmgrapp.exe 0 /opt/syslink/frameq_ti81xx_dsp.xe674
(I press Ctrl + Z)
# insmod /opt/syslink/frameqapp.ko
frameqapp: no symbol version for module_layout
insmod: error inserting '/opt/syslink/frameqapp.ko': -1 Invalid module format

Does anyone have an idea ?

JS

  • This error typically means the driver (frameqapp.ko) wasn't rebuilt against the kernel that it's trying to be loaded into.

    Chris

  • Thanks Chris,

    However, I have followed the instructions of the SysLink_02.00.00.56_alpha2_InstallGuide.pdf. So how do you explain that it does not work ? I think that the problem comes from the kernel source files I give to the programm when I build the samples. As expected at page 6 and 7 of the SysLink_02.00.00.56_alpha2_InstallGuide.pdf, I modified Makefile.inc and wrote :

    KDIR := ~/ti-ezsdk/psp/linux-2.6.34-psp04.00.00.07/source

    So normally, it is the right sources, is not it ?

  • Jean,

    Did you rebuild the PSP in that location and use the uImage that is generated by that build? This happens when the Linux uImage used on the target does not match the source that the driver is being built against.

    Regards,
    Mugdha

  • Mugdha,

    I have rebuilt the PSP in this directory (~/ti-ezsdk/psp/linux-2.6.34-psp04.00.00.07/) and I have no more problem when inserting modules on the c6a8168evm. You was right ; I was sure it was the good directory but in fact I had built the kernel and the modules from this directory to an other one...

    I had also problems when executing dsp code (the .xe674 files). The program stopped and I had no option but reseting the c6a8168evm. Now, it is better but sometimes, I have the same problem. I don't understand why. For example, one time, I had :

    # ./procmgrapp.exe 0 /opt/syslink/gatemp_ti81xx_dsp.xe674
        ProcMgrApp sample application
        Entered ProcMgrApp_startup
        ProcMgr_attach status: [0x97d2000]
        After attach: ProcMgr_getState
            state [0x1]
        ProcMgr_load status: [0x3046000]
        After load: ProcMgr_getState
            state [0x3]
        ProcMgrApp_start passed [0x6a85000]

    ...then nothing.

    And most of the time, it works... !! 
    Anyway, firstly, I am just wondering if I had specified the good target and platform. I have understood that all these parameters are specified in the syslink_software/config.bld file but there are some points I do not understand in this file :

    - Is rootDir the path to Code Generation Tools ? In syslink_InstallGuide.pdf, it is /toolchains/ti-tools/. What is ti-tools ? I used this path : ~/ti-ezsdk/cgt6x_7_2_0/.
    - Normally, all the available targets and platforms are in the xdctools_software/packages/ti/ directory. Am I right ? (if not, where are they ?) However, why the platform specified in syslink_software/config.bld is in syslink_software/ti/syslink/samples/rtos/platforms/ti816x/dsp/. I work on the TMS320C6A8168 Integra, the target should be C674. And what for the Platform ? In xdctools_software/packages/ti/, I see two possibilties : evmTI816X and evmC6A8168. Why not using these one ? What are the differences between these two platforms ?

    Thank you for your help,

    JS