Download and debug application using SES in the presence of bootloader

RE: Download and debug application using SES in the presence of bootloader

bojan — Fri, 15 May 2020 15:25:26 GMT

Hey, Einar.

Indeed, it seems it is not a problem. I respected the steps suggested by SK and now everything is OK. I will close this topic not.

Thanks for your readiness to help though!

Regards,

Bojan.

RE: Download and debug application using SES in the presence of bootloader

Einar Thorsrud — Fri, 15 May 2020 15:20:20 GMT

Hi Bojan,

The fact that nRF Connect Programmer shows the bootloader as "Application" in this case, is just an issue in how it presents it. This is not a problem and there is nothing you can do about it.

What is the real problem, and what is it you want to achieve?

RE: Download and debug application using SES in the presence of bootloader

bojan — Thu, 14 May 2020 11:26:21 GMT

Hello SK.

Thanks for the useful link. It is now clear about Flash and RAM. However, I still don't know how can I adjust the bootloader, MBR, bootloader settings parameters in secure_bootloader_gcc_nrf52.ld file that comes with dfu example.

For example, when I compile secure_bootloader_ble_s140_pca10056 example and load the .hex file nto nRF Programmer tool here is what I get:

Bootloader is not seen as a bootloader but as application. This is the appropriate content of secure_bootloader_gcc_nrf52.ld file

MEMORY
{
  FLASH (rx) : ORIGIN = 0xf8000, LENGTH = 0x6000
  RAM (rwx) :  ORIGIN = 0x20002a98, LENGTH = 0x3d568
  uicr_bootloader_start_address (r) : ORIGIN = 0x00000FF8, LENGTH = 0x4
  bootloader_settings_page (r) : ORIGIN = 0x000FF000, LENGTH = 0x1000
  uicr_mbr_params_page (r) : ORIGIN = 0x00000FFC, LENGTH = 0x4
  mbr_params_page (r) : ORIGIN = 0x000FE000, LENGTH = 0x1000
}

Should I adjust some more parameter in order to properly load bootloader?

Thanks in advance.

Bojan.

RE: Download and debug application using SES in the presence of bootloader

SK — Thu, 05 Mar 2020 01:24:40 GMT

Hi,

Can you confirm when you click Debug -> Go in SES, it does not hit main()? If that's the case, memory mapping is not done correctly.

In such case, there is a good article on adjustment in RAM and Flash that you can follow:

https://devzone.nordicsemi.com/nordic/short-range-guides/b/getting-started/posts/adjustment-of-ram-and-flash-memory

RE: Download and debug application using SES in the presence of bootloader

bojan — Wed, 04 Mar 2020 20:28:47 GMT

Hello SK.

Just tried to merge the .hex files the way you described. I was unable to debug, unfortunately.

Here is how the final sd_bl_app.hex looks like when implemented in nRF52840:

Am I missing something ?

Regards,

Bojan.

RE: Download and debug application using SES in the presence of bootloader

bojan — Tue, 03 Mar 2020 08:20:27 GMT

OK, SK.

Let me give it a try! 😉

Regards!

RE: Download and debug application using SES in the presence of bootloader

SK — Tue, 03 Mar 2020 08:18:13 GMT

It will. Make sure your addressing and memory mapping are correct.

RE: Download and debug application using SES in the presence of bootloader

bojan — Tue, 03 Mar 2020 08:01:09 GMT

Hello SK.

Thanks for your feedback. IMHO, the process you described will not allow me to debug from Segger Embedded Studio (SES) with Debug->Go. Am I correct?

Cheers,

Bojan.

RE: Download and debug application using SES in the presence of bootloader

SK — Tue, 03 Mar 2020 02:38:00 GMT

Hi bojan,

Steps as follows:

1. Generate bootloader settings hex

2. Merge with bootloader hex to generate bootloader_with_settings.hex

3. Merge bootloader_with_settings.hex with application hex -->

mergehex --merge bootloader_with_settings.hex application.hex --output bl_app.hex

4. Merge bl_app.hex with Softdevice

mergehex --merge bl_app.hex SD.hex --output sd_bl_app.hex

5. Erase memory

nrfjprog –eraseall

6. Program memory

nrfjprog --program sd_bl_app.hex

Let me know if this helps.

Best,