Other Parts Discussed in Thread: CC2652P7, LP-CC1352P7, CC1352P7,
Good day, we have developed software for 2x LP-CC2652R7.
The 1st LP-CC2652R7 establishes the thread network:
> ifconfig up
> thread start
> commissioner start
> commissioner joiner add <eui64> <pskd>
The 2nd LP-CC2652R7 is commissioned onto the thread network:
> eui64 xxxxx
> pskd xxxxx
> Successfully joined the network.
Now the above setup works successfully, but now we have an issue detailed below.
We are planning to use a commercially available module based on the CC2652P7.
However, the RF design of the module seems to be based on the LP-CC1352P7.
When we run the code of the second LP-CC2652R7 on this module (CC2652P7),
the module goes to a halt and even stops working when calling:
OtStack_joinConfiguredNetwork() -> which calls otIp6SetEnabled() and TIOP_configuredJoinerStart()
Essentially, the module does not communicate with the thread network and hence no on-boarding can be initiated.
We checked communication using the smart RF studio7, and the transmission and reception of the module works.
The bidirectional communication was tested using the cli_ftd code on both module and launchpad.
What could be the issue here, and may possible solutions exist?
Kind regards,
Logan Becker
