• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 55 subscribers
  • Views 546 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2531: Troubles running two at the same time

A Z
Prodigy 10 points
Part Number: CC2531
Other Parts Discussed in Thread: , PACKET-SNIFFER

Hello everyone. 

It is not my habit to be posting on forums but I've been stuck on the problem for days.

I have two CC2531EMK dongles that I am using for Zigbee testing. Both are flashed with sniffer_fw_cc2531.hex firmware (successfully as they work just fine alone) using cc-debgger,

My trouble is that while both dongles are recognized by pc:
└─$ lsusb
Bus 002 Device 036: ID 0451:16ae Texas Instruments, Inc. CC2531 Dongle
Bus 002 Device 034: ID 0451:16ae Texas Instruments, Inc. CC2531 Dongle

└─$ lsmod | grep cdc_acm

cdc_acm 45056 0
usbcore 344064 7 usbserial,ohci_hcd,ehci_pci,usbhid,cdc_acm,ehci_hcd,ohci_pci

Premissions dialout to user are set.

None of them is listed in /dev/tty* as ACM0 or ACM1 - I had to add those manually.

I am trying to run different tools where without specifying any device, they run just fine, but don't run at all if I try to specify device as /dev/ttyACM0 as they are not found.

I tried flashing one CC2531 dongle with another firmware (to try to differentiate them) but the ONLY successful firmware is the one listed above (be from public sources or from here - doesn't matter).

I am quite new to zigbee and similar but I'd greatly appreciate any support as I've been stuck here for awhile, emptied all of my resources that I found.

Both dongles are plugged in and work, tried switching ports and what not.

Example of running tool:
└─$ sudo zbwireshark -c 20

zbwireshark: listening on 'CC2531 USB Dongle', channel 20, page 0 (2450.0 MHz), link-type DLT_IEEE802_15_4, capture size 127 bytes
Wireshark exited (0)
8 packets captured

Example of specifying device:
└─$ sudo zbwireshark -c 20 -i /dev/ttyACM0
[redacted]Serial issue in kbutils.isgoodfetccspi: [Errno 6] could not open port /dev/ttyACM0: [Errno 6] No such device or address: '/dev/ttyACM0'.

It'd not be a tool problem as I troubleshooted with multiple other tools, scripts etc..

I greatly appreciate any help.

  • 0
    TI__Guru**** 218207 points

    Hello A Z,

    Here is a link to the Zigbee Packet Sniffing Solutions E2E post and Packet Sniffer documentation.  There is also a guide on the Zigbee2MQTT documentation.  You should install PACKET-SNIFFER as it will contain the correct CDC drivers for the CC2531EMK USB.  Once installed properly, check ls /dev before and after connecting the USB dongle to verify the correct port connection.  I have not, however, tried using two of these devices simultaneously.  What is the purpose for using both at the same time?

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 10 points

    Packet sniffer is installed on my win10 host and I can use CC without any troubles. 

    I currently don't need Z2MQTT for my purposes, it's not a testing environment that would allow anything else beside sniffing and managing devices. 

    The official drivers in Packet sniffer cannot be used for anything but sniffing, which doesn't help my cause but that works flawlessly.

    The purpose of using them both at the same time is so one can sniff traffic and display it in wireshark and the other is sending beacon signals to my gateway.

    I actually went around this problem, as there seems to be no other solution, to just clone one of my hosts and run both at the same time while one dongle is on one and the other on another - this seems to work so far for what I need. Not ideal but definitely much better than what I had before.

    I will however further investigate the /dev as you instructed but so far what I need at the time works.

    Thank you very much for your time and help Ryan, appreciate it.

  • 0 in reply to A Z
    Prodigy 10 points

    So I tested the said solution above, Ryan, to see if device shows in /dev and it doesn't. But as said in my first message, it is flashed with sniffer_fw_cc2531.hex which is the file that was received from PACKET-SNIFFER, as you stated in reply, so this should do. The sniffing can be conducted but tool chooses device by default, it cannot be specified as /dev/ttyACM0 as it is not there.