Single bank Bootloader is over 16k when generating zip file for OTA

RE: Single bank Bootloader is over 16k when generating zip file for OTA

Vidar Berg — Tue, 01 Mar 2016 07:48:21 GMT

Hi MC, the last page in flash is used by the bootlaoder to store the bootloader_settings_t structure, and cannot be included in the DFU image. But you can use it if programming through the debug interface, please see question 'E' in this FAQ for more details.

Attached a distribution packet of the other hex file you sent to my answer.

RE: Single bank Bootloader is over 16k when generating zip file for OTA

mc — Tue, 01 Mar 2016 01:34:56 GMT

Hi Vidar,

The hex files are included.

Regards, MC

RE: Single bank Bootloader is over 16k when generating zip file for OTA

Vidar Berg — Mon, 29 Feb 2016 13:28:33 GMT

strange, there isn't anything linked above 0x3FC00 or anything below 0x3C000 as far as I can see, so it shouldn't be more than 15K. May I ask for the .hex file as well?

RE: Single bank Bootloader is over 16k when generating zip file for OTA

mc — Mon, 29 Feb 2016 13:24:17 GMT

Hi Vidar,

Attached is the map files. The nRF51422-xxac.map is the file I merge with bootloader_setting.hex that just exceeding 15k as you mentioned.

Regards, MC

RE: Single bank Bootloader is over 16k when generating zip file for OTA

Vidar Berg — Mon, 29 Feb 2016 13:03:14 GMT

The .bin file is just exceeding 15K. Note that it's only the binary image that will be loaded to flash and potentially cause the "data Size Exceeds". The content of .dat will be transferred in the init packet, and loaded to RAM, and the json is used by the smart phone app determine the content of the distribution packet.

Could you share the .map file from your build output so I can see if there might be anything linked outside of the default address range?

RE: Single bank Bootloader is over 16k when generating zip file for OTA

mc — Mon, 29 Feb 2016 12:10:52 GMT

Hi Vidar,

The link help me solve why there is an extra bytes in my bootloader code when enabling the:

uint8_t m_boot_settings[CODE_PAGE_SIZE] attribute((at(BOOTLOADER_SETTINGS_ADDRESS))) attribute((used)) = {BANK_VALID_APP} ;

The work around was suggested that merging the bootloader_setting.hex with the code of

uint8_t m_boot_settings[CODE_PAGE_SIZE] attribute((at(BOOTLOADER_SETTINGS_ADDRESS))) attribute((used));

But then is still when generating the package size its still above 16k. *.bin = 15368, *.dat = 14, *.json = 492. A total of 16,226 bytes. The nRF_toolbox always says "data Size Exceeds".

Do you have any idea on how to lower it below 16k.

Thanks.

RE: Single bank Bootloader is over 16k when generating zip file for OTA

mc — Mon, 29 Feb 2016 06:48:51 GMT

Hi Vidar,

I think I find the answer on this link. devzone.nordicsemi.com/.../p>

The problem is until now this was not yet solve.

Thank you for helping.

-MC

RE: Single bank Bootloader is over 16k when generating zip file for OTA

mc — Sat, 27 Feb 2016 07:02:17 GMT

Hi Vidar,

This is my command in generating the bootloader package:

nrfutil dfu genpkg --bootloader MyBT16kFile.hex --application-version 0xFFFFFFFF --dev-type 0x0### --dev-revision 0x0### --sd-req 0x## MyBT16kOTA.zip

This much the same in you suggestion. ### is handled in the bootloader code.

I tried the example dual bank of S310 but there is an error when converting to 16k but get struck with the error:

._build\nrf51422_xxac.axf: Error: L6406E: No space in execution regions with .ANY selector matching arm_startup_nrf51.o(STACK). ._build\nrf51422_xxac.axf: Error: L6407E: Sections of aggregate size 0x800 bytes could not fit into .ANY selector(s).

I tried to search for the fix of this but no luck...I tried hacking the stack size to 255 and it compiled okay but I do not wan't to have a problem in the future of hacking stack.

I am back to solving the puzzle of nrfutil why it exceeds 16k. Some note, I used the no pack of SDK9.0 for my code.

-MC

RE: Single bank Bootloader is over 16k when generating zip file for OTA

Vidar Berg — Fri, 26 Feb 2016 13:12:13 GMT

Hi,

Are you using nrfutil to generate the distribution file as explained here?

e.g., nrfutil dfu genpkg ../application.zip --bootloader .hex --application-version 0xFFFFFFFF --dev-revision 0xFFFF --dev-type 0xFFFF --sd-req 0xFFFE

Note that this tool strips the UICR section from the .hex file before converting to a binary image. Otherwise you'd gotten a lot of byte padding in the image since UICR register are memory mapped to 0x10001000 (0x3c000 -> 0x10001000 = ~250MB).

Attachment:

application.zip