You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "Christopher Collins (JIRA)" <ji...@apache.org> on 2017/03/15 01:17:41 UTC
[jira] [Created] (MYNEWT-670) image / fs NMP: Make max chunk size
configurable
Christopher Collins created MYNEWT-670:
------------------------------------------
Summary: image / fs NMP: Make max chunk size configurable
Key: MYNEWT-670
URL: https://issues.apache.org/jira/browse/MYNEWT-670
Project: Mynewt
Issue Type: Improvement
Components: Newtmgr
Reporter: Christopher Collins
Assignee: Christopher Collins
Fix For: v1_1_0_rel
Currently, the largest image or file chunk that a Mynewt device can receive is hardcoded at 400 bytes. This is not great because this number is independent of the transport MTU, so the client has no way of knowing the limit.
The fix is to create two new compile-time settings:
* FS_UPLOAD_MAX_CHUNK_SIZE
* IMGMGR_MAX_CHUNK_SIZE
and set them to 512 by default. This value is large enough to accommodate full-size BLE packets.
This is still not a perfect solution because these values are not tied to the MTU in any way. One way to truly solve this would be to have an "NMP MTU" that the client can discover. That would be a pretty big change.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)