-
It seems that duplicated message ID are also processed. In our case the LWM2M client callback is executed for all duplicated POST messages.
Copied from The Constrained Application Protocol (CoAP) Jun…
-
Would it be possible to add "Update fails [Res == 8]" to the arrow from "UPDATING" to "IDLE" to allow a "BootLoader" to delete a broken image? (Just if that broken image could only be detected by the …
boaks updated
8 years ago
-
When analyzing issue #44, I noticed that the client transfers the next block only after the server has acknowledged the previous block. You can see this very clearly in the attached tcpdumps.
This ma…
-
I am using the HelperClient class. It seems to only send a single datagram and then wait forever for a response.
-
In case the data size of a registration exceeds the 1510 bytes, the datagram in the IPv6 stack will be fragmented. If the client device has not communicated with its destination device before (in this…
-
We use the LWM2M client with a registration size of >1800 bytes. The CoAP block transfer size is defined on "coap_max_blockwise_payload_size": 512. In the 1st block the last 2 payload bytes are inval…
-
I am currently working on pushing updates via the Firmware Object (/5/0/0); however, messages are truncated at the 128 bytes as defined by REST_MAX_CHUNK_SIZE in er-coap.h.
Current Behaviour:
Firmwar…
-
Does this library allow for blockwise transfers as described here: http://www.google.com/url?q=http%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-core-block-08&sa=D&sntz=1&usg=AFQjCNGpPAnNm15802QG7Kgw_7i…
-
When using the CoAP lib on the nano IPv6 stack with a wired Ethernet connection running the sal-driver-lwip-k64f-eth, packets with a size >1510 bytes needs to be fragmented. The issue we see is that …
-
Hello everybody, is the blockwise transfer supported?