To Next Page

To Previous Page

LOGGING OPTIONS

Application Logging Support

68 E355/E265 USER AND BEST PRACTICES GUIDE

• Wi-Fi control panel logs are enabled using configuration variable VXWIFILOG

and filters using VXWIFIFIL.

• Network control panel logs are enabled using configuration variable

VXNCPLOG and filters specified using VXNCPFIL.

• BT_MGR application logs are enabled using configuration variable

BTMGRLOG=C, and value N disables this application logs.

Application

Logging Support

• Application level software can use standard dbprintf() API for adding data

to the system log.

• Additional OS log library is available for applications to write logs to RAM

memory in a circular buffer of size 1MB.

• RAM memory logging is faster when compared to FLASH (file based) memory

logging, and it avoids any read disturbance issues in memory.

• RAM memory logs are erased after e355 restart/power cycle.

• RAM logs are enabled either by using configuration variable *APPLOG=1 or by

sending control command G31 with parameter 01.

• RAM logs are disabled either by using configuration variable *APPLOG=0 or

by sending control command G31 with parameter 00.

• RAM logs are retrieved using control command G32 or *DEBUG or *LOG.

• Applications can integrate OS log library by linking logprintf.a library at

compile time.

• OS log library provides the following APIs for logging to RAM memory:

• int logprintf (log_severity severity, const char *fmt ..)

• void logdump(log_severity severity, char *tag, void *addr,

int len)

VeriFone e355 User Manual

Other manuals for VeriFone e355