Hi Dave,
> When I run "hcidump -R", I see (among other output) lines like these,
>
>> 04 3E 26 02 01 03 01 69 57 93 F1 99 F8 1A 02 01 04 09 09 39
> 36 37 35 39 39 38 46 07 16 09 18 EB 03 00 FE 04 16 0F 18 3E
> A5
>
> But trying every available option for "btmon", I can't find anything
> remotely similar. How can I get this information using "btmon"? Or can
> I -- does "btmon" show this type of information? Is there some other
> command that would be more appropriate?
>
> I understand that "hcidump" has been deprecated for several years. Yet
> the output of "btmon" seems to imply that it is calling "hcidump". That
> doesn't make sense to me. For example,
>
> @ RAW Open: hcidump (privileged) version 2.22 {0x0002} [hci0] 1.894682
> @ RAW Open: hcidump (privileged) version 2.22 {0x0003} 1.894702
> @ RAW Close: hcidump {0x0003} 1.894708
> @ RAW Close: hcidump {0x0002} [hci0] 1.894718
I don’t know what that is, but it seems that something else in your system is calling hcidump binary. However it is for sure not btmon calling the hcidump binary and you can verify that in the btmon source code.
The hcidump -R functionality is rather useless. If you really want it, then you can get it by opening the monitor socket directly. I really don’t know what you wanted it for.
Regards
Marcel
