syslink sample error on the OMAPL138-LCDK

rose duan

Other Parts Discussed in Thread: OMAP-L138

Hi,

I have a OMAPL138-LCDK,and I'm working with syslink-examples to test the correspondence between core ARM and DSP.I got error as follow:

root@omapl138-lcdk:/ti/syslink-examples/OMAPL1XX/messageq# insmod /lib/modules/3
.1.10/kernel/drivers/dsp/syslink.ko TRACE=1 TRACEFAILURE=1
SysLink version : 2.10.03.20
SysLink module created on Date:May 11 2012 Time:10:46:29
Trace enabled
Trace SetFailureReason enabled
root@omapl138-lcdk:/ti/syslink-examples/OMAPL1XX/messageq# ls
messageq_omapl1xx_dsp.xe674 run_messageqapp_release.sh
messageqapp_debug            slaveloader_debug
messageqapp_release          slaveloader_release
run_messageqapp_debug.sh
root@omapl138-lcdk:/ti/syslink-examples/OMAPL1XX/messageq# ./slaveloader_release
1 DSP ./messageq_omapl1xx_dsp.xe674
Usage:
slaveloader --help
slaveloader list [map]
slaveloader <startup|load|all> <core name> <file path> [map file] [--args <core]
slaveloader <shutdown|unload> <core name> [map file]
slaveloader <powerup|powerdown|start|stop> <core name>

Supported core names:
- DSP

Note: [File path] argument is only required when first argument is 'startup', ''
Note: 'list' prints the state of all slave cores
Note: 'list map' also prints the memory map tables
root@omapl138-lcdk:/ti/syslink-examples/OMAPL1XX/messageq# ./slaveloader_release
startup DSP ./messageq_omapl1xx_dsp.xe674
-sh: ./slaveloader_releasestartup: not found
root@omapl138-lcdk:/ti/syslink-examples/OMAPL1XX/messageq# ./slaveloader_release
startup DSP ./messageq_omapl1xx_dsp.xe674
Attached to slave procId 0.
Loading procId 0.
------------[ cut here ]------------
WARNING: at arch/arm/mm/ioremap.c:207 __arm_ioremap_pfn_caller+0x15c/0x16c()
Modules linked in: syslink ipv6
[<c000d364>] (unwind_backtrace+0x0/0xf0) from [<c001ba74>] (warn_slowpath_commo)
[<c001ba74>] (warn_slowpath_common+0x4c/0x64) from [<c001baa8>] (warn_slowpath_)
[<c001baa8>] (warn_slowpath_null+0x1c/0x24) from [<c000f320>] (__arm_ioremap_pf)
[<c000f320>] (__arm_ioremap_pfn_caller+0x15c/0x16c) from [<c000f3a0>] (__arm_io)
[<c000f3a0>] (__arm_ioremap_caller+0x58/0x60) from [<bf07a528>] (MemoryOS_map+0)
[<bf07a528>] (MemoryOS_map+0x148/0x3e0 [syslink]) from [<bf0543c8>] (_ProcMgr_m)
[<bf0543c8>] (_ProcMgr_map+0x3b0/0x570 [syslink]) from [<bf0603f4>] (ElfLoaderT)
[<bf0603f4>] (ElfLoaderTrgWrite_copy+0xf0/0x3cc [syslink]) from [<bf065570>] (D)
[<bf065570>] (DLIF_copy+0x8/0x14 [syslink]) from [<bf063ab8>] (DLOAD_load+0x984)
[<bf063ab8>] (DLOAD_load+0x984/0xb50 [syslink]) from [<bf05f934>] (ElfLoader_lo)
[<bf05f934>] (ElfLoader_load+0x110/0x3e4 [syslink]) from [<bf04fbf8>] (Loader_l)
[<bf04fbf8>] (Loader_load+0x98/0x174 [syslink]) from [<bf05236c>] (ProcMgr_load)
[<bf05236c>] (ProcMgr_load+0x104/0x360 [syslink]) from [<bf057354>] (ProcMgrDrv)
[<bf057354>] (ProcMgrDrv_ioctl+0xd38/0x1c28 [syslink]) from [<c00921e8>] (do_vf)
[<c00921e8>] (do_vfs_ioctl+0x7c/0x598) from [<c009273c>] (sys_ioctl+0x38/0x60)
[<c009273c>] (sys_ioctl+0x38/0x60) from [<c0009320>] (ret_fast_syscall+0x0/0x2c)
---[ end trace 0905d4cd37d5cbd6 ]---
*** MemoryOS_map: Failed to map to host address space!
        Error [0x897d2003] at Line no: 517 in file /home/a0883717/ti/syslink_2_c
*** _ProcMgr_map: Memory_map failed
        Error [0xfffffff1] at Line no: 2407 in file /home/a0883717/ti/syslink_2c
Assertion at Line no: 394 in /home/a0883717/ti/syslink_2_10_03_20/packages/ti/sd
------------[ cut here ]------------
WARNING: at arch/arm/mm/ioremap.c:207 __arm_ioremap_pfn_caller+0x15c/0x16c()
Modules linked in: syslink ipv6
[<c000d364>] (unwind_backtrace+0x0/0xf0) from [<c001ba74>] (warn_slowpath_commo)
[<c001ba74>] (warn_slowpath_common+0x4c/0x64) from [<c001baa8>] (warn_slowpath_)
[<c001baa8>] (warn_slowpath_null+0x1c/0x24) from [<c000f320>] (__arm_ioremap_pf)
[<c000f320>] (__arm_ioremap_pfn_caller+0x15c/0x16c) from [<c000f3a0>] (__arm_io)
[<c000f3a0>] (__arm_ioremap_caller+0x58/0x60) from [<bf07a528>] (MemoryOS_map+0)
[<bf07a528>] (MemoryOS_map+0x148/0x3e0 [syslink]) from [<bf0543c8>] (_ProcMgr_m)
[<bf0543c8>] (_ProcMgr_map+0x3b0/0x570 [syslink]) from [<bf0603f4>] (ElfLoaderT)
[<bf0603f4>] (ElfLoaderTrgWrite_copy+0xf0/0x3cc [syslink]) from [<bf065570>] (D)
[<bf065570>] (DLIF_copy+0x8/0x14 [syslink]) from [<bf063ab8>] (DLOAD_load+0x984)
[<bf063ab8>] (DLOAD_load+0x984/0xb50 [syslink]) from [<bf05f934>] (ElfLoader_lo)
[<bf05f934>] (ElfLoader_load+0x110/0x3e4 [syslink]) from [<bf04fbf8>] (Loader_l)
[<bf04fbf8>] (Loader_load+0x98/0x174 [syslink]) from [<bf05236c>] (ProcMgr_load)
[<bf05236c>] (ProcMgr_load+0x104/0x360 [syslink]) from [<bf057354>] (ProcMgrDrv)
[<bf057354>] (ProcMgrDrv_ioctl+0xd38/0x1c28 [syslink]) from [<c00921e8>] (do_vf)
[<c00921e8>] (do_vfs_ioctl+0x7c/0x598) from [<c009273c>] (sys_ioctl+0x38/0x60)
[<c009273c>] (sys_ioctl+0x38/0x60) from [<c0009320>] (ret_fast_syscall+0x0/0x2c)
---[ end trace 0905d4cd37d5cbd7 ]---
*** MemoryOS_map: Failed to map to host address space!
        Error [0x897d2003] at Line no: 517 in file /home/a0883717/ti/syslink_2_c
*** _ProcMgr_map: Memory_map failed
        Error [0xfffffff1] at Line no: 2407 in file /home/a0883717/ti/syslink_2c
Unable to handle kernel paging request at virtual address ffffffff
pgd = c7188000
[ffffffff] *pgd=c7ffe831, *pte=00000000, *ppte=00000000
Internal error: Oops: 817 [#1] PREEMPT
Modules linked in: syslink ipv6
CPU: 0    Tainted: G        W    (3.1.10 #7)
PC is at memset+0xb8/0xc0
LR is at ElfLoaderTrgWrite_copy+0x13c/0x3cc [syslink]
pc : [<c0140f58>]    lr : [<bf060440>]    psr: 20000013
sp : c7b83d08 ip : 00000001 fp : c8ef6000
r10: ffffffff r9 : 00000008 r8 : 06a85000
r7 : 00009a28 r6 : bf140e60 r5 : c8ebf000 r4 : c7b83d90
r3 : 00000003 r2 : 00000000 r1 : 00009a24 r0 : ffffffff
Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
Control: 0005317f Table: c7188000 DAC: 00000015
Process slaveloader_rel (pid: 1563, stack limit = 0xc7b82270)
Stack: (0xc7b83d08 to 0xc7b84000)
3d00:                   c3d27e40 03046000 00027e40 00000001 ffffffff bf06e90c
3d20: c3d27e40 c3d27e40 00000008 00009a28 c8f20000 bf140e60 00000078 c3d27e40
3d40: c8ee7000 00000002 c8f0c030 00000002 c8ef4000 00000008 c7b83d90 bf065570
3d60: 00000008 bf063ab8 ffffffff bf079ff0 00000001 c8f0c150 00000000 c8ee7000
3d80: c8ee701c c8ef4000 00000001 c8ef4000 c8ef4000 c8f10000 ffffffff 00000001
3da0: 00027e80 00000000 00000002 00000008 c8ef6000 c8ef6000 00000000 c8ebf000
3dc0: 00000000 bf140e60 03046000 00000000 00000000 c8ebb000 c7b83ef0 bf05f934
3de0: c8ef2000 00000000 00000000 00000000 00000001 c8ef4000 fea00000 c8ebb000
3e00: 00000000 00000000 bf140e60 c8ef2000 c7b83ef0 00000000 00000000 bf04fbf8
3e20: 00000000 c7b83ef0 00000000 00000000 c8ec5000 00000000 00000000 bf10f624
3e40: bf140e60 c89fd000 c7b83ef0 bf05236c 00000000 c7b83ef0 00000000 00000000
3e60: 0000001e c8ef2000 0000001e bea7ab70 bf140e60 c7b82000 00000000 c8ef2000
3e80: c7b82000 c7b83ed4 00000000 bf057354 00000000 c7b83ef0 c0175734 c78f336c
3ea0: c78f3000 0000000a c7934011 c7b82000 c0177d8c c7b82000 a0000013 c0173700
3ec0: 00000001 c0173ed4 c78f3000 c78f336c 00000000 097d2000 c8ec5000 bea7ae9f
3ee0: 0000001e 00000000 00000000 00000000 00000000 c70b3e70 00000002 c00b59d4
3f00: c7b93200 bea7ab70 bea7ab70 00000007 c65b43f8 c7b82000 00000000 c00921e8
3f20: 00000000 00000001 c0161978 00000000 00000000 00000000 c7b83f6c c7905108
3f40: 00000012 00000000 c70b3e38 00000002 c7b82000 00000000 bea7a974 c0082710
3f60: c7905100 00000012 c7b93200 bea7ab70 c020e0a2 00000007 c00094a4 00000000
3f80: 00000000 c009273c 4f84883b 00000001 00000012 00000000 0008148c 00054200
3fa0: 00000036 c0009320 00000000 0008148c 00000007 c020e0a2 bea7ab70 00000001
3fc0: 00000000 0008148c 00054200 00000036 bea7ab70 c020e0a2 00000000 00000000
3fe0: 000817ac bea7ab38 000373e0 402530ac 60000010 00000007 fffffcff ffffffff
Code: ba00001d e3530002 b4c02001 d4c02001 (e4c02001)
---[ end trace 0905d4cd37d5cbd8 ]---

Everything with the OMAPL138-LCDK using are as the SD card,including u-boot,uImage,syslink.ko.Why I can't get working with syslink.

Finally,I can't revise the boot arguments for the target as the Syslink install guide.And will dose it cause the error? Hope get some advice,thanks!

Best regards

Rose

over 11 years ago

0 Titusrathinaraj Stalin over 11 years ago

TI__Guru** 116100 points

Hi Rose Duan,

Please ensure that your are following the TI wiki link for running SYSLINK examples(messageQ)

http://processors.wiki.ti.com/index.php/SysLink_Install_Guide_-_2.00_and_2.10#Running_Sample_Applications

Some useful TI wiki links related to SYSLINK

http://processors.wiki.ti.com/index.php/SysLink_Notify_Drivers_and_Transports

http://processors.wiki.ti.com/index.php/SysLink_UserGuide#MessageQ

http://processors.wiki.ti.com/index.php/SysLink_Install_Guide#Installing_Examples

0 Robert W over 11 years ago in reply to Titusrathinaraj Stalin

Mastermind 7100 points

Hello,

I have the same error as the original post. I do not find a solution after I check the link above. I would like to get a confirmation whether MessageQ and other example projects can be successfully run without errors.

Thanks,

0 Robert W over 11 years ago in reply to Robert W

Mastermind 7100 points

Hi,

I find that L138 LCDK has 128 MB DRAM. After reading below on line:

Configuring Kernel Parameters

SysLink requires a few specific arguments to be passed to the Linux kernel during boot up. To run the examples, 3MB of memory is needed by SysLink for communication between GPP and slave(s), and for slave(s) external memory usage to place its code/data sections. This must be reserved by specifying 3MB less of available memory for Linux kernel usage.

For example, with available memory of 256M, memory required for shared regions/other utils is 5M and SysLink is 3M leaving only 248M for the Linux kernel.

bootargs console=ttyS2,115200n8 root=/dev/nfs nfsroot=HOST:nfs_root,nolock rw mem=248M ip=dhcp

I set the boot args as:

setenv bootargs console=ttyS2,115200n8 rw noinitrd root=/dev/nfs nfsroot=192.168.0.103:/home/lcdkl138/arm9_FS,nolock rw mem=110M ip=dhcp earlyprintk rootdelay=2,rsize=1024,wsize=1024 ip=dhcp

Is it right? I would like to make sure the memory setting is correct first.

Thanks,

0 Robert W over 11 years ago in reply to Robert W

Mastermind 7100 points

Another thing seems strange to me. The following link gives the example execute projects path: (/ti/syslink-examples/<device>)

http://processors.wiki.ti.com/index.php/SysLink_Install_Guide#Installing_Examples

Running Examples

Each example contains a readme.txt and run.sh script to demonstrate how to run it.

The root of the samples directory on the target file-system (/ti/syslink-examples/<device>) contains a script to execute all the examples provided.

On my host PC, I find that the dates of these execute files are old (2012). I do not find the products.mak including such path. What generates such folder and files? The old dates are right?

Thanks,

0 Robert W over 11 years ago in reply to Robert W

Mastermind 7100 points

I remember that OMAP L138 evm and L138 LCDK have different memory or something else. But I do not see the syslink examples build differentiate those two. Anyone knows I should care about these two or not? Thanks,

0 Robert W over 11 years ago in reply to Robert W

Mastermind 7100 points

I find a sample args for boot on link: http://processors.wiki.ti.com/index.php/OMAP-L138_LCDK_Linux_Software_Developer%27s_Guide

bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait ip=off mem=32M@0xc0000000 mem=64M@0xc4000000

After I change the memory segment to:

setenv bootargs console=ttyS2,115200n8 rw noinitrd root=/dev/nfs nfsroot=192.168.0.103:/home/lcdkl138/arm9_FS,nolock rw mem=32@0xC0000000 mem=64@0xC4000000 ip=dhcp earlyprintk

The boot fails:

baudrate=115200
bootargs=console=ttyS2,115200n8 rw noinitrd root=/dev/nfs nfsroot=192.168.0.103:/home/lcdkl138/arm9_FS,nolock rw mem=32@0xC000
0000 mem=64@0xC4000000 ip=dhcp earlyprintk
bootcmd=dhcp;setenv serverip 192.168.0.103;tftpboot;bootm
bootdelay=3
bootfile=uImage-omapl138-lcdk.bin
dnsip=192.168.0.1
ethact=DaVinci-EMAC
ethaddr=00:00:a0:00:fb:c7
fileaddr=C0700000
filesize=1F221C
gatewayip=192.168.0.1
ip_method=dhcp
ipaddr=192.168.0.122
netargs=run bootargs
netmask=255.255.255.0
rl=tftp 0xc0700000 uImage; bootm
serverip=192.168.0.103
stderr=serial
stdin=serial
stdout=serial
ver=U-Boot 2010.12 (May 07 2012 - 16:09:45)

Environment size: 686/65532 bytes
U-Boot > boot
BOOTP broadcast 1
DHCP client bound to address 192.168.0.108
Using DaVinci-EMAC device
TFTP from server 192.168.0.103; our IP address is 192.168.0.108
Filename 'uImage-omapl138-lcdk.bin'.
Load address: 0xc0700000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #########
done
Bytes transferred = 2040372 (1f2234 hex)
## Booting kernel from Legacy Image at c0700000 ...
   Image Name:   Linux-3.1.10
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2040308 Bytes = 1.9 MiB
   Load Address: c0008000
   Entry Point: c0008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

What is the problem now?

0 Robert W over 11 years ago in reply to Robert W

Mastermind 7100 points

Hi,

I still cannot figure out the problem (cannot run example messageq on target). Here is the settings of product.mak content:

lcdkl138@lcdkl138-XPS-8500:~/syslink_2_21_03_11$ make .show-products
DEPOT                    = /home/lcdkl138
DEVICE                   = OMAPL1XX
GPPOS                    = Linux
SDK                      = NONE
TI81XXDSP_DMTIMER_FREQ   =
SYSLINK_BUILD_DEBUG      = 1
SYSLINK_BUILD_OPTIMIZE   = 0
SYSLINK_TRACE_ENABLE     = 1
LOADER                   = ELF
SYSLINK_INSTALL_DIR      = /home/lcdkl138/syslink_2_21_03_11
IPC_INSTALL_DIR          = /home/lcdkl138/ti/ipc_1_25_03_15
BIOS_INSTALL_DIR         = /home/lcdkl138/ti/bios_6_35_04_50
XDC_INSTALL_DIR          = /home/lcdkl138/ti/xdctools_3_25_03_72
LINUXKERNEL              = /home/lcdkl138/ti-sdk-omapl138-lcdk-01.00.00/board-support/linux-3.1.10
QNX_INSTALL_DIR          =
CGT_ARM_PREFIX           = /home/lcdkl138/ti/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-
CGT_C64P_INSTALL_DIR     =
CGT_C64P_ELF_INSTALL_DIR =
CGT_C674_INSTALL_DIR     =
CGT_C674_ELF_INSTALL_DIR = /home/lcdkl138/ti/ccsv5/tools/compiler/c6000_7.4.4
CGT_M3_ELF_INSTALL_DIR   =
CGT_A8_ELF_INSTALL_DIR   =
EXEC_DIR                 = /home/lcdkl138/arm9_FS
lcdkl138@lcdkl138-XPS-8500:~/syslink_2_21_03_11$

I also notice that the executables of messageq (both debug and release versions, especially DSP core code size) have different size with the SD card partition 3 fiiles (of course their names are different)

Here is a picture of the release file size:

It is about 123.4 kB vs. 400.9 kB. DSP core size is 4.4 MB vs. 5.8 MB. What makes such a difference?

Thanks,

0 Titusrathinaraj Stalin over 11 years ago in reply to Robert W

TI__Guru** 116100 points

Hi,

You will get answers for all the questions from the below thread which is newly created by you.

Do not follow up & put your questions in old thread even which is not closed

http://e2e.ti.com/support/embedded/linux/f/354/t/341242.aspx

Processors

Processors forum

syslink sample error on the OMAPL138-LCDK

Configuring Kernel Parameters

Running Examples