# Other differences: AG 4040C to CG 6060C

Other software differences between the AG 4040C and the CG 6060C boards include:

Software component | AG 4040C board | CG 6060C board
Board location utility (UNIX) | Use blocate to associate the PCI bus assignment to a physical board by flashing an LED on the board. To flash the LED on a board, call blocate with the PCI bus and PCI slot locations. | Use cg6ktool to associate the PCI bus assignment to the physical board by flashing an LED on the board. Usage: cg6ktool -B -lbus:slot
Board location utility (Windows) | Use pciscan to associate the PCI bus assignment to the physical board by flashing an LED on the board. To flash the LED on a board, call pciscan with the PCI bus and PCI slot locations. | Same as the AG board.
Boot log | The OAM API appends booting information and tracing to agpierror.log. | The OAM API logs boot-specific information to CG_6060Cboot_<bus>_<slot>.txt. The file is overwritten each time the board is booted. Use oammon to capture operational error and tracing messages.
OAM plug-in | The OAM plug-in for AG boards is agplugin.bpi. Keyword default values are built-in. | The OAM plug-in for CG boards is cg6kpi.bpi. Keyword default values are in cg6k.dft.