WL glogger

From Texas Instruments Wiki
Jump to: navigation, search

Introduction

gLogger is now the official logger for WiLink 6/7/8 and BT Firmware.

Setup

Installation

  • This tool should be included with the WL release.
  • Windows 7/8 users must run the installer as administrator
  • IMPORTANT: Do not change the target installation path. The installation path must be "C:\Program Files\Texas Instruments"
  • An new Icon will be created under Start->Programs as well as the Desktop

Configuring the logger for UART mode

  • Go to Options->Settings
  • Click the "glogger" button if it is not already selected.
  • Set the "COM Port" to correct value. On Blaze devices the UART logger COM port is usually the last COM port created.
  • To modify the baudrate simply change the "COM Port" field from "COM7" to "COM7:3000000"
    • WL127x/WL128x: Baud rate is 921600
    • WL18xx: Baud rate is 3000000
  • Set the "Main Bin File" to the firmware bin file that is running the target device. The bin file selected MUST BE IDENTICAL to the bin file running on the target device. The bin file contains all debug, strings, asserts, and other information that the logger requires in order to parse the logs correctly.
  • "Log Size" by default is set to 25Mb. This parameter configures the max size of a log file. Once the max limit is reached a new log file will be created.
  • "adb/ip" field is irrelevant for UART mode.


Configuring the logger for SDIO mode

  • Go to Options->Settings
  • Set the "COM Port" to "SDIO"
  • If you're working with an Android device, set the "adb/ip" field to the full path where adb.exe is located (e.g. "C:\ADB\adb.exe")
  • If you're working on a QNX/Linux device, set the "adb/ip" field to the IP number of the device (and make sure your PC can connect to this IP)

Configuring Colors and Highlights

  • Go to Options->Highlights and Triggers...
  • You can add strings or regular expressions that if matched will be highlighted or colored.
  • New items are always added to the end of the list and have the lowest priority. To increase priority move the selected field up.


Usage

  • On WinXP simply run the logger, on Win7/8 run the logger as administrator.
  • The logger UI is nothing more than a CSV tail application. The process that connects to the target device is gserver.exe.
  • To start the logger, press the Play icon.
  • To Stop the logger, press the Stop icon.
  • To view old logs click on the "Open Logs Directory" icon.
  • To load and parse a binary log file click on the "Open Raw Log", first select the binary log file path and then select the bin file path.
  • To clear the window while the logger is connected to the device press "ctrl-n"


Useful Features

  • To bring up the search tab, press F4. You can search for strings or regular expressions on the open log file.
  • To open old logs, go to the logs directory, select a log file and drag it on-top of the logger UI. A new tab will open with the relevant log.
  • To bring up the bookmarks tab, press F6. Bookmarks can be created manually by pressing ctrl-f2, or automatically by setting a rule under Options->Highlights and Triggers...


Android scripts

Go to **/data/misc/wifi** - All the scripts are located here

  • __Continuous mode__ - This mode outputs FW traces over SDIO through wl_fwlog_service and to the logger application
- Unload the driver by running **rmmod wl12xx** (for R5) or **rmmod wlcore** (for R8)
- Load the driver by running **insmod /system/lib/modules/wl12xx.ko fwlog=continuous** (for R5) or **insmod /system/lib/modules/wlcore.ko fwlog=continuous** (for R8)
- Add the following line to **/data/misc/wifi/testing-boot.sh**
R5:
**mkdir /data/misc/wifi/fwlogs**
**/system/bin/wl_logproxy 1555 /sys/devices/platform/omap/omap_hsmmc.4/mmc_host/mmc2/mmc2:0001/mmc2:0001:2/wl12xx/fwlog /data/misc/wifi/fwlogs/ 10000000 &**
R8:
**mkdir /data/misc/wifi/fwlogs**
**/system/bin/wl_logproxy 1555 /sys/devices/platform/omap/omap_hsmmc.4/mmc_host/mmc2/mmc2:0001/mmc2:0001:2/wl18xx/fwlog /data/misc/wifi/fwlogs/ 10000000 &**
- Reboot the device. testing-boot.sh will be executed by init.rc from now on.
- All logs will be stored in /data/misc/wifi/fwlogs/
  • __On-demand mode__ - This mode only outputs FW traces upon recovery
- Same as continuous mode, but change the insmod command parameter to **fwlog=ondemand**
  • __UART mode__ - This mode only outputs FW traces through UART (Serial Port)
- Unload the driver by running **rmmod wl12xx** (for R5) or **rmmod wlcore** (for R8)
- Load the driver by running **insmod /system/lib/modules/wl12xx.ko fwlog=dbgpins** (for R5) or **insmod /system/lib/modules/wlcore.ko fwlog=dbgpins** (for R8)

Release Notes

IMPORTANT: - Windows 7: All versions prior to 1.1 must be installed in "\program Files\Texas Instruments" instead of the default path "\program Files (x86)\Texas Instruments" - All FW versions prior to the R5.1 release will require the legacy logger (version 0.x). These versions can be found under the legacy directory. - Old XP based computers may require MS runtime to be installed. The installer is located in the root directory under MS_Runtime.exe

Latest release: 2.0

Version 2.0

Version 1.9 - Fix multiple bin files and file reload bug

Version 1.8 - Support multiple bin files (up to 3)

Version 1.7 - SDIO bug fixes

Version 1.6 - wl8 support - Minor bug fixes

Version 1.5 - Bug fixes in SDIO mode

Version 1.2 - Fixed SDIO bugs - Added offline file parsing support

Version 1.1 - SDIO continuous mode fully supported (fixed many bugs) - TSF added to all traces - Added option to change max file size (default is now 50mb instead of 25mb) - For SDIO mode, added textbox to set the path to adb.exe - Windows 7 install works by default

Version 1.0 - New protocol added to align with the original legacy protocols - SDIO mode support added for both on-demand and continuous modes