Hi,
When sniffing trace from wireshark with PCA10040 board, sniffer just stop when i bond central with peripheral.
When i break connection, advertisement packet are back. I use the last version of sniffer.hex.
What can be wrong ?
Hi,
When sniffing trace from wireshark with PCA10040 board, sniffer just stop when i bond central with peripheral.
When i break connection, advertisement packet are back. I use the last version of sniffer.hex.
What can be wrong ?
Make sure you choose the device to track from the drop down menu in Wireshark. Also, I suggest to disable mass storage class, as this will increase the throughput of the serial port: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/tools/nordic_segger.html?highlight=msddisable#disabling-the-mass-storage-device-functionality
Thanks for your answer, but disabling mass storage don't do anything on my issue...
And, for sure i choose the right device on the dop down menu.
Thanks for your answer, but disabling mass storage don't do anything on my issue...
And, for sure i choose the right device on the dop down menu.
I guess you sometimes can loose the connection request packet due to interference, so maybe try to move the two peers closer together, if you never receive the connection request packet, then I recommend to double check you are using the latest nRF Sniffer and the software versions listed in the release notes for nRF Sniffer.
Kenneth
I, i've double check hardware and firmware, same issue happens.
Hardware: PCA10040 2.1.0 2021.3
Firmware: sniffer_nrf52dk_nrf52832_4.1.0
I try to reverse engineer BLE exchanges with a chinese thermal printer (MHT-P8009), do you think the problem comes from the device ?
Noon said:I try to reverse engineer BLE exchanges with a chinese thermal printer (MHT-P8009), do you think the problem comes from the device ?
I recommend that you first try to connect with a phone for instance for comparison, if it works for intance with phone, but fails with printer, then it is likely there is something with the printer that make the sniffer miss the packet. It is mainly tested with nRF implementations, so it could be that it's something with the connection request packet from the printer that is slightly out of spec.
Kenneth
Yes, everything works well except with this specific device. I suspect BLE is out of spec.
Thanks for support.