Bootloader settings generation for application size issue

RE: Bootloader settings generation for application size issue

Hung Bui — Fri, 29 Jun 2018 14:42:13 GMT

No, I mean the nrfutil expect that the application hex image should be an image configured to be used with softdevice (flash start address of the application is at where the softdevice end)

In your case i guess you was testing using the application that should run without the softdevice , is it correct ? This wouldn't make much sense because you need the softdevice for the bootloader and to do DFU.

RE: Bootloader settings generation for application size issue

Sridhar Jonnavittula — Thu, 28 Jun 2018 14:40:28 GMT

So you say size is the issue for nrfutil to generate bootloader settings without softdevice. Is my understanding right?

RE: Bootloader settings generation for application size issue

Hung Bui — Thu, 28 Jun 2018 14:09:54 GMT

I think it has something to do with the start address setting of the application hex.

nrfutil expect the image to be used with softdevice. If you change the ROM setting of the application to start at address 0x26000 ( so it could run with S140 v6.0) you should be able to create the bootloader setting hex.

RE: Bootloader settings generation for application size issue

Sridhar Jonnavittula — Thu, 28 Jun 2018 12:43:21 GMT

Hi,

Think I took hardware peripheral blinky as it is present in SDK v15.0.0 (as in screenshot above). I did not make any changes.

Thanks

RE: Bootloader settings generation for application size issue

Hung Bui — Thu, 28 Jun 2018 11:50:57 GMT

Hi,

Could you send the application to me so we can test here ? Do you see the same issue when you generate the bootloader setting for other application ? such as the blinky or other example where have in the SDK ?