Error Locating DSP Server's MSGQ 'rmsq' after 100,000 retries

Eric Peterson54900

Other Parts Discussed in Thread: OMAP3530

Hello,

I am trying to port a custom codec to the gumstix OMAP3530 from Davinci. I first attempted running one of the examples called video_copy on the gumstix and it worked just fine. However, when I attempt to run my custom codec, I get several errors. I have already worked through some memory map errors, but I can't quite seem to get around the following error:

Error: could not locate DSP server's MSGQ 'rmsq' in 100000 retries. Check if you have the correct DSP image, or increase the number of retries (see ti.sdo.ce.osal.Global's commLocateRetries config param.

The original number of retries was 20, and I increased it to 100,000; but the error persists. According to the error, I must have an incorrect DSP image. I do not know what this means, nor how to resolve it. Could you offer any advice on where I should proceed from here? Thanks.

Eric

Some extra information:

Kernel Version: Linux overo 2.6.32

I have also attached a debug trace to this post

over 15 years ago

0 Eric Peterson54900 over 15 years ago

Prodigy 50 points

Eric Peterson said:

Some extra information:

Kernel Version: Linux overo 2.6.32

I have also attached a debug trace to this post

Hello,

Another useful piece of information I just found was the message on the gumstix console when I ran the command "dmesg" is:

DSP MMU Error Fault! MMU_IRQSTATUS = [0x1]. Virtual DSP addr reference that generated the interrupt = [0x49038020].

This error message appears to give me the virtual DSP memory address that generated the interrupt. I don't know what an MMU_IRQSTATUS of 0x1 means, but at least I know it has to do with the MMU. I hope this additional piece of information facilitates an answer to my above question. Thanks.

Eric

0 Eric Peterson54900 over 15 years ago in reply to Eric Peterson54900

Prodigy 50 points

Hello,

My colleague and I decided to take a step back to solve this problem. We started with one of the codec examples, and began replacing, file by file, the TI files with our custom files. Doing this substitution, along with adjusting *_INSTALL_DIR's and compiler options, we were able to get it running on the OMAP3530.

So, the moral of the story is:

If you have a custom codec, start with an example codec that works, and then slowly merge your code in.

Thanks.

Eric

0 Deepali Uppal over 15 years ago in reply to Eric Peterson54900

TI__Expert 4930 points

A couple of link which might provide more info:

http://processors.wiki.ti.com/index.php/DSP_MMU_Faults

http://processors.wiki.ti.com/index.php/OMAP3_DSP_MMU_Configuration

Deepali

Capture this thread to a wiki.

-->

Processors

Processors forum

Error Locating DSP Server's MSGQ 'rmsq' after 100,000 retries