How do I interpret the extra tracing data ?

Anonymous · ‎May 15, 2014

I noticed some extra data printed when using tracing on HCI UART. What is this data ?

It starts from: @$*#

Here is the example of the log from the boot-up time:

hello_sensor_create()53

E: Free bytes = 0x00005384S:0000

@$*#04FF9EF7009201130000074A05176A732000074E053169000000078206110001000007820604

0100000007820603100E000007820620000F000007820601201C000007A207000001000007A60700

0000000007D2070000000000071A080100000000078A08010000000007EE07000000000007A20800

00000000E5490B000000000007362A0100E80300073A2A500000000007522A500001000007021F01

hello_sensor_connection_up: 579610c35f9b 64

@$*#04FF3EF700920107000002FA240000000000078633000000000007E6200000000000078E1E00

00000000071E210300000000078E1E000000000007863300000000@$*#04FF0EF700920101008004

hello_sample, bond result 00

hello_sensor_timeout:35004521D0000000000074A1264000000

Also this data overwrites the other human readable lines.

asridharan · ‎May 15, 2014

With SDK 2.0.1, we implemented an encoded tracing mechanism in the ROM to reduce the ROM foot print and to make logging a bit faster. You cannot use a hyperterm like application any more because these traces are encoded. The SDK comes with its own trace parsing plugin that can decode these traces. Use the Trace -> Start Debug Traces menu item in Eclipse to capture traces on the same uart you used to download the application (or use Trace -> Setup COM Port menu to manually set it). Note that you have to Stop Debug Traces before you download the app again or the download will fail.

View solution in original post

How do I interpret the extra tracing data ?

How do I interpret the extra tracing data ?

Re: How do I interpret the extra tracing data ?