Re: Single Bank firmware update (ie nordic vendor style dfu)

Hi Jacob, On Tue, Jan 17, 2017 at 09:06:36PM -0700, Jacob Rosenthal wrote: [...] > As you can see, I cant seem to get slot1 active and confirmed It looks like one of two things is going wrong: 1. The loader (bleprph) is failing to jump into the application (splitty), or 2. The application

Re: Single Bank firmware update (ie nordic vendor style dfu)

Used your settings to be sure were the same (cool override in the target) JLinkExe -if SWD -device nRF51822 -speed 1000 erase all q newt size shows were under 112238 110532 1276 10664 122472 1de68

Re: Single Bank firmware update (ie nordic vendor style dfu)

Thanks Chris! Tried some more with the new upstreamed code but a few more issues... Still had to add the serial transport to bleprph, not sure if you left that out of there on purpose for code size.. - mgmt/newtmgr/transport/nmgr_shell newt run split-nrf51dk 0 and it responds to newtmgr

Re: Single Bank firmware update (ie nordic vendor style dfu)

Just a follow up for the list- It turns out there were a number of issues with split images. I believe they have all been resolved now. Some of the required changes were non-trivial, so I wanted to summarize what I did. 1. bleprph doesn't jump to app (slot 2). This one is straightforward.

Re: Single Bank firmware update (ie nordic vendor style dfu)

On Fri, Jan 13, 2017 at 04:38:25PM -0700, Jacob Rosenthal wrote: > Ah, I expected gdb of optimized split code to be a nightmare and hadnt > tried yet. > newtmgr has never crashed.. it just hangs forever > > I cant get the SOFT anymore now. hrmmm Just hanging out here.. > (gdb) where > #0

Re: Single Bank firmware update (ie nordic vendor style dfu)

Hi Jacob, If that reboot log entry is recent, it looks like your device is crashing. A reason of "SOFT" indicates a firmware crash [*]. I would say the quickest way to debug this is to run the code in gdb. You can do this with the "newt run" command: newt run 0 When gdb comes up, type c

Re: Single Bank firmware update (ie nordic vendor style dfu)

turned off a ton more bluetooth shit for more ram both still hang: newtmgr -c serial1 logs log_list newtmgr -c serial1 image list but log in shell now has: newtmgr 4976:Dumping log reboot_log On Thu, Jan 12, 2017 at 8:33 PM, Jacob Rosenthal wrote: > log on shell

Re: Single Bank firmware update (ie nordic vendor style dfu)

log on shell shows lots of these 9050:[0] rsn:SOFT, cnt:1, img:0.0.0.0 On Thu, Jan 12, 2017 at 8:28 PM, Jacob Rosenthal wrote: > All newtmgr commands on serial are hanging indefinitely. > Jacobs-MacBook-Air:mynewt-hr-observer jacobrosenthal$ newtmgr -c serial1 > image

Re: Single Bank firmware update (ie nordic vendor style dfu)

All newtmgr commands on serial are hanging indefinitely. Jacobs-MacBook-Air:mynewt-hr-observer jacobrosenthal$ newtmgr -c serial1 image list ^C Jacobs-MacBook-Air:mynewt-hr-observer jacobrosenthal$ newtmgr conn show Connection profiles: serial1: type=serial, connstring='/dev/tty.usbmodem1411'

Re: Single Bank firmware update (ie nordic vendor style dfu)

On Thu, Jan 12, 2017 at 07:06:37PM -0700, Jacob Rosenthal wrote: > Still ok... and Im able to interact with shell over serial and I think its > advertising!? Not sure why my newtmgr wont connect then.. Ideas to > troubleshoot? So you are sending newtmgr commands over serial? Do all commands

Re: Single Bank firmware update (ie nordic vendor style dfu)

Hi Jacob, On Thu, Jan 12, 2017 at 07:19:11PM -0700, Jacob Rosenthal wrote: > OH really interesting.. In the updated documentation the biggest change > from what I was doing was splitty is the app and bleprph is the loader. Is > that intentional? Yes - the loader needs to contain everything

Re: Single Bank firmware update (ie nordic vendor style dfu)

On Mon, Jan 09, 2017 at 10:48:48AM -0800, Christopher Collins wrote: > The boot sequence and upgrade procedure for the split image setup is a > bit complicated. I have been working on some documentation for this > area, but haven't quite finished it. I hope to have something ready in > a day or

Re: Single Bank firmware update (ie nordic vendor style dfu)

Hi Jacob, On Sun, Jan 08, 2017 at 01:04:54PM -0700, Jacob Rosenthal wrote: > On Mon, Jan 2, 2017 at 2:46 PM, Christopher Collins > wrote: > > > Do you know how big your loader is currently? > > > Well, could be anything based on how much Im trying to strip from the >

Re: Single Bank firmware update (ie nordic vendor style dfu)

Hi Jacob, On Sun, Jan 01, 2017 at 11:10:01PM -0700, Jacob Rosenthal wrote: > On low flash devices like nrf51822 FLASH_AREA_IMAGE_1 equal to > FLASH_AREA_IMAGE_0 is improbable, which means dual bank is likewise > improbable and as a result we've talked previously about how to shrink >

Single Bank firmware update (ie nordic vendor style dfu)

On low flash devices like nrf51822 FLASH_AREA_IMAGE_1 equal to FLASH_AREA_IMAGE_0 is improbable, which means dual bank is likewise improbable and as a result we've talked previously about how to shrink FLASH_AREA_IMAGE_1 down to a stub. However, my current understanding is newtmgr/imagemgr