• State Verified Answer
  • Replies 1 reply
  • Subscribers 74 subscribers
  • Views 896 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 230061
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Cannot get PCA10040 to appear in Wireshark interface list

jsheaney

I've been struggling with this for quite a while now. I've got a PCA10040 to spare that I am trying to use with nrf sniffer in Wireshark. I'm using a new iMac with the latest MacOS, 1014.4. After much effort, I think I have accomplished the following:

The sniffer_pca10040_1c2a221.hex file is installed on the board and LED 1 is flashing madly.

The nrf_sniffer python support is installed in the extcap folder in the application package, which gives me the nRF Sniffer toolbar.

I have the Wireshark profile installed, which give me the Profile_nRF_Sniffer_v2_001 profile in the Wireshark UI, which I can select.

I just don't see the device showing up in the interfaces list, so I can't start a capture.

I'm looking for any kind of checklist that I can run through to see if any configuration is missing or wrong. Yes, I've followed the document best I can and I did find that I overlooked things that I have since corrected. I've also seen all of the threads about similar issues. Unfortunately, many of them are oriented around Windows. Any help would is greatly appreciated.

One thing to note is that this particular board did not have a softdevice installed on it because I was using it for driver development. I assume that the hex file installed takes the place of a softdevice because the first step is to erase flash. I would be happy to be wrong about that.

Thanks.

Parents
  • +1

    OK, the obvious purpose of these boards is public humiliation. I realized this morning that I had cut the solder bridges from the application processor to the UART because I had dedicated this board to driver development and my main interaction with it was connect directly to the UART pins with a terminal application. I reconnected the solder bridges and it is working now.

    It isn't actually stated anywhere that I have seen, but the serial implementation used in this interface is the UART on the processor via the application processor. You can certainly infer that after just a little thought (maybe about 12 hours for some of us), but I'll just state it explicitly for anyone having the same problem. You need solder bridges 22-25 intact. Otherwise, the interface simply won't show up and there won't be any indication why.

Reply
  • +1

    OK, the obvious purpose of these boards is public humiliation. I realized this morning that I had cut the solder bridges from the application processor to the UART because I had dedicated this board to driver development and my main interaction with it was connect directly to the UART pins with a terminal application. I reconnected the solder bridges and it is working now.

    It isn't actually stated anywhere that I have seen, but the serial implementation used in this interface is the UART on the processor via the application processor. You can certainly infer that after just a little thought (maybe about 12 hours for some of us), but I'll just state it explicitly for anyone having the same problem. You need solder bridges 22-25 intact. Otherwise, the interface simply won't show up and there won't be any indication why.

Children
No Data
Related
Terms of service