Resources | developer.brewmp.com Resources | developer.brewmp.com

Developer

resources

DebugBot Help

DebugBot is a command-line tool you can use to set up the debugging environment for Brew Validation Kit (BVK) or Platform Validation Suite (PVS) test modules. DebugBot loads test modules, test frameworks, and other necessary modules or files to the device. DebugBot then creates the Microsoft Visual Studio project solution, allowing you to rebuild and conduct source-level debugging in the test module from the Visual Studio IDE.

Note: Before using DebugBot, confirm that Strawberry Perl 5.10 is installed, not Active State Perl.

DebugBot supports applet-based:

  • OAT modules
  • CTF modules
  • UITF modules
  • CTF Applet modules

To use DebugBot, install:

  • Microsoft Visual Studio (versions 2005, 2008, and 2010 are supported)
  • Brew MP Visual Studio Plugin (launch the SDK Manager to install)

Note: You must run the command window and MS Visual Studio as Administrator.

DebugBot uses the test module to create an MS Visual Studio project, starts a debug session, and then does the following:

  1. Loads the required test framework to the target.
  2. Creates a MS Visual Studio Solution for the test module.
  3. Launches the MS Visual Studio solution.
You then use MS Visual Studio to debug the module. See the Tools Reference for information on debugging Brew MP modules.

DebugBot is included in the Brew MP SDK 7.11.2 Toolsets and higher. DebugBot.exe is located in the C:\Program Files\Qualcomm\Brew MP SDK\Toolset \bin directory.

DebugBot arguments

The command-line for DebugBot is in the following form:

DebugBot -=

When invoking DebugBot, the following arguments are required:

Required argument Description
-module=

Specifies the name of the test module to debug. This can be any test module that exists in the BVK or in the PVS suite. For example:

 -module=RingerMgr_SetRingerAITest 

-target=

Specifies the name of the target (either a simulated or a physical target) to use for the debugging module to debug.

Tip: You can change the physical target name to a more user-friendly name. See Device Settings in Target Manager Help.)

You must specify the full name of the target. Use double quotes (") if there are spaces in the target name. For example:

-target="Candy Bar QCIF (1.0.4.468 PRO)" 

-ide=

Specifies the IDE to use for the MS Visual Studio solution. The following IDE names are supported:

  • VS2005
  • VS2008
  • VS2010

For example:

-ide=VS2010 

The following additional arguments are optional:

Optional argument Description
-workspace=

Specifies the name of the Results Manager workspace. If this argument is specified, DebugBot uses the Platform Pro and BVK versions from this workspace. For example:

-workspace="Candy Bar Validation Workspace" 

-platformpro=

Specifies the version of the Platform Pro kit to be used for working with PVS modules. This argument is ignored when the -workspace argument is specified. If neither -workspace nor this argument are specified, DebugBot uses the Platform Pro that is currently set as default in SDK Manager. For example:

 -platformpro="1.0.3.984" 

-bvk=

Specifies the version of the BVK to be used for working with BVK modules. This argument is ignored when the -workspace argument is specified. If neither -workspace nor this argument are specified, DebugBot uses the BVK that is currently set as default in SDK Manager. For example:

-bvk="2.0.11.12.2094342" 

-kit=

Specifies from which kit to pull the module's source. Valid options are bvk or pvs. If a kit is not specified, DebugBot uses the first module it encounters that matches the -module parameter.

-defer

If this option is specified, DebugBot will not automatically launch the IDE after creating the solution.

-verbose, -v

Enables verbose output.

-noload

If this option is specified, DebugBot skips the step of automatically loading the required test frameworks to the device.

-script=