Hayes Microcomputer Products Mwave manual Debugging Tips, Error Logs, Tracing

Page 12

4. Debugging Tips

4.1. Error Logs

Errors encountered by the ACP Modem device driver or application are logged using the syslog utility.

4.2. Tracing

The ACP device driver supports a debug argument to enable the generation of trace information. The command for this debug is listed below. You can also access several of the variables listed below in the mwaved script.

insmod mwave mwave_debug=0x0f

Where the following debug trace information is selectable:

0x01 ACP Modem Device driver entry points

0x02 Systems Management API(SMAPI)

0x04 Hardware Interface (3780I)

0x08 Thinkpad Interface (tp3780i)

Trace information is logged using the syslog utility.

The ACP application supports tracing through the use of flags configured in the [STARTUP] section of the mwavem.conf file.

Mwave Manager API trace points:

MANAGER_API_TRACE=1

MANAGER_API_DATA_TRACE=1

MANAGER_CORE_TRACE=1

MANAGER_SPECIFIC_TRACE=1

MEIO Manager trace points:

MEIO_API_TRACE=1

MEIO_CORE_TRACE=1

MEIO_SPECIFIC_TRACE=1

Mwave Modem application trace points:

MWMLW32_TRACE=1

4. Debugging Tips

10

Image 12
Contents Linux ACP Modem Mwave mini−HOWTO Paul SchroederTable of Contents General Information and Hardware Requirements IntroductionCredits Copyright Notice and DisclaimerFeatures of the Modem Which Systems are SupportedCompilation, Installation, and Startup Building and Installing SourceSetting Things Up PrerequisitesRuntime Loading the ACP device driverRunning ACP Modem Application Dev/modem Resolving Installation and Configuration Problems DSP Does Not StartResource Conflicts Not Connecting at Specified Starting Speed Dialer Application Cannot Detect Serial PortPPP Errors Using 2.4.0 Version of the Kernel Error Logs Debugging TipsTracing Trace information is logged using the syslog utility Test Claims List of Supported Countries Country Name Access Code List of Supported CountriesElsalvador Philippines Poland Portugal Trademarks