Introduction to Remote Call Profiler (Windows CE 5.0)
To use Remote Call Profiler, you must do the following:
- Compile code that contains profiling hooks.
- Download the compiled code to a target device.
- Connect Remote Call Profiler to the target device.
You can profile OS and application code. If the code is part of an application, you must then run the application on the target device.
You can instrument your code for profiling by using the compiler that ships with your product.
If you wrote your code with Microsoft® eMbedded Visual C++® 4.0 or later, you can download your compiled code to a target device with eMbedded Visual C++.
If your application is a Platform Builder project, the executable file for your application is placed in the release directory when you build it.
When you connect Remote Call Profiler to the target device, your application downloads automatically.
For applications created with a tool other than eMbedded Visual C++ or Platform Builder, use Remote File Viewer to copy the files to your target device.
As an alternative, if you use Platform Builder, you can also copy the files manually to your release directory. For more information about copying files manually to your release directory, see Downloading and Launching an Instrumented Module.
Before you run your application on the target device, you must connect Remote Call Profiler to your target device. To connect Remote Call Profiler to a target device, you must first connect to the target device with Platform Manager. For more information about connecting to a target device with Platform Manager, see Application Connectivity.
To run your application on the target device, run the application in the Remote Call Profiler window.
As an alternative, you can run the application in eMbedded Visual C++ by pressing the F5 key or in Platform Builder by choosing Run Programs from the Target menu.
See Also
Remote Call Profiler Quick Start
Send Feedback on this topic to the authors