openthread Coap Client and Coap Server Example

RE: openthread Coap Client and Coap Server Example

hugzy123 — Fri, 09 Dec 2022 15:29:24 GMT

That fixed my issue, our custom board only has an internal LF clock and I forgot you need to tell the SD to use it. The client example on our custom board can now control the led on the server.

Thank you for your help.

"Doesn't the log that you attached come from UART on your custom board?"

I was using the dev kit for the serial so had access to UART and on the client I was using RTT logs.

RE: openthread Coap Client and Coap Server Example

Edvin — Fri, 09 Dec 2022 13:53:56 GMT

Does your custom board have an external 32KHz XTAL? If not, can you please try to add this line to your prj.conf:

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

[quote user="hugzy123"]Do you know why these uart pins are needed if the there is no console for the "sleep end device" version? [/quote]

I am not sure about this. Not my area of expertise. I suggest you create a separate ticket with this question. Doesn't the log that you attached come from UART on your custom board?

RE: openthread Coap Client and Coap Server Example

hugzy123 — Fri, 09 Dec 2022 13:31:24 GMT

Thanks for your quick reply. After seeing it ran ok on your machine I decided to uninstall and reinstall the nrf connect sdk and it works ok on the development kits.

However, I'm still having issues when trying to run the client on my custom board and the server on a development kit.

My custom board pcb contains an raytac mdbt50Q module and some other hardware, I have tested it with another application firmware that uses Bluetooth and it works correctly.

I am using the "overlay-logging.conf" to run the application as a "sleepy end device". Again this works ok on the development kits but not on the custom board/

I've attached a .txt file of the server logs with additional logging enableddevzone.nordicsemi.com/.../coap_5F00_server_5F00_custom.log

On line 78 you can see a log for "Child timeout expired", this line doesn't appear in the logs of the server on the development kit (I can attach these too if needed)

I've also included a screenshot of the RTT logs from the client running on the custom board below (again I can include the non custom board if needed too)

When I run the same example on the development kit the example runs attached ok, confirmed by typing ot childip and responding with the child's ip.

Below I've included my dts file for the custom board (I've had to change the extension to .txt so the upload would work)

devzone.nordicsemi.com/.../custom_5F00_board.txt

One thing i wanted to ask was; i've had to add uart pins so the firmware will compile even though my board doesn't have uart. Do you know why these uart pins are needed if the there is no console for the "sleep end device" version?

RE: openthread Coap Client and Coap Server Example

Edvin — Fri, 09 Dec 2022 09:37:59 GMT

That looks strange. I tried the unmodified samples just now, using NCS v2.1.2, and this was my result:

using the "ot state" command also verifies that they have the roles that they claim during the startup. I started by erasing the flash (nrfjprog -e) before programming the samples, so no network data was stored before programming these boards.

[quote user=""]However, if I run the CoAP CLI example first and go through the Thread network initiation commands (ot channel, PANID, etc.), and then flash the CoAP client/server examples, it will work okay. [/quote]

That is probably because the network data is not deleted when you reprogram the board (because it uses a different region of the flash). But you should not need to run the CLI sample first to store the network data.

Can you try to erase the flash, program the client/server samples, and run these commands on both boards:

ot state
ot panid
ot extpanid
ot networkkey
ot channel
ot psck

Do they report the same values on all of them?

Best regards,

Edvin