Memory allocation macros in Segger Embedded Studio to program a Soft Device, Application and Bootloader all at once

RE: Memory allocation macros in Segger Embedded Studio to program a Soft Device, Application and Bootloader all at once

RichieJH — Sun, 24 Apr 2016 10:55:55 GMT

There is both a Memory Map XML and a Flash Placement XML. With the Flash Placement XML there is no obvious way in which to add a length or end memory address looking in the example files. Nor is there an obvious way in which to associate each memory segment with the linker files. Are you able to provide further guidance? You mentioned you had managed to get this to work, how did you do it?

RE: Memory allocation macros in Segger Embedded Studio to program a Soft Device, Application and Bootloader all at once

Michael Dietz — Sun, 24 Apr 2016 09:20:47 GMT

OK. I didn't see any way to specify FLASH_LENGTH or FLASH_END in section placement macros. You could try setting the actual memory map. I think this is in either flash placement xml or something like that. You can right click the project and select import flash placement (or memory map) and then select edit flash placement. Then instead of using section placement macros you can set flash, ram start and end here.

RE: Memory allocation macros in Segger Embedded Studio to program a Soft Device, Application and Bootloader all at once

RichieJH — Sun, 24 Apr 2016 08:51:11 GMT

Hi Micheal, yes I tried that - same issue. As alluded to in my previous comment, for the app we are not specifying an end address or length, so could this be an issue for SES when it comes to inserting the Bootloader since it doesn't know where the app has ended or does it calculate this dynamically on building? I am also going to be using fstorage in this application and I know amendments will be needed to the flash_placement_xml, just for added complexity.

RE: Memory allocation macros in Segger Embedded Studio to program a Soft Device, Application and Bootloader all at once

Michael Dietz — Sun, 24 Apr 2016 08:40:49 GMT

OK, I'll need to try this and let you know what I find. Can you try flashing just the softdevice, application and bootloader from additional load files (no bootloader_settings.hex). Is there still a collision? bootloader_settings.hex writes a flag in memory where the bootloader is programmed so maybe Embedded Studio is being too strict here and we need to find a way to allow this.

RE: Memory allocation macros in Segger Embedded Studio to program a Soft Device, Application and Bootloader all at once

RichieJH — Fri, 22 Apr 2016 19:50:54 GMT

Hi Michael, I'm afraid I couldn't get this to work. I got "cannot download multiple load files because they overlap." I had 3 files to load using the loader in addition to the app. The total set comprised the SD, the app - which just happened to be the ble_app_uart I was working on, the pca10040 dual bank boot loader hex and the boot loader setting hex. The only section placement macros was the for the app (where, perhaps importantly, you only specify the start of the memory for the app, not its length or end), as usual. Any other thoughts? RJH

RE: Memory allocation macros in Segger Embedded Studio to program a Soft Device, Application and Bootloader all at once

RichieJH — Fri, 22 Apr 2016 14:47:43 GMT

Thanks Michael, that was the bit I was missing - the hex carries its own address. I'll give it a go a little later and let you know how I get on. Thanks - RJH

RE: Memory allocation macros in Segger Embedded Studio to program a Soft Device, Application and Bootloader all at once

Michael Dietz — Fri, 22 Apr 2016 14:47:03 GMT

Note: A common misconception is that you need to flash the bootloader using nrfjprog. This is only the case when using Keil with nRF51. The Keil Flash algorithms can't properly write the UICR on nRF51 and this is why the problem occurs.

If you are developing on nRF52, or you aren't using Keil, you can use your IDE to program the Bootloader no problem! (to be clear: You can program the bootloader from the Keil IDE when using nRF52 device).

RE: Memory allocation macros in Segger Embedded Studio to program a Soft Device, Application and Bootloader all at once

Michael Dietz — Fri, 22 Apr 2016 14:43:42 GMT

Short Answer: You don't need to specify where the Bootloader goes (see the 'Loading .hex files' section below). Basically a .hex file specifies where the data should go. You have already configured the Section Placement Macro/Memory Map for the SoftDevice and don't need to do anything else here.

Loading the .hex files:

The .hex file specifies both the actual program data to be written to flash, along with the address of where that data should be written (i.e. write 0xDEADBEEF to address 0x1C000, 0xB16B00B5 to address 0x1C004, etc...) So when we load these .hex files to the board we are sure there will be no overlapping.

Doing this all in Embedded Studio:

We want to specify both the SoftDevice and Bootloader as 'Additional Load Files' in 'Project Properties -> Debugger -> Loader Options.' So specify the paths to each of the .hex files there. (To flash the Application when a Bootloader is present you also need to write a flag in FLASH. I recommend also specifying this bootloader_settings_nrf52.hex as an additional file to loader. It is a .hex file that writes that flag for you). bootloader_settings_nrf51.hex

Now when you compile your application and load it to your board, Embedded Studio will flash the SD, BL and write the flag for you! And if there are any collisions between the .hex file you will get an error.

RE: Memory allocation macros in Segger Embedded Studio to program a Soft Device, Application and Bootloader all at once

Ole Bauck — Fri, 22 Apr 2016 13:45:48 GMT

Ok, then I will withdraw my statement and wait for Michael to answer.

RE: Memory allocation macros in Segger Embedded Studio to program a Soft Device, Application and Bootloader all at once

RichieJH — Fri, 22 Apr 2016 13:43:19 GMT

Hi Ole, the reason I asked is that Mike said it was possible. I had an exchange with him yesterday where he said ask in the forum and he would respond.

RE: Memory allocation macros in Segger Embedded Studio to program a Soft Device, Application and Bootloader all at once

Ole Bauck — Fri, 22 Apr 2016 13:40:43 GMT

You need to use nrfjprog to program the bootloader, so I guess it will not work anyhow.

To get the bootloader to start the application after flashing without using DFU you need to set address BOOTLOADER_SETTINGS_ADDRESS to 0x01, see this FAQ (question E).