# Debugging resource management

There are several ways to debug the resource management strings defined in CG boards. This topic describes:

- Using CG board debug masks

- Resource management board errors

- Debugging resource management with cgtrace

## Using CG board debug masks

Each CG board keyword file includes a DebugMask keyword. When this keyword value is set, it turns on global flags in the system. These flags display status information about different board components whenever the board is booted. After the board has been booted, run cgtrace to obtain a list of global and local debug masks and a brief description of the types of information they provide. For more information, refer to cgtrace - Performing CG board debugging.

Note: To view debug information, you must be running the OAM API utility oammon. For more information about using oammon, refer to the Dialogic® NaturalAccess™ OAM System Developer’s Manual.

If you encounter DSP resource management problems when booting a CG board, set the DebugMask keyword value to 0x08. This setting configures the board so that it displays all of the resources available for each DSP. In some circumstances, it also displays the calculated resource usage based on the resource management keywords specified in the board keyword file.

## Resource management board errors

If an application tries to use the allocated DSP resources in a way not specified in the board's DSP resource management configuration, the board returns an error. Use the OAM utility oammon to monitor these errors.

Some possible debug errors include the following error messages:

Error message | Problem | Solution
--- | --- | ---
Board Error 0xe40: Resource Manager: Insufficient resources. In this case, the total resource usage for the board is displayed. | The board can allocate resources for only a portion of the ports you require, because the resource consumption exceeds available DSP resources. | Adjust the number (or type) of DPFs that can execute simultaneously on each port so that the board supports the required number of ports, or decrease the number of ports used.
Board Error 0xa0e: Function 0x001A0000 not found on any engine. In this case, the calculated resource is not displayed. | A DSP has not been loaded with all the DPMs specified in the Resource[x].Definitions or Resource[x].TCPs keyword strings. | The error provides the DPF's family and function ID in hexadecimal form (in the example error, this is 0x001A0000). Make sure a DPM has been loaded for each DPF specified in the resource definition string.

For more information about CG board errors, refer to the Dialogic® NaturalAccess™ Board and Driver Error Reference. For more information about the hexadecimal IDs associated with DPMs and DPFs, refer to f41info - Displaying DPF file resource usage.

## Debugging resource management with cgtrace

cgtrace is an interactive debugging tool that enables you to debug CG board output. Once the CG board is booted, use cgtrace to evaluate CG board DSP resource management on a per-port and per-DSP basis.

Refer to cgtrace - Performing CG board debugging for more information.