• 

  Andrei Tanasache

  • 1 month ago
  • Zigbee & Thread
  • Zigbee & Thread forum

  CC2531: Development Link Down

  TI Thinks Resolved

  Part Number: CC2531 Hello there, I am starting to look into development procedure with CC2531 and observed on this sticky page that the links for Step 3 Begin software development are down. I am not able to access them. Connection timeout...
• 

  Howjie zhou

  • 24 days ago
  • Zigbee & Thread
  • Zigbee & Thread forum

  About CC2531 reception test

  Hi,All, Currently, RF engineers test the receiving sensitivity of CC2531 through RF instruments: CC2531 is in packetRx state in SmartRf Studio, The RF instrument sends ten 127-byte data packets quickly (about 5ms), and SmartRf Studio shows that...
• 

  hobieboy

  • 5 months ago
  • Zigbee & Thread
  • Zigbee & Thread forum

  CC2531: CC2531

  • Resolved

  Part Number: CC2531 Hi, Does anyone know what does status codes 0x10 and 0x1a coming from CC2531
• 

  vincent hartman

  • 5 months ago
  • Zigbee & Thread
  • Zigbee & Thread forum

  CC2531:

  Part Number: CC2531 Good day, I had exactly that problem. My USB powered target as well as the CC Debugger were connected to my PC Window laptop via a USB hub. As soon as I plugged both into the laptop native usb ports the issue went away.
• 

  Sohan B

  • 3 months ago
  • Zigbee & Thread
  • Zigbee & Thread forum

  CC2531 as end device

  TI Thinks Resolved

  Hello everyone, I have two CC2531 dongles. A CC2531 coordinator connected to a Raspberry Pi A CC2531 router connected to a Raspberry car. I successfully paired both of them, but I would like to send messages from the coordinator to the router...
• 

  Ryan Brown1

  • 3 months ago
  • Zigbee & Thread
  • Zigbee & Thread forum

  RE: CC2531: Invalid profile ID 0xffff in outgoing message

  You've set the Options byte in your AF_DATA_REQUEST to AF_WILDCARD_PROFILEID (0x02), this causes outgoing packets to use ZDO_WILDCARD_PROFILE_ID (0xFFFF) as the Profile ID regardless of what's been registered. Regards, Ryan
• 

  Peter Drozda

  • 3 months ago
  • Zigbee & Thread
  • Zigbee & Thread forum

  RE: CC2531: ZStack 1.2 - Compile end device for CC2531

  Hi Ryan, Thanks for hints but I found more general approach. Indeed HAL was guilty. To fix the issue I had to change the path to inludes from: ...components/hal/target/2530EB to ...components/hal/target/2530USB Also add all subdirectories...
• 

  Mark Morgan Lloyd

  • 7 months ago
  • Zigbee & Thread
  • Zigbee & Thread forum

  CC2531: CC2531

  • Resolved

  Part Number: CC2531 I've been tinkering with some CC25xx chips, using SDCC and a download utility
• 

  takenari

  • 5 months ago
  • Zigbee & Thread
  • Zigbee & Thread forum

  CC2531: Variation in reception time

  • Resolved

  Part Number: CC2531 The receiver which is 2 to 1 transmitter, reception receives the same packet
• 

  Peter Hoyer

  • 10 days ago
  • Zigbee & Thread
  • Zigbee & Thread forum

  CC2531: Z-Stack Linux server: MAX_SUPPORTED_ENDPOINTS applied at boot?

  • Resolved

  Part Number: CC2531 Just a quick question: is MAX_SUPPORTED_ENDPOINTS from config.ini applied each

Didn't find what you are looking for? Post a new question.

• Ask a new question