Tuning command syntax - get_first_core / get_next_core

3 posts / 0 new

Last post

Mon, 03/20/2023
8:07am

Rodrigo

Top

Tuning command syntax - get_first_core / get_next_core

Hi,

We are trying to get the list of AWE instances from the target.

Our target contains multiple sharc DSPs, each with multiple cores.

The command "get_first_core" works fine to retrieve the information about the first core. However, when we follow up with "get_next_core", we don't get the expected answer.

The documentation on "Tuning command syntax" PDF is quite short. Could you give us some example how to retrieve information of all AWE instances from the target?

Ideally, we would like to have the name of the AWE instances running in the sharc cores, and any additional information available on them.

Mon, 03/20/2023
6:11pm

DSPC Michael

Top

Hi Rodrigo,

The get_core_list command returns the number of AWE instances and their IDs.

When you are using the get_next_core command, what answer are you expecting and what answer are you recieving?

Thanks,

Michael

Tue, 03/21/2023
4:14am

Rodrigo

Top

(Reply to #2) #3

Hi Michael,

We need to get the names of the cores and further information about them.
Therefore we are using the "get_first_core" and "get_next_core" commands.

The file "Audio-Weaver--Tuning-Command-Syntax.pdf" says that both commands should reply the following.

success,sampleRate,profileFreq,packetBufLen,nCores,nThreads,nInputs,nOutputs,baseBlockSize,packedInfo,ve rsion,CpuType,targetName,proxyName,CpuFreq,instanceID,isSMP,nInputPins,nOutputPins,featureBits

When running "get_first_core" the reply is successful and we can parse the targetName and instanceID from the answer.

However running "get_next_core,0" afterwards results in the following reply:

"failed,bad packet received"

But we are expecting a similar reply when running "get_first_core" as we have multiple Sharc DSPs connected.