Cannot Execute Binary File & DSP

I'm having issues with the 'cannot execute binary file' error. First
of all when I tried to install the CodeSourcery tools v 2010.09-50 for
GNU/Linux, I get the error when trying to run the installer. But I saw
that others were having this issue, so I also did the manual install
with tar and updated $PATH. However then when I got to test that its
working with 'arm-none-linux-gnueabi-g++ -v' I get the same error
again. I also get this same error when trying to run another installer
for some TI DSP tools.

I have BeagleBoard-xM rev B and I installed Linux through the 'Demo
Image' method from http://elinux.org/BeagleBoardUbuntu#Maverick_10.10_2
on an 8GB sd card. I'm trying to run PTAMM which is CPU intensive and
streams from a web-cam, so I need to get DSP set-up to do some of the
work.

Any help would be appreciated!

I'm having issues with the 'cannot execute binary file' error. First
of all when I tried to install the CodeSourcery tools v 2010.09-50 for
GNU/Linux, I get the error when trying to run the installer. But I saw
that others were having this issue, so I also did the manual install
with tar and updated $PATH. However then when I got to test that its
working with 'arm-none-linux-gnueabi-g++ -v' I get the same error
again. I also get this same error when trying to run another installer
for some TI DSP tools.

Just for sanity sake for users on this email list... On the system you
get this "cannot execute binary file" error.. Please run "uname -m"
and report it..

I have BeagleBoard-xM rev B and I installed Linux through the 'Demo
Image' method from BeagleBoardUbuntu - eLinux.org
on an 8GB sd card. I'm trying to run PTAMM which is CPU intensive and
streams from a web-cam, so I need to get DSP set-up to do some of the
work.

Regards,

uanme -m is: armv71

I figured... The CodeSoucery tools and TI DSP tools are x86 binaries..
Your not going to get them to run directly/natively on the target.

Regards,

Yea I should have mentioned I just figured that out earlier. Now I’m working through this tutorial: http://www.elinux.org/BeagleBoard_Ubuntu_%26_DSP_From_Sources but I’m having issues when I build the .deb package for the kernel. I get the error:

dpkg-gencontrol: error: current host architecture ‘armel’ does not appear in package’s architecture list (amd64)

Any idea what might be causing that? Everything up to that point had worked fine…

I pushed out a patch from Robert.

http://bazaar.launchpad.net/~beagleboard-kernel/+junk/2.6-stable/revision/190

so do a 'bzr pull'

So far it works on my ubuntu 10.10 amd64 system, when cross building..

Just waiting for my panda to finish building with the same patch to
make sure there are no regressions's..

Regards,

Ok great I’ll try it and let you know how it goes. Thanks!

Well the ./build_deb worked this time and I was able to finish out the
tutorial. However when I insert the card into my BeagleBoard nothing
happens, the lights for the SD card don't light at all. I'm using a
16GB microSd card and I'm not sure if that may have something to do
with it. Also I was a little unsure about the 'setenv' commands, as
I'm using bash. I substituted it with:

export bootargs=...
export bootcmd=...

I have BeaglBoard-xm rev B, has anyone tried a 16GB card?

Well the "build_deb.sh" script just builds a deb file....

So how did you build your sd card for the beagle? The format for the
the X-loader/U-boot is pretty important.. It's best to use one of my
demo images by default, and then install the deb file aftewards..

http://elinux.org/BeagleBoardUbuntu

Regards,

Well i went through this entire tutorial:
http://www.elinux.org/BeagleBoard_Ubuntu_%26_DSP_From_Sources . There
were instructions for building the X-loader and U-boot which I did.
The reason I used this tutorial is because it was more recent and had
instructions for setting up the DSP bridge and there were some steps
in building the kernel which enabled DSP drivers, I wasn't sure if the
demo images would have that enabled or not...

Except the dspbridge is already enabled in my demo images. Right now,
the only change between the demo image kernel and the one you build on
the wiki is the *.deb generation fix and an audio fix... (which will
then be updated when natty final gets out). But with that wiki Robert
goes into alot more detail with using a different userspace
library(userspace-dspbridge) then what i was defaulting too (gst-dsp),
on my wiki page..

Regards,

Well i went through this entire tutorial:
http://www.elinux.org/BeagleBoard_Ubuntu_%26_DSP_From_Sources . There
were instructions for building the X-loader and U-boot which I did.
The reason I used this tutorial is because it was more recent and had
instructions for setting up the DSP bridge and there were some steps
in building the kernel which enabled DSP drivers, I wasn't sure if the
demo images would have that enabled or not...

Ok well I have been through your tutorial successfully as well but I
don't think I had the DSP working, or atleast the PTAMM program I was
running was streaming video very slowly. Tomorrow I'll try using your
demo image and maybe the DSP stuff from the other tutorial.

Thanks for all your help!

Ok well I have been through your tutorial successfully as well but I
don't think I had the DSP working, or atleast the PTAMM program I was
running was streaming video very slowly. Tomorrow I'll try using your
demo image and maybe the DSP stuff from the other tutorial.

Thanks for all your help!

I got the Natty demo image going, installed the DSP binaries, BIOS,
code generation utilities, and userspace utilities. I used modprobe to
load the mailbox module and the base image.

'cat /proc/interrupts' shows 28: DspBridge iommu fault but there is
nothing at 26 at this tutorial states:
http://omappedia.org/wiki/DSPBridge_Project#Working_with_bridge_driver

sudo ./cexec.out ddspbase_tiomap3430.dof64p gives:
DSP device detected!! - but nothing about DSPProcessor_Start

and sudo ./ping.out gives:
DSP device detected!!
DSPNode_Allocate failed: 0xffffffff

Also I noticed that there is no dspbridge.ko, only bridgedriver.ko and
and ldconfig gives:
/sbin/ldconfig.real: /lib/libqos.so.2 is not an ELF file - it has the
wrong magic bytes at the start.

I believe this is a part of the bridge userspace utilities...

Any ideas about what I'm doing wrong?

Hi Jeff,

What are you trying to do? How do you need to do with the dsp?

If you are going to use DSPBridge, please consider that the dspbridge
user space utils are pretty much broken. Instead you should use
dsp-tools:

http://elinux.org/BeagleBoard/dsp-tools

If you are looking for multimedia processing, checkout gst-dsp:

http://elinux.org/BeagleBoard/gst-dsp

vmjl

I’m running PTAMM, which uses video from a web cam and tracks different targets to localize and map an environment. It streams the web cam video along with the mappings and without the DSP it was too slow for practical purposes. So I thought maybe if the DSP were able to handle some of the video (it uses OpenGL and OpenCV) that would help improve performance.

So you think I should try gst-dsp instead?

A better question.. Is PTAMM even setup to use the DSP on the OMAP?

Just because you get the dsp running, doesn't mean some random
software will actually use it..

Regards,

I doubt that it is setup for it, atleast I was planning on having to do some modifications…

Robert Nelson, if you're around: I was doing a fresh build of BeagleBox
today and found that the SGX patches from your host are not accessible.
All URLs to http://rcn-ee.homeip.net:81/ are giving "Access Denied".

Do you know if this is a permanent change or just a temporary one? If
temporary, I can wait. No problem. If permanent, do you have any
objection to my placing the patches on gitorious for BeagleBox builds?

Thanks.