• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 1110 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.

DM8148 insmod syslink.ko error

enson Steven
Intellectual 630 points
Other Parts Discussed in Thread: SYSCONFIG

hello,

I rebuilt the kernel ,when I use the prebulid filesystem as the nfs,it come to

VFS: Mounted root (nfs filesystem) on device 0:15.
devtmpfs: mounted
Freeing init memory: 232K
INIT: version 2.86 booting
Please wait: booting...
Starting udev
udevd (67): /proc/67/oom_adj is deprecated, please use /proc/67/oom_score_adj instead.
Root filesystem already rw, not remounting
Caching udev devnodes
ALSA: Restoring mixer settings...
NOT configuring network interfaces: / is an NFS mount
Mon Dec 31 10:37:00 UTC 2012
INIT: Entering runlevel: 5
Loading HDVICP2 Firmware
DM814X prcm_config_app version: 2.0.0.1
Doing PRCM settings...
PRCM for IVHD0 is in Progress, Please wait.....
BW Phy Addr : 0x48180600 Data : 0x00000001
AW Phy Addr : 0x48180600 Data : 0x00000002
Phy Addr : 0x48180c04 Data : 0x00000037
BW Phy Addr : 0x48180620 Data : 0x00070000
AW Phy Addr : 0x48180620 Data : 0x00050002
BW Phy Addr : 0x48180624 Data : 0x00030000
AW Phy Addr : 0x48180624 Data : 0x00010002
Phy Addr : 0x48180600 Data : 0x00000102
BW Phy Addr : 0x48180c10 Data : 0x00000007
AW Phy Addr : 0x48180c10 Data : 0x00000003
Phy Addr : 0x48180c14 Data : 0x00000004
BW Phy Addr : 0x58088000 Data : 0x2d8b6676
AW Phy Addr : 0x58088000 Data : 0xeafffffe
BW Phy Addr : 0x58098000 Data : 0x019af45e
AW Phy Addr : 0x58098000 Data : 0xeafffffe
BW Phy Addr : 0x48180c10 Data : 0x00000003
AW Phy Addr : 0x48180c10 Data : 0x00000000
Phy Addr : 0x48180c14 Data : 0x00000007
PRCM for IVHD0 is Done Successfully
PRCM Initialization completed
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 don't know how to rebuilt the syslink.ko

thanks

enson 

  • 0
    Intellectual 315 points

    Hello,

    You need to compile syslink.ko with the version of Kernel you are trying to insert syslink. Basically error is that your syslink.ko is compiled with some version of kernel which is not same as what version of kernel you have loaded.

    Syslink build method is explained here http://processors.wiki.ti.com/index.php/SysLink_Install_Guide

    Build SysLink Driver and Libraries

    In EZSDK, syslink: ti-ezsdk_dm814x-evm_5_05_02_00/component-sources/syslink_2_20_02_20

    Best Regards,

    Magy

  • 0 in reply to Magy Gashova
    Intellectual 630 points

    Hello Magy, 

    Thank you very much I have rebuild the syslink.ko and it is ok.But I　have a new problem,see the kernel log following

    PRCM Initialization completed
    SysLink version : 2.20.02.20
    SysLink module created on Date:Mar 20 2013 Time:14:48:52
    PM: Adding info for No Bus:syslinkipc_Osal
    PM: Adding info for No Bus:syslinkipc_Ipc
    PM: Adding info for No Bus:syslinkipc_ProcMgr
    PM: Adding info for No Bus:syslinkipc_Notify
    PM: Adding info for No Bus:syslinkipc_MultiProc
    PM: Adding info for No Bus:syslinkipc_NameServer
    PM: Adding info for No Bus:syslinkipc_SharedRegion
    PM: Adding info for No Bus:syslinkipc_HeapBufMP
    PM: Adding info for No Bus:syslinkipc_HeapMemMP
    PM: Adding info for No Bus:syslinkipc_ListMP
    PM: Adding info for No Bus:syslinkipc_GateMP
    PM: Adding info for No Bus:syslinkipc_MessageQ
    PM: Adding info for No Bus:syslinkipc_SyslinkMemMgr
    PM: Adding info for No Bus:syslinkipc_ClientNotifyMgr
    PM: Adding info for No Bus:syslinkipc_FrameQBufMgr
    PM: Adding info for No Bus:syslinkipc_FrameQ
    PM: Adding info for No Bus:syslinkipc_RingIO
    PM: Adding info for No Bus:syslinkipc_RingIOShm
    FIRMWARE: I2cInit will be done by M3
    FIRMWARE: Memory map bin file not passed
    Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
    ===Mandatory arguments===
    <Processor Id> 0: DSP, 1: Video-M3, 2: Vpss-M3
    <Location of Firmware> firmware binary file
    <start|stop> to start/stop the firmware
    ===Optional arguments===
    -mmap input memory map bin file name
    -i2c 0: i2c init not done by M3, 1(default): i2c init done by M3
    FIRMWARE: isI2cInitRequiredOnM3: 1
    FIRMWARE: Default memory configuration is used
    Firmware Loader debugging not configured
    Default FL_DEBUG: warning
    Allowed FL_DEBUG levels: error, warning, info, debug, log
    MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.2.1
    FIRMWARE: 1 start Successful
    Loading HDVPSS Firmware
    FIRMWARE: I2cInit will be done by M3
    FIRMWARE: Memory map bin file not passed
    Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
    ===Mandatory arguments===
    <Processor Id> 0: DSP, 1: Video-M3, 2: Vpss-M3
    <Location of Firmware> firmware binary file
    <start|stop> to start/stop the firmware
    ===Optional arguments===
    -mmap input memory map bin file name
    -i2c 0: i2c init not done by M3, 1(default): i2c init done by M3
    FIRMWARE: isI2cInitRequiredOnM3: 1
    FIRMWARE: Default memory configuration is used
    Firmware Loader debugging not configured
    Default FL_DEBUG: warning
    Allowed FL_DEBUG levels: error, warning, info, debug, log
    MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.2.1
    FIRMWARE: 2 start Successful
    VPSS_FVID2: M3 firmware version 0x1000145 is newer,driver may not work properly.
    PM: Adding info for No Bus:fb0
    PM: Adding info for No Bus:fb1
    PM: Adding info for No Bus:fb2
    Configuring fb0 to LCD
    HDMI W1 rev 4.0
    HDMI CEC Spec version 1.2
    PM: Adding info for No Bus:TI81XX_HDMI
    hdmi: Enter HDMI_W1_StopVideoFrame()
    hdmi: *** Set PHY power mode to 1
    hdmi: *** Set PHY power mode to 2
    I2C No Ack

    HDMI failed to read E-EDID
    hdmi: Enter HDMI_W1_GlobalInitVars()
    hdmi: Enter HDMI_Core_GlobalInitVars()
    hdmi: Enter HDMI_W1_ConfigVideoResolutionTiming()
    hdmi: Enter HDMI_W1_ConfigVideoInterface()
    hdmi: Enter DSS_HDMI_CORE_SW_RESET_ASSERT ()
    hdmi: Enter DSS_HDMI_CORE_POWER_DOWN_DISABLE()
    hdmi: Enter DSS_HDMI_CORE_SW_RESET_RELEASE()
    hdmi: Enter HDMI_W1_StartVideoFrame ()
    hdmi: Irqenable 60000011
    hdmi: 40 hpd
    hdmi: -------------DEBUG-------------------
    hdmi: 1 hdmi_wp_irqstatus
    hdmi: 1 hdmi_core_intr_state
    hdmi: 40 hdmi_core_intr1
    hdmi: 3 hdmi_core_intr2
    hdmi: 9 hdmi_core_intr3
    hdmi: 83 hdmi_core_sys_sys_stat
    hdmi: -------------DEBUG-------------------
    hdmi: first hpd
    PM: Adding info for No Bus:tlc59108-bl
    Starting system message bus: dbus.
    Starting Dropbear SSH server: NET: Registered protocol family 10
    dropbear.
    Starting telnet daemon.
    Starting network benchmark server: netserver.
    Starting syslogd/klogd: done
    Starting thttpd.
    Starting PVR
    PVR: PVRCore_Init
    PM: Adding info for platform:pvrsrvkm
    PVR: PVRSRVDriverProbe(pDevice=bf21d140)
    PVR: EnableSystemClocks: Enabling System Clocks
    PVR: GPTIMER11 clock is 20MHz
    PVR: OSUnMapPhysToLin: unmapping 4 bytes from fa048054
    PVR: OSUnMapPhysToLin: unmapping 4 bytes from fa048038
    PVR: PVRCore_Init: major device 250
    PM: Adding info for No Bus:pvrsrvkm
    PM: Adding info for No Bus:bccat0
    /dev/mem opened.
    Memory mapped at address 0x4027e000.
    Read at address 0x48180F04 (0x4027ef04): 0x00000001
    Write at address 0x48180F04 (0x4027ef04): 0x00000000, readback 0x00000000
    /dev/mem opened.
    Memory mapped at address 0x40284000.
    Read at address 0x48180900 (0x40284900): 0x00000102
    Write at address 0x48180900 (0x40284900): 0x00000002, readback 0x00000002
    /dev/mem opened.
    Memory mapped at address 0x40314000.
    Read at address 0x48180920 (0x40314920): 0x00040002
    Write at address 0x48180920 (0x40314920): 0x00000002, readback 0x00000002
    PVR: Installing MISR with cookie bf21e81c
    PVR: Installing device LISR SGX ISR on IRQ 37 with cookie ca077f00
    PVR: OSUnMapPhysToLin: unmapping 65536 bytes from d5ba0000
    PVR_K:(Warning): SysFinalise: Version string: SGX revision = 1.2.5 [583, usr/local/ezsdk02/component-sources/graphics-sdk_4.04.00.02/GFX_Linux_KM/services4/system/ti81xx/sysconfig.c]
    PVR_K: (FAIL) SGXInit: Mismatch in client-side and KM driver build options; extra options present in KM: (0x1). Please check sgx_options.h
    PVR_K:(Error): PVRSRVFinaliseSystem: Failed PVRSRVDevInitCompatCheck call (device index: 0) [422, usr/local/ezsdk02/component-sources/graphics-sdk_4.04.00.02/GFX_Linux_KM/services4/srvkm/common/pvrsrv.c]
    PVR_K:(Error): BridgedDispatchKM: Initialisation failed. Driver unusable. [3785, usr/local/ezsdk02/component-sources/graphics-sdk_4.04.00.02/GFX_Linux_KM/services4/srvkm/bridged/bridged_pvr_bridge.c]
    Calibrating touchscreen (first time only)ts_open: No such file or directory
    .
    Starting Matrix GUI application.

    _____ _____ _ _
    | _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_
    | | _| .'| . | . | | __| _| . | | | -_| _| _|
    |__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|
    |___| |___|

    Arago Project http://arago-project.org dm814x-evm ttyO0

    Arago 2011.09 dm814x-evm ttyO0

    dm814x-evm login: eth0: no IPv6 routers present
    root
    root@dm814x-evm:~#

    ....................

    FIRMWARE: Memory map bin file not passed 

    what should I do?

    Best Regards,

    Enson

  • 0 in reply to enson Steven
    TI__Guru* 80190 points

    Hello,

    Could you posting the bootargs?

    enson Steven said:
    FIRMWARE: Memory map bin file not passed 

        The message "Memory map bin file not passed" is just the status message.

        As you see the message "Default memory configuration is used" in the subsequent lines.

        User can pass different memory configuration file, if not it picks the default memory configuration file.

        You can see more details on this and on firmware loader at link "http://processors.wiki.ti.com/index.php/EZSDK_Memory_Map"

    Best Regards,

    Margarita

  • 0 in reply to Margarita Gashova
    Intellectual 630 points

    Hi,

    The bootargs I set is

    'console=ttyO0,115200n8 notifyk.vpssm3_sva=0xBF900000 root=/dev/nfs nfsroot=192.168.1.213:/home/enson/targetfs/,nolock rw mem=248M ip=dhcp earlyprintk debug'

    I have read the memory map guide I think may is the load-hd-firmware.sh have something wrong.

    firmware_loader $HDVICP2_ID /usr/share/ti/ti-media-controller-utils/dm814x_hdvicp.xem3 start

    I think it lose the bin file name behond the "start" it should be :

    firmware_loader $HDVICP2_ID /usr/share/ti/ti-media-controller-utils/dm814x_hdvicp.xem3 start <filename>

    thanks,

    Enson