DSPNode_allocated failed: 0xffffffff

GoogleGroups
1

I have some problem with dsp bridge
my step:

git clone git://dev.omapzoom.org/pub/scm/tidspbridge/kernel-dspbridge.git
// TI website

wget http://gitorious.org/vjaquez-beagleboard/marmita/blobs/raw/master/meta-marmita/linux/linux-omap-bridgedriver/defconfig
-O .config // beagle board website

make menuconfig // module dsp
bridge , I use default set

modprobe mailbox
modprobe bridgedriver base_img=/lib/dsp/baseimage.dof

./ping.out

terminal display
DSP device detected !!
DSPNode_Allocate failed: 0xffffffff

please tell me what's wrong ...thx

2

I have some problem with dsp bridge
my step:

git clone git://dev.omapzoom.org/pub/scm/tidspbridge/kernel-dspbridge.git
// TI website

wget http://gitorious.org/vjaquez-beagleboard/marmita/blobs/raw/master/meta-marmita/linux/linux-omap-bridgedriver/defconfig
-O .config // beagle board website

make menuconfig // module dsp
bridge , I use default set

modprobe mailbox
modprobe bridgedriver base_img=/lib/dsp/baseimage.dof

./ping.out

terminal display
DSP device detected !!
DSPNode_Allocate failed: 0xffffffff

please tell me what's wrong ...thx

Do you have stored the socket nodes in /lib/dsp ??

You need this one: pingdyn_3430.dll64P

Checkout http://elinux.org/BeagleBoard/DSP_Howto#ping_test

vmjl

3

I had try it
./dynreg.out -r pingdyn_3430.dll64P
the result still is
DSP device detected !!
DSPNode_Allocate failed: 0xffffffff

4

I had try it
./dynreg.out -r pingdyn_3430.dll64P
the result still is
DSP device detected !!
DSPNode_Allocate failed: 0xffffffff

I don't know the current state of the tidspbridge library since I
don't use it anymore. What I should recommend is to try with the
dsp-tools[1] or try to debug libtidspbridge[2] by your self.

1. http://elinux.org/BeagleBoard/dsp-tools
2. http://gitorious.org/vjaquez-beagleboard/libbridge

5

Hi

modprobe dspbridge

modprobe bridgedriver base_img=baseimage.dof

./cexec ddspbase_tiomap3430.dof64P

./cexec dynbase_tiomap3430.dof64P

./dynreg -r pingdyn_3430.dll64P

kindly check above procedure

saminath

2010/9/29 Victor Manuel Jáquez Leal <ceyusa@gmail.com>

6

modprobe dspbridge

This is usually done by udev.

modprobe bridgedriver base_img=baseimage.dof

This is correct, although it's easier to put this into
'/etc/modprobe.d/bridgedriver.conf':
options bridgedriver base_img=/lib/dsp/baseimage.dof

So you only need to do 'modprobe bridgedriver'. And also, I think udev
is also loading bridgedriver, so the above would make it work from the
boot.

./cexec ddspbase_tiomap3430.dof64P

This is reloading the baseimage... if you are going to do that, then do:
modprobe bridgedriver base_img=ddspbase_tiomap3430.dof64P

./cexec dynbase_tiomap3430.dof64P

Ditto.

./dynreg -r pingdyn_3430.dll64P

I believe if you use 'ddspbase_tiomap3430.dof64P' that's not
necessary. But as Victor said with dsp-tools it's much easier:
http://elinux.org/BeagleBoard/dsp-tools

7

Thank All

"cat /proc/interrupts"

I found I only had "28" & lacked "26"

"26" sometimes show up, but the probability is very less

once "26" show up , I can execute "ping" right