 |
|
Check the progress of a TRACE32 command
|
| Ref: 0458 |
|
 |
Is it possible to check the progress of the execution of a TRACE32 command through the Remote API?
|
| |
|
There is no function in the Remote API that can check the progress of the execution of a TRACE32 command. You can however call the command within a PRACTICE script and check the execution state of the script using T32_GetPracticeState().
|
|
|
Long execution time of LINE_Receive
|
| Ref: 0457 |
|
|
The execution time of the Remote API LINE_Receive() function is too long. What is the purpose of
this function. Is it possible to reduce the execution time?
|
| |
|
LINE_Receive() is the essential function within the API, used by every function that communicates with TRACE32 PowerView. LINE_Transmit() sends the request to TRACE32, while LINE_Receive() receives the answer. A long time can be caused by several reasons. In most cases, the time is simply the execution time of the command - e.g. if the command within T32_Cmd() takes a lot of time you will end up having this time in LINE_Receive(), too. Very high computing load of the PC running TRACE32 PowerView, or network time if client and TRACE32 PowerView are not running on the same PC could also be the reason of such delays.
|
|
|
T32API for C# (C-Sharp)
|
| Ref: 0308 |
|
|
Where do I get the TRACE32 Remote API for C# (C-Sharp)?
|
| |
|
For 'Managed C++', 'VB.NET' and 'C#' (C-Sharp), please use the .NET API wrapper from your Lauterbach DVD folder
/files/demo/api/dotnet.
(Source code is also included.)
|
