• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 55 subscribers
  • Views 485 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.

Z-STACK-HOME 1.2 permit join rsp problem

dpintaric
Prodigy 210 points

Other Parts Discussed in Thread: Z-STACK, CC2530

Hi,

I have been using Zstack 2.5.1a up untill now and wanted to switch to Z-Stack Home 1.2. The problem is that with Z-Stack Home 1.2 I never get ZDO_MGMT_PERMIT_JOIN_RSP to my ZDO_MGMT_PERMIT_JOIN_REQ command.

I have compiled the stack with -DMT_ZDO_MGMT,-DMT_ZDO_FUNC and -DMT_ZDO_CB_FUNC and also wrote 0x1 (true) to ZCD_NV_ZDO_DIRECT_CB.

Any idea why this is happening with Zstack Home 1.2 and it works normally with Zstack 2.5.1a.

P.S

I'm using CC2530.

  • 0
    Prodigy 210 points

    Maybe I'm looking this the wrong way...i don't get the ZDO_MGMT_PERMIT_JOIN_RSP because the ZDO_MGMT_PERMIT_JOIN_REQ is never carried out. When I send ZDO_MGMT_PERMIT_JOIN_REQ via uart i get the SRSP back but on my sniffer I see no permitJoin command.

    So what could cause ZDO_MGMT_PERMIT_JOIN_REQ to fail?

  • 0 in reply to dpintaric
    Prodigy 240 points

    Hi,

    It sounds like you're using the ZNP, in which case you will find the format of the MT MGMT Permit Join Req command has been changed in the latest release. The format of the new command is different and it wasn't implemented in a backwards compatible way, breaking old hosts. This one got me too...

    Mark

  • 0 in reply to MarkV
    Prodigy 210 points

    At some point I saw that they changed the format and that they added the extra byte for AddrMode and I did added this extra byte BUT I did not change the length of the package form 0x4 to 0x5 :))

    Anyway your post made me recheck my code and yes it works now so thank you for that!

    To bad they did not implemented backward compatibility now i'm going to have to check the firmware version first and then send the appropriate frame. Ahhh....