RE: nrfThread Eddystone example problems (SDK4 Thread)

jpablodt — Mon, 24 Feb 2020 18:14:04 GMT

Well, that did the trick... I modified the path removing spaces and dots but did not think of shortening it significantly.
Thanks for the quick update!

RE: nrfThread Eddystone example problems (SDK4 Thread)

Vidar Berg — Mon, 24 Feb 2020 14:26:54 GMT

Hello,

This example should be supported by SES as far as I can tell. I was able to run it on my 52833 DK without making any changes at least. So, I'm wondering if it might be related to path lengths. I have encountered a few cases where the source and include paths become too long even on Windows 10 (was far more common with W7). Could you try to shorten the paths by moving the SDK directory closer to the root of your hard drive?

The 'ble_thread_dyn_coap_srv_eddystone' debug log I got here :

<info> app_timer: RTC: initialized.
<info> app: Thread version   : OPENTHREAD/20180926-01143-g8a1992e2; NRF52833; Dec 10 2019 22:38:51
<info> app: Network name     : OpenThread
<info> app: Thread interface has been enabled.
<info> app: 802.15.4 Channel : 11
<info> app: 802.15.4 PAN ID  : 0xABCD
<info> app: Radio mode       : rx-on-when-idle
<info> app: BLE Thread dynamic CoAP server eddystone example started.
<info> app: State changed! Flags: 0x011FD33D Current role: 1

<info> app: State changed! Flags: 0x00000040 Current role: 1

<info> app: State changed! Flags: 0x008012A5 Current role: 4

Thanks,

Vidar