[ 
https://issues.apache.org/jira/browse/MYNEWT-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vipul Rahane closed MYNEWT-489.
-------------------------------
    Resolution: Fixed

> Changes to newtmgr fragmentation code - Removing RSP_COMPLETE flag
> ------------------------------------------------------------------
>
>                 Key: MYNEWT-489
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-489
>             Project: Mynewt
>          Issue Type: Improvement
>            Reporter: Vipul Rahane
>            Assignee: Vipul Rahane
>             Fix For: v1_0_0_rel
>
>
> Current functionality: 
> Firmware: We have a flag named NMGR_F_CBOR_RSP_COMPLETE. When the protocol 
> fragments the response, it sets this flag on the last fragment. Each fragment 
> has a 8 byte newtmgr header which is not currently used for any specific 
> purpose in subsequent fragments other than the first fragment.
> Each fragments header contains the length of the fragment.
> Newtmgr Tool: Caters to firmware functionality.
> Proposed changes: 
> Firmware: Only the first fragment would have a newtmgr header with the length 
> of the entire response. The subsequent fragments would not contain the 
> header. NMGR_F_CBOR_RSP_COMPLETE will get removed with the above changes. 
> This would mean that reliability would get handled by the transport as 
> opposed to the application layer protocol. Bluetooth being a reliable 
> protocol, fragmentation works fine.
> Newtmgr Tool: Make changes to it to cater to the firmware functionality.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to