From 46760c2cac5076bab038c63a64e56b4708e1fc65 Mon Sep 17 00:00:00 2001 From: Matthias Ringwald Date: Thu, 14 May 2015 17:06:55 +0200 Subject: [PATCH] emphasize hci_dump_open calls --- docs/manual/markdown/docs/how_to.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/manual/markdown/docs/how_to.md b/docs/manual/markdown/docs/how_to.md index 916f66830..8542490a7 100644 --- a/docs/manual/markdown/docs/how_to.md +++ b/docs/manual/markdown/docs/how_to.md @@ -294,12 +294,12 @@ For this, BTstack provides a configurable packet logging mechanism via hci_dump. // formats: HCI_DUMP_BLUEZ, HCI_DUMP_PACKETLOGGER, HCI_DUMP_STDOUT void hci_dump_open(const char *filename, hci_dump_format_t format); -On POSIX systems, you can call hci_dump_open with a path and HCI_DUMP_BLUEZ -or HCI_DUMP_PACKETLOGGER in the setup, i.e., before entering the run loop. +On POSIX systems, you can call *hci_dump_open* with a path and *HCI_DUMP_BLUEZ* +or *HCI_DUMP_PACKETLOGGER* in the setup, i.e., before entering the run loop. The resulting file can be analyzed with Wireshark or the Apple's PacketLogger tool. -On embedded systems without a file system, you still can call hci_dump_open(NULL, HCI_DUMP_STDOUT). +On embedded systems without a file system, you still can call *hci_dump_open(NULL, HCI_DUMP_STDOUT)*. It will log all HCI packets to the consolve via printf. If you capture the console output, incl. your own debug messages, you can use the create_packet_log.py tool in the tools folder to convert a text output into a