• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 57 subscribers
  • Views 1197 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: Z-Stack 3.0.2 Firmware issues

Martin Korejtko
Prodigy 10 points

Part Number: CC2531
Other Parts Discussed in Thread: Z-STACK

Hi,

we are using for our client Z-Stack 3.0.2 like source of firmware.

Can you help us with these questions?

  1. If we are writing firmware "\Projects\zstack\ZNP\CC253x\bin\CC2531SB.hex” to dongle, the dongle is not communicating. If we are writing "\Projects\zstack\ZNP\CC253x\dev\CC2531ZNP-with-SBL.hex”, the dongle is communicating. Why only the dev version is working? Do you know what is wrong? For writing we are using debugger SmartRF04EB.
  2. At first time if we are connecting end device to the ZigBee network, everything is ok, but after dongle restart, the dongle has not this device like a neighbor. Is it a bug or we are making something wrong?
  3. We have trouble with pairing. Some devices are connecting fine, but some devices random. We allow pairing and after that, we are waiting for DEVICE ANNOUNCE EVENT. Is it normal?
  4. We founded byte 0xEF and we are using them, if dongle does not respond to our restart command. Is it correct using? Do we have to send it in some other cases?

  • 0
    Guru 735705 points

    1. CC2531SB.hex contains boot loader only so it doesn’t work as ZNP.

    2. Couldn’t understand your question. Please elaborate.

    3. Do you use sniffer to check what happens over the air.

    4. Couldn’t understand your question. Please elaborate.

  • 0
    TI__Guru**** 223787 points

    Hi Martin,

    1. Refer to YK's response and review the Serial Boot Loader document.
    2. Are you referring to a reset of the ZNP as a coordinator?  Are there other routing devices available that the end devices could join?  Is NV_RESTORE and NV_INIT enabled?
    3. Waiting for a Device Announce is a logical path, but as YK mentioned a sniffer log would help debug this as well as question 2.  Are there different devices connecting or is the same firmware always involved?
    4.   Send a SYSTEM_PING to check if the dongle is responsive, otherwise further evaluate the Z-Stack Monitor and Test API.  It is possible to create a custom MT command but this would require changes to the ZNP firmware.

    Regards,
    Ryan

  • 0
    Prodigy 20 points

    @

    1. thank you for your answer
    2. Device connects to the network but once we restart the dongle, no other devices has it as its neighbour. Is that feature or a bug?
    3. We have problem with pairing process, some devices connect without any problems, but some devices dont connect at all, or it takes them quite long time.
      We allow pairing and we wait for DEVICE ANNOUNCE EVENT. Is that the right way, or are we doing something wrong?
    4. We found a 0xEF byte, which we use if the dongle isnt responding after a reset. Is that correct usage? Do we have to send the byte in any other cases?
    No we are not using any sniffers
  • 0 in reply to user6193606
    Guru 735705 points

    2. How do you judge no other devices has it as its neighbour?

    3. I need your Sniffer log to judge what happens.

    4. As Ryan has relied, you can send a SYSTEM_PING to check if the dongle is responsive.