mtd not getting commissioned in NRF sdk for thread an zigbee version 4.0.0

[Bhumika]

I have recently upgraded my working stack based on nrf sdk for thread and zigbee v2.0.0 to nrf sdk for thread and zigbee v4.0.0

But since then my mtd's are not getting commissioned on network.

Please suggest what's the possible reason for that.

[Jørgen Holmefjord]

Hi,

How do you commission the devices in the network? Do you get any errors?

Have these nodes been in the network previously with the application based on Thread and Zigbee SDK v2.0.0? Did you run an "erase all" operation on the board when updating?

You are able to commission FTD devices with the same approach?

Best regards,
Jørgen

[Bhumika]

Yes I am trying to commission them in the network.

yes these nodes have been previously in the network with application based on v2.0.0

Before updating, I have run nrfjprog --eraseall on device.

I haven't tried on FTD devices yet.

[Jørgen Holmefjord]

Can you describe or post a link to the process you use for commissioning the devices? Is the commissioner also updated to SDK v4.0.0, or is that running on SDK v2.0.0?

[Bhumika]

I am starting the commissioner at border router side having NCP updated to SDK v4.0.0, using following wpantund commands..

sudo wpanctl commissioner start

sudo wpanctl commissioner joiner-add "*" 180 J01NMYNET

Also previous mtd version based on v2.0.0 getting commissioned on latest NCP.

I am first checking the state of mtd using

otDatasetIsCommissioned,

and if it returns false then starts the joiner in mtd using otJoinerStart

 

[Bhumika]

do you suggest any other method for commissioning the device ?

[Bhumika]

Do you have update on this?

I am still stuck in the issue.

However I am able to commission CLI example in the network.