Zephyr and OpenThread join support

[Louis]

While attempting to join a network formed by the OpenThread border router reference implementation and an external commissioner using the Android app, my zephyr end device (based on the lwm2m client sample) ends up failing an assertion:

assertion "awaited_property == AWAITED_PROPERTY_NONE" failed: file "WEST_TOPDIR/zephyr/modules/hal_nordic/nrf_802154/serialization/platform/nrf_802154_spinel_response_notifier.c", line 63, function: nrf_802154_spinel_response_notifier_lock_before_request

I'm not sure I'm doing this properly. CONFIG_OPENTHREAD_CUSTOM_PARAMETERS has to be set in order to be able to link the binary which I think is a little suspicious and not documented as far as I know:

CONFIG_OPENTHREAD_JOINER=y
CONFIG_OPENTHREAD_CUSTOM_PARAMETERS="OPENTHREAD_CONFIG_JOINER_ENABLE=1"
CONFIG_OPENTHREAD_JOINER_AUTOSTART=y
CONFIG_OPENTHREAD_JOINER_PSKD="J01NU5"
CONFIG_MBEDTLS_HEAP_SIZE=10240

[Carl Richard]

Hello, Louis!

Are you using Zephyr standalone or the nRF Connect SDK, based on Zephyr? In the latter we provide a OpenThread configuration guide and samples that should be more straightforward to setup with our devices. 

I will ask the developers about the issue you're seeing here.

Best regards,
Carl Richard

[Louis]

Thanks,

I'm using the nRF SDK. I tried to add join support to the cli sample. Configuring the application with OPENTHREAD_JOINER_AUTOSTART didin't do anything (no failed assertion but no join either). So I added a "join button" (project here) and ended up with the same failed assertion.

[Carl Richard]

That's unfortunate. Did you try with the pull request I mentioned as well? 

ZEPHYR_BASE is supposed to point to <ncs_install_folder>/zephyr. The nrf folder is located at <ncs_install_folder>/nrf. I believe is used the wrong path in my earlier instructions. Apologies for that!

Best regards,
Carl Richard

[Louis]

No problem. Yes, I pulled everything uptream including <ncs_install_folder>/nrf.

[Carl Richard]

Ok! Thanks.

Could you get me the current commit hash of nrfxlib? Enter <ncs_install_folder>/nrfxlib and call

git rev-parse HEAD

Best regards,
Carl Richard

[Louis]

It was 11fb8c5e5ecdd25c1e15efbd94b07dea14b621db. I pulled nrfxlib again (now c9cf6f74c618581794cda73063f93e77123dadbc) but the assertion still fails.

[Carl Richard]

Just want to clarify here; the recommended way to update the nRF Connect SDK is to pull the newest sdk-nrf (nothing else) and then do west update. Manually pulling other repos could result undefined behavior or the SDK not working at all.

Can you confirm that you follow the recommended procedure?

Best regards,
Carl Richard

[Louis]

Hi Carl,

I rebuild my dev environment and only pulled nrfxlib before performing a "west update". I confirm that the pull request you mentioned made it to ZEPHYR_BASE. I also added : 

CONFIG_NRF_RTC_TIMER_USER_CHAN_COUNT=2

to cli sample with added join support. Unfortunately, still the same result.

Louis

[Carl Richard]

Hi again!

Please try to pull in nrf, not nrfxlib and then do the west update. 

Best regards,
Carl Richard

[Louis]

still the same result after:

# cd nrf
# git pull origin master
# cd ../nrfxlib
# git pull ncs master
# cd ..
# west update
# cd nrf
# git rev-parse HEAD
75db44dec9af4f52861759b05bcb3b309bcf3544
# cd ../nrfxlib/
# git rev-parse HEAD
5c6944ecf908d050da93d8755c3441a35ebdfa98

[Louis]

Same result with the container implementation.