• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 16 subscribers
  • Views 345 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.

SmartRF packet sniffer bug?

James14409
Prodigy 100 points

Hello,

I am using the SmartRF packet sniffer to observe the generic packets sent by a CC1110EM. When I use fixed-length packets, i.e., PKTCTRL0 = 0x44, the packet sniffer is still trying to read the 1st byte after sync word as length byte and parse the packet accordingly, which resulted in errors.

My understanding is that in the case of fixed-length packet, the 1st byte after sync word belongs to payload and we should be able to use it for other purposes than length byte. Do I understand it correctly? Can anyone confirm this bug?

Thanks!

  • 0
    TI__Genius 13620 points

    You are correct. This is a known limitation in the packet sniffer (firmware). The capture device will always assume that the first byte in the packet is the length field, regardless of the register settings. As a consequence, the packet sniffer will not be able to display the fixed length packets correctly.

  • 0 in reply to M
    Prodigy 100 points

    Thank you for confirming this. Hopefully TI will fix this bug in the next release of the packet sniffer.

    Jim