Thread NCP SPI pin configuration

RE: Thread NCP SPI pin configuration

jebentancour — Mon, 23 Mar 2020 20:21:16 GMT

Binary file /usr/sbin/MQTT-SNGateway matches <- This is the problem

The MQTT-SN gateway uses GPIO 23, 24 and 25:

/*==========================================================
* Light Indicators
===========================================================*/
#define MAX_GPIO 27 // GPIO02 - GPIO27
#define LIGHT_INDICATOR_GREEN 23 // RPi connector 16
#define LIGHT_INDICATOR_RED 24 // RPi connector 18
#define LIGHT_INDICATOR_BLUE 25 // RPi connector 22

RE: Thread NCP SPI pin configuration

jebentancour — Thu, 19 Mar 2020 13:40:50 GMT

It seems that the pin I want to use is already in use:

pi@raspberrypi:/sys/class/gpio $ ls
export gpio19 gpio23 gpio25 gpio6 gpiochip100 unexport
gpio13 gpio21 gpio24 gpio26 gpiochip0 gpiochip504

The NFC shield does not uses GPIO24 (pin 18):

My schematic:

I am going to try in a fresh Raspbian install, but it would be nice to know who is using those pins on the BR image.

RE: Thread NCP SPI pin configuration

Jørgen Holmefjord — Thu, 19 Mar 2020 11:24:52 GMT

I figured that you need also to set the SPI_INT_GPIO_PIN in wpantund init config script found in /etc/init.d/wpantund for the GPIO to be initialized correctly. Did you modify this as well, or only the /etc/wpantund.conf file? I tested with GPIO20, and this seems to work correctly. Note that some GPIOs may collide with the NFC shield used by the MeshCop example for commissioning. From the schematics of the shield, it can look like GPIO25 is used for switching between SPI and I2C mode.

gpio25 is also listed in /sys/class/gpio, which may indicate that it is used by another module. I can't find any references to this the BR image, but a grep tells me that it found a match for "/sys/class/gpio/export" inside a few binary files:

pi@raspberrypi:~ $ grep -r "/sys/class/gpio/export" / 2> /dev/null
Binary file /proc/11933/task/11933/cmdline matches
Binary file /proc/11933/cmdline matches
/etc/init.d/wpantund:        echo "$SPI_INT_GPIO_PIN" > /sys/class/gpio/export
Binary file /usr/sbin/nfccommissiond matches
Binary file /usr/sbin/MQTT-SNGateway matches
Binary file /usr/sbin/MQTT-SNLogmonitor matches
Binary file /usr/lib/python2.7/dist-packages/RPi/_GPIO.arm-linux-gnueabihf.so matches

RE: Thread NCP SPI pin configuration

jebentancour — Tue, 17 Mar 2020 17:37:47 GMT

I tried a few different GPIOs and it only works on GPIO 21

RE: Thread NCP SPI pin configuration

Jørgen Holmefjord — Tue, 17 Mar 2020 16:00:09 GMT

Unfortunately, I do not have any suggestions on what could be wrong on the Raspberry Pi. It looks like you have changed the wpantund.conf file correctly. Do any other GPIOs work, or do only GPIO 21 work?

RE: Thread NCP SPI pin configuration

jebentancour — Tue, 17 Mar 2020 14:58:48 GMT

I tried the things you suggested and find out that the problem is in the INT pin configuration from the Raspberry GPIO side.

I was using GPIO 24 but when leave the default GPIO 21 the NCP started to work.

Do you have any idea what the problem could be? I would like to use GPIO 24

RE: Thread NCP SPI pin configuration

Jørgen Holmefjord — Tue, 17 Mar 2020 13:03:46 GMT

Which pins are you using for the SPI interface?
Are you using a DK or a custom board?
Have you tested the NCP with SPI transport with a DK and the precompiled examples?

RE: Thread NCP SPI pin configuration

jebentancour — Tue, 17 Mar 2020 12:55:36 GMT

I was able to compile the libraries:

- I move the SDK closer to the root of the drive
- I move the compiler binaries closer to the root of the drive
- Remove the quotes for the # Toolchain commands in the file Makefile.common

Compiled the example successfully but the NCP crashes a few seconds after being running.

pi@raspberrypi:~ $ sudo wpantund
wpantund[2439]: Starting wpantund 0.08.00d (Dec 13 2019 21:37:34) . . .
wpantund[2439]: Configuration file "/etc/wpantund.conf" read.
wpantund[2440]: About to exec "/usr/bin/spi-hdlc-adapter -i /sys/class/gpio/gpio24 /dev/spidev0.1"
spi-hdlc-adapter[2440]: spi-hdlc-adapter 0.07 (21:37:34 Dec 13 2019)
wpantund[2439]: Ready. Using DBUS bus ":1.63"
wpantund[2439]: Running as root without dropping privileges!
wpantund[2439]: State change: "uninitialized" -> "offline"
wpantund[2439]: NCP is running "OPENTHREAD/20180926-01143-g8a1992e2; NRF52840; Mar 16 2020 17:35:06"
wpantund[2439]: Driver is running "0.08.00d (; Dec 13 2019 21:37:34)"
wpantund[2439]: Network is not joinable
wpantund[2439]: State change: "offline" -> "offline:commissioned"
wpantund[2439]: [-NCP-]: SLAAC enabled
wpantund[2439]: Finished initializing NCP
wpantund[2439]: AutoResume is enabled. Trying to resume.
wpantund[2439]: NCP is commissioned. Resuming...
wpantund[2439]: State change: "offline:commissioned" -> "associating"
wpantund[2439]: State change: "associating" -> "associated"
wpantund[2439]: Node type change: "unknown" -> "leader"
wpantund[2439]: Adding on-mesh prefix "fd11:22::/64" to NCP
wpantund[2439]: SpinelNCPTask.cpp:86: Requirement Failed (IS_EVENT_FROM_NCP(event) && GetInstance(this)->mInboundHeader == mLastHeader)
wpantund[2439]: SpinelNCPTaskSendCommand.cpp:323: Requirement Failed ((mRetVal == kWPANTUNDStatus_Ok) || (mRetVal == kWPANTUNDStatus_Busy))
wpantund[2439]: SendCommand task encountered an error: 7 (0x00000007)
wpantund[2439]: SpinelNCPTask.cpp:86: Requirement Failed (IS_EVENT_FROM_NCP(event) && GetInstance(this)->mInboundHeader == mLastHeader)
wpantund[2439]: SpinelNCPTaskSendCommand.cpp:381: Check Failed (error 7)
wpantund[2439]: Error Timeout (7) while performing "adding on-mesh prefix" on NCP - Resetting NCP.

Caught SIGHUP!

RE: Thread NCP SPI pin configuration

Jørgen Holmefjord — Mon, 16 Mar 2020 15:46:19 GMT

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.

RE: Thread NCP SPI pin configuration

jebentancour — Wed, 11 Mar 2020 15:49:50 GMT

I checked the commit version and still have the same problem

RE: Thread NCP SPI pin configuration

Jørgen Holmefjord — Wed, 11 Mar 2020 08:20:12 GMT

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

RE: Thread NCP SPI pin configuration

jebentancour — Tue, 10 Mar 2020 22:20:32 GMT

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.

RE: Thread NCP SPI pin configuration

Jørgen Holmefjord — Tue, 10 Mar 2020 13:54:35 GMT

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