tidspbridge: problems executing sample apps

Commit Message

Javier Martin June 15, 2011, 3:19 p.m. UTC

Hi,
we have a Beagleboard xM (DM3730) and we are currently working with
stable kernel 2.6.39 and we have compiled the tisdpbridge in the
staging directory.

In order to test basic DSP functionality we are using
userspace-dspbridge from git repository
git://dev.omapzoom.org/pub/scm/tidspbridge/userspace-dspbridge.git and
commit 9c64192758fd066d1a3f50867919e7aa21f04387
And the following version of needed packages are being used:

bios_5_41_07_24
TI_CGT_C6000_6.1.17
xdctools_3_20_06_81

1- If I try prebuilt binaries (both for DSP side and userspace) I get
an execution error:

root@beagleboard:/dspbridge# ./ping.out
DSP device detected !!
DSPNode[   30.530944] DSPTrace: PING: **PING_TI_create: retval = 0x0 **
[   30.530975] PING: PING_TI_execute: Entered ...
[   30.530975]
Create succeeded[   30.545135] DSPTrace: PING: PING_TI_execute:
Received ping from GPP: cmd = 0xbebe0001; cnt = 0x200596aa
[   30.545166]

DSPNode_registerNotify succeeded
DSPNode_run succeeded
Ping: Id 1.000000 Msg 0.000000 Mem 15408.000000
DSPNode_GetMessage failed: 0xffffffc2
Ping: Id 1.000000 Msg 1.000000 Mem 15408.000000
DSPNode_GetMessage failed: 0xffffffc2

2- If I compile only MPU samples and use DSP prebuilt binaries it works fine.

3- If I compile both DSP side and MPU side samples it also gives an
execution error:

root@beagleboard:/dspbridge# ./cexec.out ddspbase_tiomap3430.dof64P
DSP device detected !!
[   45.862640] proc_load: Processor Loaded ddspbase_tiomap3430.dof64P
[   45.876892] proc_start: dsp in running state
DSPProcessor_Sta[   45.881927] procwrap_detach: deprecated dspbridge ioctl
rt succeeded.
Hit any key to terminate cexec.

root@beagleboard:/dspbridge# ./ping.out
DSP device detec[   64.484649] procwrap_detach: deprecated dspbridge ioctl
ted !!
DSPNode_Create failed: 0xffffffe3


In order to achieve option (3) I had to apply the attached patch to
fix some build errors and I had to copy libstdc++.so.5 to  /usr/lib32/
since I am on a 64bit machine
http://mirror.ovh.net/ubuntu//pool/universe/g/gcc-3.3/libstdc++5_3.3.6-15ubuntu4_i386.deb

Do you know what combination of DSP bios, TI CGT and xdctools is most
suitable for using with tidspbridge in kernel 2.6.39?

Thank you.

Comments

omar ramirez June 16, 2011, 8:56 p.m. UTC | #1

Hi Javier,

On Wed, Jun 15, 2011 at 10:19 AM, javier Martin
<[e-mail]> wrote:
> Hi,
>
> 1- If I try prebuilt binaries (both for DSP side and userspace) I get
> an execution error:
...
> DSPNode_GetMessage failed: 0xffffffc2

In this case, sample application is working, however the failures on
get_message are unexpected, it seems this arose when the error codes
were changed and the precompiled binaries where not updated, I'll fix
this, thanks for the heads up.

> 3- If I compile both DSP side and MPU side samples it also gives an
> execution error:
...
> root@beagleboard:/dspbridge# ./ping.out
> DSP device detec[   64.484649] procwrap_detach: deprecated dspbridge ioctl
> ted !!
> DSPNode_Create failed: 0xffffffe3
>
...
> Do you know what combination of DSP bios, TI CGT and xdctools is most
> suitable for using with tidspbridge in kernel 2.6.39?

This is mentioned in the wiki: bios 5.33.04 and cgt tools 6.0.7
http://omapedia.org/wiki/DSPBridge_Project#Initial_environment_setup

This version of the bios already has the xdc tools bundled. BTW I
replied to your gforge query in case it gives any information:
http://bit.ly/laeJFD

I also applied your patch to fix copying the dsp binaries on the build
system, thanks!

Regards,

Omar
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [e-mail]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Patch

diff --git a/source/product.mak b/source/product.mak
index 892faf5..1996366 100755
--- a/source/product.mak
+++ b/source/product.mak
@@ -13,12 +13,12 @@ 
 #
 
 # DSP BIOS
-SABIOS_VER   = 5.33.04
-SABIOS_VER_2 = 5_33_04
+SABIOS_VER   = 5.41.07.24
+SABIOS_VER_2 = 5_41_07_24
 
 # CodeGen Tools
 CGT55_VER = 3.2.2
-CGT6X_VER = 6.0.7
+CGT6X_VER = 6.1.17
 
 # Framework components
 FC_VER = 1_10_04
diff --git a/source/samplemakefile b/source/samplemakefile
index 4d11610..ac9f772 100755
--- a/source/samplemakefile
+++ b/source/samplemakefile
@@ -83,8 +83,8 @@  BRIDGE_EXPORT_PACKAGES = dsp/ti/dspbridge/dsp/bridge_product
 
 SAMPLE_PACKAGES = samples/dsp
 
-DLL_FILES=$(wildcard $(SAMPLE_PACKAGES)/*.dll64P))
-DOF_FILES=$(wildcard $(SAMPLE_PACKAGES)/*.dof64P))
+DLL_FILES=$(wildcard $(SAMPLE_PACKAGES)/*.dll64P)
+DOF_FILES=$(wildcard $(SAMPLE_PACKAGES)/*.dof64P)
 
 .samples: .bridge_samples
 
@@ -144,7 +144,7 @@  ifneq ($(DLL_FILES),)
 	$(CP) -f $(DLL_FILES) $(TARGETDIR)/dspbridge/
 endif
 ifneq ($(DOF_FILES),)
-	$(CP) -f $(DOF_FILES)/ $(TARGETDIR)/dspbridge/
+	$(CP) -f $(DOF_FILES) $(TARGETDIR)/dspbridge/
 endif
 
 #.execute_version_script: version.ksh $(VERSION_FILE)
diff --git a/source/samples/dsp/ddspbase.tci b/source/samples/dsp/ddspbase.tci
index 1746adc..d968cab 100755
--- a/source/samples/dsp/ddspbase.tci
+++ b/source/samples/dsp/ddspbase.tci
@@ -19,6 +19,8 @@ 
  *
  */
 
+var chipType = environment["config.chipType"];
+
 /* bridge default is 512, that's not enough sometimes */
 var traceSize = 512;