Problems on nrf52840 coap server to receive packages

RE: Problems on nrf52840 coap server to receive packages

Jørgen Holmefjord — Thu, 17 Dec 2020 15:36:50 GMT

Yes, logs from OpenThread are set to OT_LOG_LEVEL_CRIT by default. If you want to increase this level, you can do that as described in the link I provided above. Then you need to rebuild the OpenThread libraries.

RE: Problems on nrf52840 coap server to receive packages

taoyinzhou — Thu, 17 Dec 2020 06:16:50 GMT

I tried to set the Log level to 4 as you said, and then checked with debug in SEGGER Embedded Studio, but I only saw the print Added by myself, without any other log.

RE: Problems on nrf52840 coap server to receive packages

Jørgen Holmefjord — Wed, 09 Dec 2020 15:45:05 GMT

I believe that logging should be enabled by default in this example, over RTT. You can use J-Link RTT Viewer to see the logs.

You can increase the log-level output from application by setting this config to Debug/4 in your sdk_config.h file:

// <o> NRF_LOG_DEFAULT_LEVEL  - Default Severity level
 
// <0=> Off 
// <1=> Error 
// <2=> Warning 
// <3=> Info 
// <4=> Debug 

#ifndef NRF_LOG_DEFAULT_LEVEL
#define NRF_LOG_DEFAULT_LEVEL 4
#endif

For more details about logging from OpenThread stack, see OpenThread logging.

RE: Problems on nrf52840 coap server to receive packages

taoyinzhou — Mon, 07 Dec 2020 05:47:56 GMT

coap_default_handler() or other coap handle have no received any events when the message is received.

Where do I add the print log?

RE: Problems on nrf52840 coap server to receive packages

Jørgen Holmefjord — Thu, 03 Dec 2020 15:54:02 GMT

Do you have any log outputs from your application?

Are you receiving any events in coap_default_handler() (or some other CoAP handler) when the message is received?

RE: Problems on nrf52840 coap server to receive packages

taoyinzhou — Tue, 24 Nov 2020 06:26:08 GMT

I've tried it, but it still doesn't work.

RE: Problems on nrf52840 coap server to receive packages

Jørgen Holmefjord — Tue, 17 Nov 2020 15:59:36 GMT

Sorry, you are right. It is possible for NAT64 to receive packets if it has the state from a recent transfer, or it is using static routing.

Have you tried removing the first backslash from the URI path? As you can see from the proceeding resource definitions, the leading backslash is not used in the path, this is added automatically by the CoAP libraries:

.mUriPath = "$sys/CxD2hb4NHT/tttt/thing/property/set",

RE: Problems on nrf52840 coap server to receive packages

taoyinzhou — Tue, 27 Oct 2020 02:53:03 GMT

I also released problem on https://groups.google.com.

groups.google.com/.../8hv4SjVRBgAJ.

RE: Problems on nrf52840 coap server to receive packages

taoyinzhou — Tue, 27 Oct 2020 02:48:49 GMT

The sniffer trace does confirm that the CoAP PUT request is being sent over the air and received by the intended recipient. So,NAT64 can be deliver packets going from global IPv4 internet to the IPv6 based Thread network.The problem should be with my source code caused the error.devzone.nordicsemi.com/.../75155.main.c devzone.nordicsemi.com/.../thread_5F00_coap_5F00_utils.c

RE: Problems on nrf52840 coap server to receive packages

Jørgen Holmefjord — Mon, 26 Oct 2020 16:45:15 GMT

It looks from your sniffer logs that you do not have global IPv6 connectivity and/or the CoAP cloud server is running on a IPv4 interface. In order to send packets from IPv4 cloud service to the nodes in the network, you either need to use global IPv6 addresses (2000::/3 prefix), or you need to setup a translation method on the border router to forward the packets to the correct node (for instance NAT46). The border router image provided by Nordic only enables NAT64, which can send packets from the IPv6 based Thread network, to global IPv4 internet. It does not provide any mechanisms for packets going from global IPv4 internet to the IPv6 based Thread network.

RE: Problems on nrf52840 coap server to receive packages

taoyinzhou — Fri, 23 Oct 2020 01:55:18 GMT

Hi,

Actually, my coap server needs to both send and receive coap packages. The nrf52840 coap server needs to send a registration package to the cloud server first, then I can receive a reply package from the cloud. So, I can confirm that the whole network is working.

I have attached the .pcap that trace on both the wpan0 interface as well as a sniffer packet capture from the Thread network.

Thread Master Key is 00112233445566778899aabbccddeeff

devzone.nordicsemi.com/.../10.23_2D00_sniffer.pcap devzone.nordicsemi.com/.../10.23_2D00_wpan0.pcap

you can see the first and second packages is the interaction between the cloud server and nrf52840 coap server. nrf52840 coap server address is fd11:22::2d65:6cbb:4e63:ef8. I think the nrf52840 coap server should receive this package. The last package is the one that sent from the cloud to the coap server.

Here is my code modified extract:

static otCoapResource m_property_set_request_resource =

{

.mUriPath = "/$sys/CxD2hb4NHT/tttt/thing/property/set",

.mHandler = property_set_request_handler,

.mContext = NULL,

.mNext = NULL

};

static void thread_coap_init(void)

{

thread_coap_utils_configuration_t thread_coap_configuration =

{

.coap_server_enabled = true,

.coap_client_enabled = true,

.configurable_led_blinking_enabled = false,

};

thread_coap_utils_init(&thread_coap_configuration);

}

void thread_coap_utils_init(const thread_coap_utils_configuration_t * p_config)

{

otInstance * p_instance = thread_ot_instance_get();

otError error = otCoapStart(p_instance, OT_DEFAULT_COAP_PORT);

ASSERT(error == OT_ERROR_NONE);

otCoapSetDefaultHandler(p_instance, coap_default_handler, NULL);

m_config = *p_config;

m_light_command_handler = light_changed_default;

if (m_config.coap_server_enabled)

{

retval = app_timer_create(&m_provisioning_timer,

APP_TIMER_MODE_SINGLE_SHOT,

provisioning_timer_handler);

ASSERT(retval == NRF_SUCCESS);

m_light_resource.mContext = p_instance;

m_property_set_request_resource.mContext = p_instance;

error = otCoapAddResource(p_instance, &m_light_resource);

ASSERT(error == OT_ERROR_NONE);

error = otCoapAddResource(p_instance, &m_property_set_request_resource);

ASSERT(error == OT_ERROR_NONE);

}

static void property_set_request_handler(void * p_context,

otMessage * p_message,

const otMessageInfo * p_message_info)

{

printf("property_set_request_handler\n");

}

The function property_set_request_handler is not called.

Is there some problems with my code that caused the received coap package handle improperly?

Best,

tao

RE: Problems on nrf52840 coap server to receive packages

Jørgen Holmefjord — Wed, 21 Oct 2020 12:34:29 GMT

Hi,

Can you provide more details about the "internet coap client"? How are the packets addressed to the CoAP server node in the Thread network? Do you have global IPv6 connectivity to the border router?

Can you post logs, packet captures, etc that can help with identifying where the packets stop? If you could also upload the modified CoAP server project to show the changes you made, that would also be helpful.

Best regards,
Jørgen