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?
On Fri, Dec 30, 2016 at 5:13 PM, Jacob Rosenthal <[email protected]> wrote: > I think I want a bootloader, and Im ok with stub solutions 'losing' a > little flash space, especially if some other dep might still want a little > bit of that space. > > For nrf51 targets it seems like I just wont have room to split equally at > the very least. What other deps use flash areas? My understanding is the > flash area 1 was sized such so that it mainly was used for a 'dual bank' > style solution? > > What about split-nrf51dk-16kbram.ld? Does bsp.part2linkerscript not get > used unless the split dep is utilized? > > Has anyone done anything like that yet, without newtmgr etc? IE dfu > 'single bank' style dfu service like nordic has? > > Thanks for all the info and for such a customizable platform. > > On Fri, Dec 30, 2016 at 4:41 PM, Christopher Collins <[email protected]> > wrote: > >> probably need to build and upload a new boot loader. >> Stub slot support was ad >> > >
