Memory partition between application and bootloader in nRF52832

RE: Memory partition between application and bootloader in nRF52832

Vidar Berg — Wed, 06 Mar 2024 09:00:57 GMT

You project was partly configured to run on the nRF52810.

devzone.nordicsemi.com/.../bootloader_5F00_nrf52832_5F00_mod.zip

RE: Memory partition between application and bootloader in nRF52832

Sanjana — Wed, 06 Mar 2024 05:29:40 GMT

Hello,

Sorry for the delay in reply.

Please find the bootloader file here

RE: Memory partition between application and bootloader in nRF52832

Vidar Berg — Wed, 28 Feb 2024 11:16:29 GMT

Are you able to share your modified bootloader here?

RE: Memory partition between application and bootloader in nRF52832

Sanjana — Wed, 28 Feb 2024 09:31:50 GMT

It is buffering here and shows nothing and the log is empty

RE: Memory partition between application and bootloader in nRF52832

Vidar Berg — Wed, 28 Feb 2024 07:37:17 GMT

Could you please share the debug log from the phone app, as well as the debug log from the bootloader (if logging is enabled in the bootloader)?

RE: Memory partition between application and bootloader in nRF52832

Sanjana — Wed, 28 Feb 2024 04:06:31 GMT

My custom bootloader is pretty much similar to the SDK bootloader example except that It has few other additional led indications. Presently, the device is advertising and when I connected to it, no services are visible and the device got disconnected after few seconds.

RE: Memory partition between application and bootloader in nRF52832

Vidar Berg — Mon, 26 Feb 2024 12:14:57 GMT

What is supposed to happen when your custom bootloader enters DFU mode? Should it start BLE advertising? Is your bootloader based on the SDK bootloader?

RE: Memory partition between application and bootloader in nRF52832

Sanjana — Mon, 26 Feb 2024 12:10:06 GMT

My device has a combined hex file (bootloader + application + softdevice(s112) ) with the above memory settings. I tried to enter into the bootloader mode, but no services were shown here.

RE: Memory partition between application and bootloader in nRF52832

Vidar Berg — Mon, 26 Feb 2024 08:29:52 GMT

I don’t see any obvious errors in the memory layout you’ve posted. I might be able to help if you can describe the actual problem you’re facing.

RE: Memory partition between application and bootloader in nRF52832

Sanjana — Mon, 26 Feb 2024 05:28:30 GMT

Can you please verify the above memory settings. I'm stuck here

RE: Memory partition between application and bootloader in nRF52832

Sanjana — Tue, 20 Feb 2024 13:03:18 GMT

Can you please verify my section placement macros and memory segments bootloader

Bootloader:

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x80000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0x10000

FLASH_START=0x50000

FLASH_SIZE=0x10000

RAM_START=0x20001C08

RAM_SIZE=0x43F8

Memory segments:

FLASH RX 0x0 0x80000;RAM RWX 0x20000000 0x10000;uicr_bootloader_start_address RX 0x10001014 0x4;bootloader_settings_page RX 0x0007F000 0x1000;mbr_params_page RX 0x0007E000 0x1000;uicr_mbr_params_page RX 0x10001018 0x4

RE: Memory partition between application and bootloader in nRF52832

Vidar Berg — Tue, 20 Feb 2024 11:36:46 GMT

Then, I suggest using the memory layout from our example as a reference.

Memory layout

RE: Memory partition between application and bootloader in nRF52832

Sanjana — Tue, 20 Feb 2024 11:26:00 GMT

Yes, i am developing a custom bootloader

RE: Memory partition between application and bootloader in nRF52832

Vidar Berg — Tue, 20 Feb 2024 10:20:58 GMT

Are you developing a custom bootloader, and is there a reason for not using the default memory layout used in our bootloader example?

RE: Memory partition between application and bootloader in nRF52832

Sanjana — Tue, 20 Feb 2024 10:07:09 GMT

I am using nRF5 SDK and S112 softdevice

Can you please help me with proper section placement macros for application and bootloader for RAM and flash

RE: Memory partition between application and bootloader in nRF52832

Vidar Berg — Tue, 20 Feb 2024 07:52:45 GMT

Hi,

The correct memory layout depends on the SDK you use. With the nRF Connect SDK, the bootloader starts at address zero, and with the nRF5 SDK, the bootloader is placed after the application. Are you developing a custom bootloader? We don't impose any restrictions on the features you can implement in the bootloader.