Forums - mini-dm on ubuntu 16

4 posts / 0 new
or Register
Last post
mini-dm on ubuntu 16
just4you
Profile picture
Join Date: 24 Jun 16
Location: south korea
Posts: 10
Posted: Mon, 2016-09-05 21:43
Top

I want to make the DSP application, so I need the method for debugging DSP.

However, I don't know what I shoul do.

 

I am a newbie of linux using the ubuntu 16 LTS natively.

There are anybody to explain in detail.

 

The following messages are displayed to execute the mini-dm on ubuntu.

 

mini-dm in the Hexagon 2.0 shows...

Device found with Product ID 0x903a. Continuing...
mini-dm is waiting for a DMSS connection...

 

mini-dm in the Hexagon 3.0 shows...

Running mini-dm version: 3.0
Device found with Product ID 0x903a. Continuing...
mini-dm is waiting for a DMSS connection...

  • Up0
  • Down0
Re: mini-dm on ubuntu 16
chenna
Join Date: 4 Feb 16
Posts: 54
Posted: Mon, 2016-09-05 23:17
Top

mini-dm displays diagnostic messages generated by the Hexagon DSP. You need to add FARF messages in your code 

Please go through Debugging_Message Logs.html in <SDK_ROOT>/docs for adding FARF messages

 

 

  • Up0
  • Down0
Re: mini-dm on ubuntu 16
just4you
Profile picture
Join Date: 24 Jun 16
Location: south korea
Posts: 10
Posted: Tue, 2016-09-06 02:14
Top

I am using the third party's custom board. so I think it makes some troubles.

 

I'd received a snapdragon flight kit today.

The mini-dm would be connected fine, but the code on the dsp was broken.

 

Then, I wonder that the mini-dm's working configuration.

What server application and configuration is needed on the snapdragon board?

  • Up0
  • Down0
Re: mini-dm on ubuntu 16
chenna
Join Date: 4 Feb 16
Posts: 54
Posted: Tue, 2016-09-06 04:33
Top

Ror requirements to run minidm please go through minidm documentation Hexagon_SDK/3.0/docs/Debugging_Message Logs.html 

For debugging your dsp code you need to add FARF messages in your code. 

 

 

 

 

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.