OT-Daemon kills itself while the commissioning process

[Hardik Prajapati]

Hello OT Team,

I am working on the custom product where Openthread would be used. I am facing the issue while commissioning the other device to join the network.

The environment setup:

- A custom product that has CC2538 connected on UART and RCP binary(without any change) is flashed on the CC2538.

- A nRF52840 DK is flashed with a simple client binary to act as an end device

Problem:

- I have started and run the ot-daemon on CC2538, created it as a Leader using ot-ctl binary.

- I need to connect the nRD52840 to the leader to act as an end device. So commissioned the nRF52840 to allow it to join the thread network.

- Sometimes, it will be able to join the network, and sometimes, it shows the error while in the commissioning process.

Error 1: This comes while applying the commissioning commands to join the other devices to the network.

ot-daemon: /home/openthread/src/posix/../../src/posix/platform/udp.cpp:271: otError otPlatUdpBind(otUdpSocket*): Assertion `aUdpSocket->mHandle != nullptr' failed.
line 1: 1897 Aborted ./ot-daemon 'spinel+hdlc+uart:///dev/ttyS1?uart-baudrate=115200'
[1]+ Exit 134

Error 2: This comes once the device is joined to the network and at a random time it disconnects as following.

[1]+ Exit 6         ./ot-daemon 'spinel+hdlc+uart:///dev/ttyS1?uart-baudrate=115200'

These two errors are random, can anyone please help me to find out what could be the issue. 

Thanks in advance,

Hardik

[Edvin]

Having no knowledge about the CC2538 or their ot-daemon, it looks like you are struggling with opening the COM port. I think you need to contact Texas Instruments for this issue, as it doesn't seem to be related to the Nordic Semiconductor chip? If I am mistaken, then I must misunderstand your question.

BR,

Edvin

[Hardik Prajapati]

Hi Edvin,

It seems that it is more related to the Openthread and binary created for CC2538 from the Openthread source itself. I better ask to Openthread platform.

Regards,

Hardik