OrgApache/incubator-nuttx
OrgApache
/
incubator-nuttx
mirror of https://github.com/apache/incubator-nuttx.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Trivial update to a README file

This commit is contained in:
Gregory Nutt 2017-08-08 13:03:09 -06:00
parent d49d6a6aa9
commit 53d8a0b557
1 changed files with 10 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
configs/b-l475e-iot01a/README.txt
View File

@ -593,13 +593,16 @@ Configuration sub-directories
I would say it is functional but fragile in this usage, but probably I would say it is functional but fragile in this usage, but probably
robust in a less busy environment. robust in a less busy environment.
2017-08-08: Added broadcast packet transfers using the hub-based 2017-08-08: The warning debug messages noted yesterday are no longer
broadcast UDP client. This appears to be a problem the HC06 present. No clue why.
compression/decompression. The decompression logic comes up with
the destination address as ff02::ff00:00fe:3500 (which the receiving Added broadcast packet transfers using the hub-based broadcast UDP
node address is 37) instead of ff02::0001. It is then out of sync client. This appears to be a problem the HC06 compression and/or
with the IPHC headers and is unable to uncompress the rest of the decompression. The decompression logic comes up with the
packet correction. destination address of ff02::ff00:00fe:3500 (which derives from the
receiving node address of 37) instead of the all-nodes multicast
address of ff02::0001. It is then out of sync with the IPHC headers
and is unable to uncompress the rest of the packet correctly.
Trying again with HC1 compression, I see other isses. The first Trying again with HC1 compression, I see other isses. The first
frame is received correctly, but the following frames have an incorrect frame is received correctly, but the following frames have an incorrect