Quantcast
Channel: Processors forum - Recent Threads
Viewing all articles
Browse latest Browse all 17527

syslink: ProcMgr_load failure

$
0
0

Hello,

I am working with OMAP L138 and trying to upload a simple DSP program by calling ProcMgr_load. I create the DSP side using CCS projects. The project contains just an empty main function. When I map it to use the shared memory (i.e. 0x80000000) the program is loaded fine. But if I add SYS/Bios to the DSP project and use ti.platforms.evmOMAPL138 platform then I get memory mapping errors. For example:

WARNING: at arch/arm/mm/ioremap.c:207 __arm_ioremap_pfn_caller+0x15c/0x16c()
Modules linked in: syslink
[<c000d364>] (unwind_backtrace+0x0/0xf0) from [<c001b87c>] (warn_slowpath_common+0x4c/0x64)
[<c001b87c>] (warn_slowpath_common+0x4c/0x64) from [<c001b8b0>] (warn_slowpath_null+0x1c/0x24)
[<c001b8b0>] (warn_slowpath_null+0x1c/0x24) from [<c000f320>] (__arm_ioremap_pfn_caller+0x15c/0x16c)
[<c000f320>] (__arm_ioremap_pfn_caller+0x15c/0x16c) from [<c000f3a0>] (__arm_ioremap_caller+0x58/0x60)
[<c000f3a0>] (__arm_ioremap_caller+0x58/0x60) from [<bf025a0c>] (MemoryOS_map+0x148/0x3e0 [syslink])
[<bf025a0c>] (MemoryOS_map+0x148/0x3e0 [syslink]) from [<bf006d80>] (_ProcMgr_map+0x3c0/0x57c [syslink])
[<bf006d80>] (_ProcMgr_map+0x3c0/0x57c [syslink]) from [<bf010298>] (CoffLoaderTrgWrite_copy+0xc8/0x3bc [syslink])
[<bf010298>] (CoffLoaderTrgWrite_copy+0xc8/0x3bc [syslink]) from [<bf00b6b4>] (Coff_load+0xa80/0x1f70 [syslink])
[<bf00b6b4>] (Coff_load+0xa80/0x1f70 [syslink]) from [<bf00f5b4>] (CoffLoader_load+0x14c/0x3c0 [syslink])
[<bf00f5b4>] (CoffLoader_load+0x14c/0x3c0 [syslink]) from [<bf0025a4>] (Loader_load+0x98/0x174 [syslink])
[<bf0025a4>] (Loader_load+0x98/0x174 [syslink]) from [<bf004c6c>] (ProcMgr_load+0x104/0x358 [syslink])
[<bf004c6c>] (ProcMgr_load+0x104/0x358 [syslink]) from [<bf009ab0>] (ProcMgrDrv_ioctl+0xd40/0x1bd4 [syslink])
[<bf009ab0>] (ProcMgrDrv_ioctl+0xd40/0x1bd4 [syslink]) from [<c009200c>] (do_vfs_ioctl+0x7c/0x598)
[<c009200c>] (do_vfs_ioctl+0x7c/0x598) from [<c0092560>] (sys_ioctl+0x38/0x60)
[<c0092560>] (sys_ioctl+0x38/0x60) from [<c0009320>] (ret_fast_syscall+0x0/0x2c)
---[ end trace 414793cb713960c8 ]---
*** MemoryOS_map: Failed to map to host address space!
Error [0x897d2003] at Line no: 517 in file /home/glebf/ti/syslink_2_21_03_11/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/c
*** _ProcMgr_map: Memory_map failed
Error [0xfffffff1] at Line no: 2441 in file /home/glebf/ti/syslink_2_21_03_11/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslinkc
_ProcMgr_map for SlaveVirt:
dstAddr [0xc3011000]
sgList.paddr [0xc3011000]
sgList.offset [0x268]
sgList.size [0x2268]
Coff_load: Reading section [3] from file into host buffer

The DSP SW uses memory starting at 0xC3000000 as shown in the map file:

OUTPUT FILE NAME: <DemoDsp.out>
ENTRY POINT SYMBOL: "_c_int00" address: c3009380


MEMORY CONFIGURATION

name origin length used unused attr fill
---------------------- -------- --------- -------- -------- ---- --------
IROM 11700000 00100000 00000000 00100000 R X
IRAM 11800000 00040000 00000000 00040000 RW X
L3_CBA_RAM 80000000 00020000 00000000 00020000 RW X
DDR c3000000 01000000 00013d26 00fec2da RWIX

My question is: how does the hlos side determines memory mapping and what do I need to do to match the mapping of DSP side?

Regards

Gleb


Viewing all articles
Browse latest Browse all 17527

Trending Articles