Forums - make tree V= hexagon_ReleaseG

2 posts / 0 new
Last post
make tree V= hexagon_ReleaseG
phalgunb
Join Date: 6 Oct 14
Posts: 18
Posted: Mon, 2014-10-13 05:07

i am new to this hexagon dsp ihave started with making downscaleBy2 algorihm in the exmples by he following command

make tree V=Hexagon_ReleaseG

making was successfull. but the output was not as was shown in the example document as shown below

QURT kernel started
QURT kernel init cache params
QURT root task started
QuRTOS heap init: start 1d029ec0 size 0x80000
space init ...
Init memory pools...
0 name LOADER_POOL pool 1e0ba678
        0 start 20000000 size 100000 hbits 0
1 name EBI1_pool pool 1e0ba750
        0 start 30000000 size 10000000 hbits 0
2 name DEFAULT_PHYSPOOL pool 1e0ba828
        0 start 1d000000 size 10000000 hbits 0
3 name DRIVER_POOL pool 1e0ba900
        0 start 90000000 size 40000000 hbits 0
4 name TCM_PHYSPOOL pool 1e0ba9d8
        0 start d8020000 size 20000 hbits 0
App Images Init
allocated kernel trace buffer at vaddr=f0000000 paddr=1e100000 with size 0x4000 bytes
QURT Timer IST started
QURT Timer Driver client started
QURT Timer service was initialized.

but instead i got something like this

making ../../test util

making ../../dspCV

making ../../rpcmem

making.

Done

To: insns:  Tcycles:

T1:insns:   T cycles:

T2: Insns    Tcycles:

 

total instructions

simulator speed 

ratio to real time

 

is it correct what ever i go or should i be expecting the same thing as was shown in the document.

 

 

  • Up0
  • Down0
mcastell
Join Date: 24 Apr 13
Posts: 11
Posted: Mon, 2014-10-13 11:19

You are correct, the document is not quite right for getting the full results to display.

Please try make tree V=hexagon_ReleaseG VERBOSE=1

We'll update the document.

  • 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.