Failing to update OpenThread binaries in SEGGER

[purvisb]

I'm trying to follow these instructions to update the openthread binaries in nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8.

I have a Windows host machine and a Ubuntu VM.

 I attempted to follow the "Building the library with GCC on Linux or Mac (recommended)" section and build the libraries on a VM, then move them to the windows guest machine, where SES and the SDK are located. I got stuck on step 7 of that section. The `/external/project/openthread/examples/platforms/nrf528xx/src` directory does not exist for me. I'm assuming that directory is starting in the installation directory of the sdk.

I also attempted to follow the "Building the library with GCC on Windows" section to build the libraries on windows. On step 2 of that section I get this error 

Traceback (most recent call last):
  File "C:\Users\Brandon\Desktop\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\external\openthread\project\build_gcc_libs.py", line 28, in <module>
    subprocess.run(make_cmd, check=True)
  File "C:\Users\Brandon\AppData\Local\Programs\Python\Python39\lib\subprocess.py", line 505, in run
    with Popen(*popenargs, **kwargs) as process:
  File "C:\Users\Brandon\AppData\Local\Programs\Python\Python39\lib\subprocess.py", line 951, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "C:\Users\Brandon\AppData\Local\Programs\Python\Python39\lib\subprocess.py", line 1420, in _execute_child
    hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified

[Charlie]

Hi Purvis,

1) This is as expected. The OpenThread repository is under active development, when the document was written the folder structure may like this, but now the files are restructured. I find the mentioned files are now actually located at "openthread\examples\platforms\nrf528xx\src".

2) This is caused by a similar issue. You are using latest pyhon39, which is not been tested with an older building environment.

As you have experienced, there are more and more incompatibilities appearing with nRF5 SDK based solutions. As mentioned on Thread - nordicsemi.com, the nRF5 SDK will have no further update. I strongly suggest you switch to the nRF Connect SDK platform for your new development.

Best regards,

Charlie