Hi.
I've used the script provided in elinux.org/BeagleBoardUbuntu to
install the DSP files. After this when i try sudo dsp-test I get this
error:
create_node:dsp node allocate failed
main: dsp node creation failed
my kernel is the last version: 2.6.37.2-x3
What could i be missing? Thank you.
xM or C4?
xM: has always been broken..
C4: it worked at one point, but i need to find time to bisect it again..
Let me know if your interested on working on this..
Regards,
xM or C4?
Hi
Neither. I have a B7, but i suppose it's not much different from C4.
So you're saying it's not currently working?
Let me know if your interested on working on this..
I'm not sure I have enough knowledge to work on this...
Thank you.
xM or C4?
Hi
Neither. I have a B7, but i suppose it's not much different from C4.
So you're saying it's not currently working?
Those are close enough, yeah it's currently not working...
Let me know if your interested on working on this..
I'm not sure I have enough knowledge to work on this...
No one ever does when they start.. 
Regards,
>> Let me know if your interested on working on this..
> I'm not sure I have enough knowledge to work on this...
No one ever does when they start..
I guess I could give it a try, but I'll need a lot of help along the
way.
Regards,
Ramiro.
You have the proper files in /lib/dsp? There's nothing on the console?
(dmesg) How about the kernel config file?
Felipe, if he followed the direction i have on that wiki link the
lib's are installed by default, right before it builds gst-dsp..
https://github.com/RobertCNelson/2.6.39-devel/blob/master/create_dsp_package.sh
It's currently using: TI_DSPbinaries_RLS23.i3.8-3.12 i know you do a
lot DSP work, are these the prefered or is there a newer/better
release to pull them from?
Regards,
Hi Robert,
Hi,
Guillaume said that he fixed the problem by forcing the CPU checks in
arch/arm/mach-omap2/mailbox.c.
I haven't seen the patch, but I guess it shouldn't be that hard.
My problem was there were no mailboxes for DM3730 (beagle xM CPU), so I made it available.
The little hack is available here:
http://guillaume.gardet.free.fr/OMAP/patch_add-omap-mailboxes-for-dm3730.patch
I did not submit it yet.
Guillaume
I'm having the same issue, how should I apply this patch?
This should be taken care with the cpu_is_omap34xx check[1].
I haven't seen the kernel you are trying to boot but it seems it has
an older version of the omap mailbox driver.
Regards,
Omar
your-kernel$ wget <Guillaume's.patch>
your-kernel$ git am <Guillaume's.patch>
Or take the one on mainline:
git remote add <linux-2.6>
git remote update
git cherry-pick ff0fba0bca4182e022c0a2ac0f3e63508e86e9f1
Regards,
Omar
Le 20/04/2011 18:16, Omar Ramirez a �crit :
My problem was there were no mailboxes for DM3730 (beagle xM CPU), so I made
it available.
The little hack is available here:
http://guillaume.gardet.free.fr/OMAP/patch_add-omap-mailboxes-for-dm3730.patchThis should be taken care with the cpu_is_omap34xx check[1].
Not all versions of the CPU have a DSP.
I haven't seen the kernel you are trying to boot but it seems it has
an older version of the omap mailbox driver.
This was the 2.6.37 from tmlind.
Guillaume
Indeed, AFAIK 3503 and 3515 doesn't have DSP, however the driver is
not generic enough to distinguish other than dsp or iva users.
When the driver is reworked to be used by anybody dynamically this
portion of the code along with most of the cpu_is checks should go
away.
Regards,
Omar
Hi Jeff,
If you don't want to patch it, 2.6.39-rc4 just finished building last
night for Maverick:
http://rcn-ee.net/deb/maverick/v2.6.39-rc4-d3/install-me.sh
mailbox.c from 2.6.39-rc4:
#if defined(CONFIG_ARCH_OMAP3)
else if (cpu_is_omap34xx()) {
list = omap3_mboxes;
list[0]->irq = platform_get_irq(pdev, 0);
}
#endif
I'm unable to test the DSP with it this week, as my xM's currently
across the us, i brought a c4 with on my trip.. (but it installed fine
and my build farm at home is still running with the new version..)
it'll boot fine, just note the smsc95xx is no longer usb1 in 2.6.39's,
but actually eth0...
Regards,
2.6.39-rc3-d3 had a problem, not seeing the on-board network card on the -XM. Is it fixed in 2.6.39-rc4-d3?
Regards
Sid.
Can I just run this script from my BeagleBoard then?
Hi Sid,
Yeah, the ehci bus was broken in mainline for omap's, but i applied
Juergen Kilb's fix for it.. so "2.6.39-rc3-d3" should have been the
first..
https://github.com/RobertCNelson/2.6.39-devel/commit/086e07a6729a6596556f3a919ae728d4aa63e23a
But if it's just the usb/network you can't see, double check it's not
showing up as eth0 now..
If there's no LED lights on the network connector:
sudo rmmod smsc95xx
sudo modprobe smsc95xx
first saw it in 2.6.38, and i have one board that is 25/75% boots up
into that situation..
Regards,