Thread NCP SPI pin configuration

[jebentancour]

I can not find where to change the default pins to connect the nrf52840 to the rpi over SPI.

The default pins are

SPI pin     Raspberry Pi pin     nRF52833, nRF52840 or nRF52811 pin
MOSI     pin 19 (GPIO10)     P0.04
MISO     pin 21 (GPIO09)     P0.28
SCK     pin 23 (GPIO11)     P0.03
CSN     pin 26 (GPIO07)     P0.29
INT     pin 40 (GPIO21)     P0.30

In the infocenter sais "The SPI pins on the Development Kit (nRF52833, nRF52840 or nRF52811) can be configured when building the example. " but i can not find where are they configured.

Please help

[Jørgen Holmefjord]

Hi,

This statement is not entirely accurate. The SPI/UART pins are set in the platform-config.h file in OpenThread, as described on this page. Changing this config requires you to rebuild the OpenThread libraries.

Best regards,
Jørgen

[jebentancour]

Ok, now i am having trouble to build the libraries

C:\Users\User\Documents\nRF5_SDK_for_Thread_and_Zigbee_v4.0.0\external\openthread\project>py build_gcc_libs.py
Compiling file: cli.cpp
make: se ingresa al directorio `C:/Users/User/Documents/nRF5_SDK_for_Thread_and_Zigbee_v4.0.0/external/openthread/project/nrf52840/openthread_cli/ftd/armgcc'
"'C:" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
make: *** [_build/libopenthread_cli_ftd_nrf52840/cli.cpp.o] Error 1
make: se sale del directorio `C:/Users/User/Documents/nRF5_SDK_for_Thread_and_Zigbee_v4.0.0/external/openthread/project/nrf52840/openthread_cli/ftd/armgcc'
Traceback (most recent call last):
  File "build_gcc_libs.py", line 28, in <module>
    subprocess.run(make_cmd, check=True)
  File "C:\Users\User\AppData\Local\Programs\Python\Python38\lib\subprocess.py", line 512, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['make', '-C', 'nrf52840\\openthread_cli/ftd\\armgcc']' returned non-zero exit status 2.

[Jørgen Holmefjord]

Did you checkout the correct commit after cloning the OpenThread repository? If you try to build master, the project files in the SDK may not include all the required paths and source files.

The commit used by the SDK is indicated in the project readme-file: external\openthread\project\readme.txt

[jebentancour]

I checked the commit version and still have the same problem

[Jørgen Holmefjord]

I'm not speaking Spanish, but from what I can see from Google translate it looks like an issue with the paths. Can you try to move the SDK closer to the root of the drive? I have sometimes seen issues when the paths get too long.