BeagleBoard + EZSDK 5.05 + Kernel 3.3.7 + DPS Support

Hi Martin,

Which cross compiler you are using and could you check the exported PATH to the cross-compiler to assure that you are using the right one?

Hi Cvetolin,

thank you for answer.

• For the first way (manual syslink compiling), the standard cross compiler included in Sitara is used. Here is my compiling setting of product.mak The $(DEPOT) is the link to the ti-sdk-beagleboard-05.05.00.00 install folder.

......

######## For OMAP3530 device ########

ifeq ("$(DEVICE)","OMAP3530")

LINUXKERNEL             = $(DEPOT)/board-support/linux-3.3.7-r115

CGT_ARM_INSTALL_DIR     = $(DEPOT)/linux-devkit

CGT_ARM_PREFIX          = $(CGT_ARM_INSTALL_DIR)/bin/arm-arago-linux-gnueabi-

IPC_INSTALL_DIR         = $(DEPOT)/ipc_1_24_03_32

BIOS_INSTALL_DIR        = $(DEPOT)/bios_6_33_05_46

XDC_INSTALL_DIR         = $(DEPOT)/xdctools_3_23_03_53

# If LOADER=ELF then below elf tools path is required else set C64P path

ifeq ("$(LOADER)","ELF")

CGT_C64P_ELF_INSTALL_DIR= $(DEPOT)/_your_c64pelf_code_gen_install_

else

CGT_C64P_INSTALL_DIR    = $(DEPOT)/ccsv5/tools/compiler/c6000

endif

.......

• For the http://omappedia.org/wiki/Syslink_Project same cross compiler is used althrought the codesourcey is recomented. Should be this step the problem of the second way?

Hi,

here, http://e2e.ti.com/support/embedded/linux/f/354/t/162692.aspx?pi68664=2 , I found that syslink is not supported for kernel 3.3.x. So I am not sure, is the syslink supported or not?

How can I use  DPS for Ti EZSDK for BB-xM? Is there a source EZSDK for older Kernel 2.6.x which is supported by syslink?

thank you

m.

Hi Martin,

I have the same problem, but with old C4 Beagleboard. I even tried to talk with TI support but they said that I should try here or on Beagle forums, because they don't support Beagleboard products.  Hope that if you succeed then you inform about it here. I will try today evening some not EZSDK solution, with kernel from PSP 04.02.00.07

Kind regards,

V.

You have rigth as we can see. ;-) Kernel 3.x does not support Syslink and dsplink so now, I am trying Angstrong Linux. The online builder has a support for DSP so you can try it. 

I also try http://elinux.org/index.php?title=ECE497_Notes_on_DSP_via_c6run&oldid=152360 and it works. The modules has been cteared but the examples for DPS doesnt work. Maybe I shloud rewrite some memory allocation.

I saw exercises from ECE497, but I have to use SysLink. It can't be DSPLink even :)

I thought about Angstrom. I remember that I saw there was possible to add TI SysLink Examples in builder. It is interesting how then tie it with SysLink? And how to force it to use kernel 2.6.x

I wanted to try EZSDK for beagleboard with 2.6.x kernel but I didn't find it. I think it shlould be a way. 

I also tried to find it. EZSDK 4.01 had 2.6.32 and next EZSDK 5.02 was with 2.6.39. But it disappeard :D They keep only new version.

Here is http://www.ti.com/lsds/ti/tools-software/linux.page that others has 2.6.x kernels. The question is what is easier (and possible?) now: adapt other board SDK to ours or try with building own kernel and file system. I'm not enough experienced to answer this question.

I am not sure if I am able to help you with this issue. :-) We are using Ang.. at this time... with 2.6 so you can try to make own 2.6 kernel with own FS.

Hi, Cvetolin

  We are using "ti-sdk-beagleboard-05.05.01.00-Linux-x86-Install" from TI.com. and i also have the same problems. My question is: does this sdk support "syslink_2_21_00_03" ?

==

Following is my products.mak and errors when i execute make syslink:

=== product.mak

root@ubuntu:syslink# make .show-products
DEPOT                    = /opt/ti
DEVICE                   = OMAP3530
GPPOS                    = Linux
SDK                      = EZSDK
TI81XXDSP_DMTIMER_FREQ   =
SYSLINK_BUILD_DEBUG      = 1
SYSLINK_BUILD_OPTIMIZE   = 0
SYSLINK_TRACE_ENABLE     = 1
LOADER                   = ELF
SYSLINK_INSTALL_DIR      = /home/mtu/syslink_2_21_00_03
IPC_INSTALL_DIR          = /opt/ti/ipc
BIOS_INSTALL_DIR         = /opt/ti/bios
XDC_INSTALL_DIR          = /opt/ti/xdc
LINUXKERNEL              = /opt/ti/linux
QNX_INSTALL_DIR          =
CGT_ARM_PREFIX           = /opt/ti/cross_compiler/bin/arm-arago-linux-gnueabi-
CGT_C64P_INSTALL_DIR     =
CGT_C64P_ELF_INSTALL_DIR =
CGT_C674_INSTALL_DIR     =
CGT_C674_ELF_INSTALL_DIR =
CGT_M3_ELF_INSTALL_DIR   =
CGT_A8_ELF_INSTALL_DIR   =
EXEC_DIR                 = /nfsboot/syslink
root@ubuntu:syslink#

===make syslink

make[2]: Entering directory `/home/mtu/syslink_2_21_00_03/packages/ti/syslink/utils/hlos/knl/Linux'
make -C /opt/ti/linux SUBDIRS=/home/mtu/syslink_2_21_00_03/packages/ti/syslink/utils/hlos/knl/Linux modules
make[3]: Entering directory `/usr/local/ti-sdk-beagleboard/board-support/linux-3.3.7-r115'
  CC [M]  /home/mtu/syslink_2_21_00_03/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/family/hlos/knl/omap3530/omap3530dsp/omap3530_hal.o
In file included from /home/mtu/syslink_2_21_00_03/packages/ti/syslink/inc/knl/Linux/omap3530_hal_mmu_defs.h:52:0,
                 from /home/mtu/syslink_2_21_00_03/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/family/hlos/knl/omap3530/omap3530dsp/omap3530_hal.c:52:
arch/arm/plat-omap/include/plat/iommu.h: In function 'dev_to_omap_iommu':
arch/arm/plat-omap/include/plat/iommu.h:135:46: error: dereferencing pointer to incomplete type
make[4]: *** [/home/mtu/syslink_2_21_00_03/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/family/hlos/knl/omap3530/omap3530dsp/omap3530_hal.o] Error 1
make[3]: *** [_module_/home/mtu/syslink_2_21_00_03/packages/ti/syslink/utils/hlos/knl/Linux] Error 2
make[3]: Leaving directory `/usr/local/ti-sdk-beagleboard/board-support/linux-3.3.7-r115'
make[2]: *** [default] Error 2
make[2]: Leaving directory `/home/mtu/syslink_2_21_00_03/packages/ti/syslink/utils/hlos/knl/Linux'
make[1]: *** [syslink-driver-linux] Error 2
make[1]: Leaving directory `/home/mtu/syslink_2_21_00_03/packages'
make: *** [syslink-driver] Error 2
root@ubuntu:syslink#

=== opt devs

root@ubuntu:ti# ls -l
total 20
lrwxrwxrwx  1 root root   15 2012-12-04 12:19 bios -> bios_6_34_03_19
drwxr-xr-x  7 root root 4096 2012-12-04 12:19 bios_6_34_03_19
drwxrwsr-x  6 root root 4096 2012-12-04 14:27 C6000CGT6.1.22
lrwxrwxrwx  1 root root   14 2012-12-04 14:27 cgt -> C6000CGT6.1.22
lrwxrwxrwx  1 root root   42 2012-12-04 14:36 cross_compiler -> /usr/local/ti-sd
k-beagleboard/linux-devkit
lrwxrwxrwx  1 root root   14 2012-12-04 12:19 ipc -> ipc_1_25_01_09
drwxr-xr-x  6 root root 4096 2012-12-04 12:16 ipc_1_25_01_09
lrwxrwxrwx  1 root root   60 2012-12-04 12:20 linux -> /usr/local/ti-sdk-beagleb
oard/board-support/linux-3.3.7-r115
lrwxrwxrwx  1 root root   19 2012-12-04 12:20 xdc -> xdctools_3_24_05_48
drwxr-xr-x 10 root root 4096 2012-12-04 12:18 xdctools_3_24_05_48
root@ubuntu:ti#

Hi Bennett,

The "ti-sdk-beagleboard-05.05.01.00-Linux-x86-Install" release from TI.com does not support "syslink_2_21_00_03". You could search for it in the sdk's folder. It would be useful to read the Developers guide and look at the table containing information about applications available by development platform at the link below:

http://processors.wiki.ti.com/index.php/Sitara_Linux_Software_Developer%E2%80%99s_Guide

BR

Tsvetolin Shulev