Uploading Bootloader & application

RE: Uploading Bootloader & application

Vidar Berg — Fri, 30 Sep 2022 08:49:24 GMT

No, this is an issue with the linking of your FW images. Forcing the programmer load the FW to another address is not going to fix that.

RE: Uploading Bootloader & application

Asha — Fri, 30 Sep 2022 08:47:05 GMT

Can you guide me how to write the bootloader program into MBR using nRF connect?

RE: Uploading Bootloader & application

Vidar Berg — Fri, 30 Sep 2022 07:42:37 GMT

The problem is that you have two programs that overlap with each other in FLASH. I'm not familiar with PlatformIO, so I can't tell you where to change the linker settings, but that's probably what you need to do.

You can compare the *.map files from your build folders to see where overlap is.

RE: Uploading Bootloader & application

Asha — Fri, 30 Sep 2022 07:28:01 GMT

my application program is simple blinking of LED. I took the .hex files of these and trying to burn it through nRF connect.

When i bun it through VS code, there is no problem. But the same thing when i try to upload through nRF connect its overlapping.

When our product goes for mass production we cant give the source code for burning. So we prefer to give the .hex to burn

RE: Uploading Bootloader & application

Asha — Fri, 30 Sep 2022 07:24:44 GMT

Hi, we have developed our Bootloader & application using VScode(using platformio) on Linux.

Controller using - nRF52382.

This is my bootloader program.

[env:adafruit_feather_nrf52832]
platform = github.com/.../platform-n-able.git#1.0.0
board = adafruit_feather_nrf52832
framework = arduino
board_bootloader = adafruit
;board_build.f_cpu = 64000000L
upload_protocol = jlink
debug_tool = jlink

RE: Uploading Bootloader & application

Vidar Berg — Fri, 30 Sep 2022 07:20:39 GMT

Please summarize what you have done thus far. E.g.. which SDK examples you used to generate the hex files and with what IDE/toolchain. We can't tell you why your hex file overlap when we don't have any information about your projects.

RE: Uploading Bootloader & application

Asha — Fri, 30 Sep 2022 07:13:27 GMT

I didn't find any Linker script in my project

RE: Uploading Bootloader & application

Lecram69 — Fri, 30 Sep 2022 06:47:11 GMT

Take a look here: Nordic Semiconductor Infocenter

Bootloader is at the end of flash. Application starts at 0x1000 without SD but with MBR. Otherwise it starts at 0x27000 with SD. If the parts are not on the correct address position in flash it wont work. You can specify the adress range of the parts in the linker script. Take a look into your project settings and search for a .ld file.

it seems your application starts at 0x1000 so no SD is available. To do a DFU update you still need an MBR at 0x0000-0x1000. The reason you face the problem above is the bootloader. It shouldnt be at the beginng of the flash or collapse with the application at all.

RE: Uploading Bootloader & application

Asha — Fri, 30 Sep 2022 04:23:45 GMT

Please check i have updated the picture.

Bootloader.hex - my bootloader file.

Rizwan.hex - my application, which needs to flash.

RE: Uploading Bootloader & application

Lecram69 — Thu, 29 Sep 2022 10:43:41 GMT

What is Rizwan.hex? What is the address range of blinky.hex?

At the beginng of the flash is the MBR expected with range 0x0000 - 0x1000. At 0x1000 is either the softdevice or the application itself if no softdevice is needed

RE: Uploading Bootloader & application

Asha — Thu, 29 Sep 2022 07:21:06 GMT

can u please guide me, what i should do? because I'm new to this...

RE: Uploading Bootloader & application

Lecram69 — Thu, 29 Sep 2022 06:52:50 GMT

Adjust linker memory section of apllication in flash. Seems like you got MBR and application? Bootloader is at the end of the flash