SYSLink Build for L138.

Jason Urban

Prodigy 180 points

Other Parts Discussed in Thread: SYSBIOS, OMAP-L138

Working on building SYSLink for an L138 running SYSBIOS on the DSP and QNX on the ARM.

Versions installed:

- BIOS 6_33_01_25

- IPC 1_24_00_16

- SYSLink 2_10_02_17

- XDC Tools 3_23_00_32

- QNX 6.4

- Running on a Windows devel host

- No Linux development installed. No Linux shell or anything else Linux related.

I've gone through the SysLink Install guide which seems to support QNX. However, I do CCSv4 installed but not sure where to point the CGT directory. I'm getting a string of these errors when doing a make syslink-driver:

C:/TI_SW/syslink_2_10_02_17/packages/ti/syslink/ipc/hlos/GateMP_qnx.c: In function 'GateMP_setup':
C:/TI_SW/syslink_2_10_02_17/packages/ti/syslink/ipc/hlos/GateMP_qnx.c:431: error: 'GateMP_RemoteCustom1Proxy_create' undeclared (first use in this function)
C:/TI_SW/syslink_2_10_02_17/packages/ti/syslink/ipc/hlos/GateMP_qnx.c:431: error: (Each undeclared identifier is reported only once
C:/TI_SW/syslink_2_10_02_17/packages/ti/syslink/ipc/hlos/GateMP_qnx.c:431: error: for each functionit appears in.)

Here is the .show-products output from products.mak

DEVICE = OMAPL1XX

GPPOS = Qnx

SDK = NONE

TI81XXDSP_DMTIMER_FREQ =

SYSLINK_BUILD_DEBUG = 1

SYSLINK_BUILD_OPTIMIZE = 0

SYSLINK_TRACE_ENABLE = 1

LOADER = COFF

SYSLINK_INSTALL_DIR = C:/TI_SW/syslink_2_10_02_17

IPC_INSTALL_DIR = c:/TI_SW/ipc_1_24_00_16

BIOS_INSTALL_DIR = c:/TI_SW/bios_6_33_01_25

XDC_INSTALL_DIR = c:/TI_SW/xdctools_3_23_00_32

LINUXKERNEL =

QNX_INSTALL_DIR = C:/QNX641

CGT_ARM_PREFIX =

CGT_C64P_INSTALL_DIR =

CGT_C674_INSTALL_DIR = c:/TI_SW/c6000

CGT_C674_ELF_INSTALL_DIR =

CGT_M3_ELF_INSTALL_DIR =

CGT_A8_ELF_INSTALL_DIR =

EXEC_DIR =

Am I missing something in a config, tools, make file, or anything else? I've searched the forums and elsewhere online but there is no straight information on compiling this for QNX.

Thanks!

over 13 years ago

0 Ramsey over 13 years ago

TI__Genius 12025 points

Jason,

You are getting those build errors because we do not support QNX on OMAPL1XX, only for TI814X. Specifically, that symbol is defined in GateMPDefs.h which would require SYSLINK_PLATFORM_OMAPL1XX to be defined.

If you are trying to port SysLink on QNX for OMAPL1XX, then you need to go into ti/syslink/utils/hlos/usr/Qnx/usr_lib/common.mk and add an additional check for SYSLINK_PLATFORM that matches OMAPL1XX. Then define SYSLINK_PLATFORM_OMAPL1XX. But this might just be the first of many issues.

~ Ramsey

0 Arnie Reynoso over 13 years ago

TI__Expert 6860 points

Jason,

On the OMAP-L138, SysLink GPP supported is only on Linux. SysLink does support QNX for the GPP but only on TI814x devices. The Makefile (build) should have caught this as it does for various other DEVICE/GPPOS combinations.

0 Jason Urban over 13 years ago in reply to Arnie Reynoso

Prodigy 180 points

Ramsey/Arnie-

Thanks for the responses. I may try falling back to DSPLink since there's part of a BSP Project in QNX. However, I was having build issues with DSPLink and moved up to SYSLink.

Any hints for DSPLink?

Basically, I want one of the 'Links for ARM-to-DSP executable loading/start and to transfer buffers of data during runtime.

0 Arnie Reynoso over 13 years ago in reply to Arnie Reynoso

TI__Expert 6860 points

BTW: The supported Devices and GppOS combinations are stated in the SysLink release notes provided in the product.

Out of curiosity, where are you obtaining the QNX Board Support Package (BSP) for this device. We are not aware of any newer QNX BSPs that support this device thus never attempted to port SysLink to this device.

0 Jason Urban over 13 years ago in reply to Arnie Reynoso

Prodigy 180 points

This was my baseline thought for being able to use one of packages with QNX:

http://community.qnx.com/sf/wiki/do/viewPage/projects.bsp/wiki/DSPLink?

Basically, what packages do I need in order to handle this setup:
- OMAP L138 (using LogicPD SOM)

- QNX OS on the ARM

- DSP functions/SW on the DSP

- Load the DSP from the ARM

- Get data between DSP and ARM

Do I need go down this DSP/SYSLink/BIOS route for all this?

Jason.

0 Arnie Reynoso over 13 years ago in reply to Jason Urban

TI__Expert 6860 points

DSPLink or SysLink does provided basic services to load/run the slave cores (DSP). They also has a few modules that facilitate data passing between the cores.

If there is a DSPLink port available for QNX, this may be a better approached to trying to get SysLink built for your device.

There is a Audio SOC example for your device that leverage DSPLink (this builds/runs on Linux). Regardless, it's still a good starting point for your application once you get DSPLink built and running with QNX on OMAP-L138.

Here are a few good links that you may already be aware of but good reference points.

http://processors.wiki.ti.com/index.php/Category:DSPLink

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

http://processors.wiki.ti.com/index.php/Category:SysLink

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

Processors

Processors forum

SYSLink Build for L138.