Hello,

 

Are you using loadmodules.sh for inserting the dsplinkk.ko? There is a
FAQ for this failure at

http://wiki.davincidsp.com/index.php?title=DVEVM_and_DVSDK_frequently_as
ked_questions

 

There is another FAQ for rebuilding LINK at
http://wiki.davincidsp.com/index.php?title=Changing_the_DVEVM_memory_map

 

I think rebuilding Link with the default configuration (both GPP and DSP
sources) and inserting the correct module without any parameters will
resolve your issue.

 

Chris: Can you comment further on this issue?

 

Regards,

Deepali

________________________________

From: ketan deshpande [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 04, 2007 3:21 PM
To: Uppal, Deepali; Linux DaVinci; Subashini Ravindran; Ring, Chris
Cc: Kamoolkar, Mugdha
Subject: Re: DSPLINK PROC_Start failure

 

Hello Deepali,

Tried to go through all the suggestions that you mentioned and here is
what we have

*       DSP has not been loaded correctly, and hence is not executing
correctly to reach the point where the driver completes the handshake
between GPP and DSP for PROC_Start. 

 

How do we make sure of that? Bcoz...the PROC_Load() passes successfully
and it gives error on PROC_Start(). It also says error value to be
0x800080008 which is DSP_EFAIL(A general failure occurred). What
actually General Failure mean in this case? Unrecognised state?

*       There is a memory configuration mismatch in memory regions
between the GPP and DSP, resulting in the GPP looking for handshake at
one location, and the DSP looking at another location. 

    Have you made memory address changes in
$DSPLINK/config/all/CFG_Davinci.TXT? If so please check:

        *       Are the memory address changes present both in gpp side
configuration $DSPLINK/config/all/CFG_DAVINCI>TXT as well as dsp side
platform tci file
$DSPLINK/dsp/inc/DspBios/Davinci/dsplink-davinci-base.tci 
        *       No memory segment is overlapping i.e. you can sum the
base address and size of each memory segment to ensure that no memory
segment is overlapping 
        *       Is the POOL size configured to be a subset of the memory
entry from which it is configured? i.e. the size is less than the size
of the DSPLINKMEM entry 


Verified. Memory maps in both the cases match. 
We are basically using the examples given by TI without any code change.
Just the compilation and run it.

*       User has not reserved the required amount of memory from Linux
kernel space. 

        *       Check Linux kernel space of Davinci platform i.e. check
mem boot parameter value. Has the mem boot parameter correctly
configured?


In bootargs we specify 'mem=120M' Is that correct?

*       Have you got Dsplink source base from a CE release? If so, there
is a known issue where the samples require SW3-4 be set to "ON"
position. The SW3-4 switch controls whether the ARM boots the DSP or the
DSP 'self boots'.  Setting this switch to "1" says that the DSP should
'self boot'. When the DSP self boots, the samples would work as PSC and
GEM are both enabled but when ARM boots the DSP i.e. ARM has to do the
power management of DSP, the samples would not work. Please check if the
samples work when you set SW3-4 to ON. If they work, you can check the
DOPOWERCTRL flag in $DSPLINK/config/all/CFG_Davinci.TXT. If it is FALSE,
make it TRUE, rebuild. The samples will work for both host boot and self
boot mode.


Thats correct. We are using the DSPLink_1_30 from CE release. But when
we try to put SW3-4 to ON position we just get BOOTME. Seems strange but
i think it was mentioned sometime back on Spectrum Digital website that
this kind of behavious can be expected if DSP is in SELF BOOT mode. Also
setting the DOPOWERCTRL  to TRUE did not help our cause. 

But the examples that we got from
dsplink/package/ti/dsplink/gpp/Linux/Davinci/DEBUG  and
dsplink/package/ti/dsplink/dsp/DspBios/Davinci/DEBUG seem to be working
fine. 

We have tried some other examples like loopgpp also and we get the
similar kind of behavior.

For confirmation we are mentioning the process to be used for
compilation of the sources. Plz let us know if we are doing something
wrong.

for compilation we go to the directory 
    dsplink/gpp/src/samples/message
    make 

Then the executable would be made in 
    dsplink/gpp/export/BIN/Linux/Davinci/DEBUG

from there take GPP executable similar procedure for DSP Side and then
run them together. Is that right?

regards,
-Ketan


Send free SMS to your Friends on Mobile from your Yahoo! Messenger.
Download Now! http://messenger.yahoo.com/download.php

_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to