I am new to the beagle board and I need some help setting up my
developing tools. (I am using ubuntu 10.04 and 9.10, the board will be
running on Ångström)
I want to develop some audio apps, which shall make use of the DSP
Core. (Voice processing, recognition, classification of signals).
There are some tutorials but I am confused. Which tools to I need to
build DSP applications?
I also don't know how to use and configure the cross compiler needed
for the GPP part of DSP apps. In one of the tutorials I read, that one
should use the crosscompiler built by OE. As OE doesn't work right
now, I need a toolchain, that doesn't rely anyhow von OE. I do not
have the time to fix OE, maybe I can do this later (lowest priority).
Which tools do I need and how must I configure them?
I already installed the following tools:
a) TI C6000 compiler (current version, 7?)
b) gcc (build-essential)
c) XDCTools (Why do I need them?)
Thank you in advance!
With kind regards,
Sven Wilksen
It currently works fine for me and countless others right now when using angstrom.
regards,
Koen
I get many errors, which I can't resolve and which I won't discuss
here. 
OE is not so important for me and I must focus on setting
up the toolchain. I want to focus on dsp apps and not on custom build
images for the beagleboard.
Which is the correct cross compilation toolchain, that works for DSP
Link, applications using DSP Link and other GPP applications?
The one that OE builds, but I won't discuss that here
ok ok, you got me
Looks like I can't get around OE.
I got several issues with OE. Sometimes, it tells me, the preferred u-
boot version could not be found and the expat package can not be
extracted.
THe last error is an gzip issue. The package is not broken, gzip can't
just extract the files. I tried repairing the package (unpacking on a
windows PC and packing it again on ubuntu) but of course the md5
checksum do not match afterwards.
Can I download the toolchain anywhere without having to do an OE build?
I'm facing the same problem. I need to get the dsp working on
beagleboard. I'm following a very well written guide. It uses OE but
it's very clear.
http://pixhawk.ethz.ch/tutorials/start
For programming the DSP side I'm thinking about using Code Composer
Studio even if it has been just released for linux and I don't know
how it works.
I hope it will be helpful.
Regards,
Matteo
If OE is giving you much trouble, CodeSourcery has the Lite version of
their ARM toolchain available at http://www.codesourcery.com/sgpp/lite/arm
which should also do the job.
Utilizing the DSP can be done via DSP/Link as you mentioned, so its
documentation might be a good place to get started. Please see
http://processors.wiki.ti.com/index.php/Building_DSPLink - it has some
examples included and describes the build process. It's a bit involved
but there's a project in the making to make DSP development easier.
Hope this helps a little.
Yaman
That guide is a few months behind on the status quo. If you use the angstrom instructions it's a easy as downloading the angstrom setup script and the restricted c6x compiler.
regards,
Koen
The setups script is really, makes things much easier. But I still
have one problem.
Bitbake gives me this warning "preferred version git of u-boot not
available (for item u-boot)"
That prevents a successfull build. I had the problem yesterday on both
my computer at work and on my private laptop. (Both running ubuntu
10.04). This time, the error occured on my private computer at home,
running on ubuntu 9.10.
I downloaded the current oebb.sh script today and ran the following
commands:
oebb.sh config beagleboard
(no problems)
oebb.sh update
(first run: fatal: git checkout: branch org.openembedded.dev already
exists, sceond run without problems)
oebb.sh bitbake base-image
(parsing without error, but then "NOTE: preferred version git of u-
boot not available (for item u-boot)")
I couldn't find a solution for my problem. I think I'm doing something
wrong.
regards,
Sven
That guide is a few months behind on the status quo. If you use the angstrom instructions it's a easy as downloading the angstrom setup script and the restricted c6x compiler.
regards,
Koen
The setups script is really, makes things much easier. But I still
have one problem.
Bitbake gives me this warning "preferred version git of u-boot not
available (for item u-boot)"
That prevents a successfull build. I had the problem yesterday on both
my computer at work and on my private laptop. (Both running ubuntu
10.04). This time, the error occured on my private computer at home,
running on ubuntu 9.10.
This is a warning, it does not stop builds from succeeding.
Philip
I got the real error. I can't access the logs on my computer at work,
so I had to run bitbake here at home again.
Here, bitbake or gcc fails here:
##LOG###
/home/sven/OE/build/tmp-angstrom_2008_1/work/i686-linux/qemu-
native-0.12.3-r2/qemu-0.12.3/target-ppc/translate.c: In function
'gen_stfq':
/home/sven/OE/build/tmp-angstrom_2008_1/work/i686-linux/qemu-
native-0.12.3-r2/qemu-0.12.3/target-ppc/translate.c:5248: internal
compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions.
make[1]: *** [translate.o] Error 1
make: *** [subdir-ppc-softmmu] Error 2
FATAL: oe_runmake failed
ERROR: Function do_compile failed
NOTE: package qemu-native-0.12.3-r2: task do_compile: Failed
ERROR: TaskFailed event exception, aborting
ERROR: Task 1280 (virtual:native:/home/sven/OE/sources/openembedded/
recipes/qemu/qemu_0.12.3.bb, do_compile) failed with 256
ERROR: Build of virtual:native:/home/sven/OE/sources/openembedded/
recipes/qemu/qemu_0.12.3.bb do_compile failed
ERROR: Task 1280 (virtual:native:/home/sven/OE/sources/openembedded/
recipes/qemu/qemu_0.12.3.bb, do_compile) failed with 256
Waiting for 1 active tasks to finish:
1: binutils-cross-2.18.50.0.7-r7.1 do_compile (pid 16221)
ERROR: 'virtual:native:/home/sven/OE/sources/openembedded/recipes/qemu/
qemu_0.12.3.bb' failed
NOTE: package binutils-cross-2.18.50.0.7-r7.1: task do_compile:
Succeeded
ERROR: 'virtual:native:/home/sven/OE/sources/openembedded/recipes/qemu/
qemu_0.12.3.bb' failed
ERROR: 'virtual:native:/home/sven/OE/sources/openembedded/recipes/qemu/
qemu_0.12.3.bb' failed
##END OF LOG##
That guide is a few months behind on the status quo. If you use the angstrom instructions it's a easy as downloading the
angstrom setup script and the restricted c6x compiler.
Sorry, where can I find the angstrom instructions?
Thank you,
Matteo
That guide is a few months behind on the status quo. If you use the angstrom instructions it's a easy as downloading the
angstrom setup script and the restricted c6x compiler.
Sorry, where can I find the angstrom instructions?
http://www.angstrom-distribution.org/ -> developers
Please help me... I'm a newbie and I'm very confused...!
My goal is to get DSPLink working on OMAP 3530 SoC. I have a
beagleboard with angstrom on the SD card.
I dowloaded the setup script I found here:
http://gitorious.org/angstrom/angstrom-setup-scripts/commits/texas-instruments
Is this the correct script to obtain an OE image of Angstrom with
DSPLink inside??
Then I run the following commands:
sh oebb.sh config beagleboard
source ./oe/environment
sh oebb.sh update
bitbake base-image
If everything is OK, I should get the kernel image I want, shouldn't
I?
Thanks,
regards,
Matteo
Anyone had that kind of problems, too?
I would really like to use OE but when it keeps failing, it's useless
for me. 
Could someone with a working OE please tell me, on which OS it runs
and which version of gcc is used?
Regards,
Sven Wilksen
Anyone had that kind of problems, too?
I would really like to use OE but when it keeps failing, it's useless
for me. 
Could someone with a working OE please tell me, on which OS it runs
and which version of gcc is used?
Most Linux's.
It should work with any reasonably recent gcc. For building the
software that runs on the Beagle, OE will build a suitable gcc based
cross compiler.
Philip
I had exactly this problem on three computers. Two with recently
installed ubuntu 10.04 and one with a recently installed ubuntu 9.04
And these are three completely different machines.
Really strange. Seems to me like the current gcc version in ubuntu is
broken.
OE Problem solved!
Heres the problem:
gcc 4.4.1 won't compile all packages. Here it fails to compile qemu
0.12.3. Tested it on three different computers.
Fix:
Used gcc 4.1 to compile. No problems, all task completed successfully.
Only tested on my desktop computer running ubuntu 9.10.
So now I got the cross toolchain.
But: I did not fully understand how the makefiles of the dsplink
package know which toolchain to use.
It would be great If someone could explain this to me 
You don't need to know, because 'bitbake ti-dsplink' will take care of that for you.