Hi Jacob,
On Fri, Dec 30, 2016 at 05:42:06PM -0700, Jacob Rosenthal wrote:
> It seems like the current bootloader can receive bytes over serial, but
> mainly boots or swaps flash areas, presuming newtmgr already received and
> placed the update in flash 1
> For 'single bank' style it seems like I would need some kind of softdevice
> style solution like nordic so the bootloader has (unduplicated)access to
> nimble so it could receive bytes via bluetooth in the bootloader without
> duplicating that code...
> Whats the newt way :) Thoughts?
I think it might help if you could clarify what you are looking for. In
particular, I am not sure what you mean by "single bank." Mynewt lets
you use the following setups:
* Dual bank (two standalone images)
* Split (Kernel in slot 0, application in slot 1)
* Single image (One large image; upgrade not supported)
The split option is closest to Nordic's DFU solution. In this setup,
functionality is partitioned among the two slots as follows:
* Slot 0 (loader):
o OS.
o BLE stack.
o Anything else required for image upgrade.
* Slot 1 (application):
o Parts of Mynewt not required for image upgrade.
o Application-specific code.
The split image setup saves flash space because the application image
doesn't need to contain the OS and network stack. However, image
upgrade is a bit more complicated, and there is no automatic fallback to
the previous image on upgrade failure.
Chris
