You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "Jacob (JIRA)" <ji...@apache.org> on 2017/05/10 02:41:04 UTC

[jira] [Created] (MYNEWT-747) Impossible to newtmgr upload firmware to nrf51 devices

Jacob created MYNEWT-747:
----------------------------

             Summary: Impossible to newtmgr upload firmware to nrf51 devices
                 Key: MYNEWT-747
                 URL: https://issues.apache.org/jira/browse/MYNEWT-747
             Project: Mynewt
          Issue Type: Bug
          Components: Image Mgmt, Newtmgr
         Environment: All
            Reporter: Jacob
            Assignee: Marko Kiiskila


It is currently not possible to upload firmware to a nrf51 device.
Mailing list discussion:
https://lists.apache.org/thread.html/bc99b1c75790198685d40a12e8e49de12f0b9e8891f93f2fd9a95f0d@%3Cdev.mynewt.apache.org%3E

Logs show:
832:[ts=6499968ssb, mod=4 level=0] Disconnection Complete: status=0 handle=1 reason=8

Appears to be related to the flash erase
https://github.com/apache/incubator-mynewt-core/blob/cb23f34e9b55de68078c0c2200b268cf536d003b/mgmt/imgmgr/src/imgmgr.c#L324

Flash erase is blocking and takes a while, so traditionally on nordic softdevic schedule to work outside of radio events as much as possible.  newtmgr isnt and probably shouldn't be coupled down to the radio abstraction.

Nordic forum also talks about altering intervals and latencies, 
https://devzone.nordicsemi.com/question/24290/slow-flash-erase-performance-with-sd_flash_page_erase/?answer=24361#post-id-24361
but discussion on the list also found that a lacking solution

One possible solution discussed solution was to separate erase from upload commands 




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)