Trying to compile DFU bootloader code in segger embedded studio.

[Meera Shah]

When I tried to compile bootloader example code of sdk  bootloader_secure, I am facing some of the errors when I tried to compile using Segger Embedded Studio, which could not be solved. I think this is generating because of compiler difference. I am using s130.

`.bootloaderSettings' will not fit in region `UNPLACED_SECTIONS' region .

   In function `nrf_dfu_transports_init':
     undefined reference to `__stop_dfu_trans'
     undefined reference to `__start_dfu_trans'
   In function `nrf_dfu_bl_continue':
    undefined reference to `__isr_vector'
Build failed

[bjorn-spockeli]

You,re probably missing the bootloaderSettings section in the flash_placement.xml file, take a look at the flash_placement.xml file from this answer. 

Best regards

Bjørn

[Meera Shah]

I have uploaded this image of upgraded SDK code. But in my 12.3.0 there is no option in linker of Section placement file.

So there would be no effects of flash_placement.xml. whether I will do changes or not.

[Meera Shah]

Hey I have resolved these 2 errors described below by adding into flash_placement.xml.

undefined reference to `__stop_dfu_trans'
undefined reference to `__start_dfu_trans'

Can you tell me how to resolve undefined reference to `__isr_vector' ? Because I am working in Segger so  #define BOOTLOADER_START_ADDR        (uint32_t)&__isr_vector   this will be activated.

[awneil]

Meera Shah said:

how to resolve undefined reference to `__isr_vector' ?

You need to provide a definition of __isr_vector.

Again, look at a current SDK example, as that will have an SES project - use that to guide you.

[Meera Shah]

Where I need to provide a definition of __isr_vector?

[awneil]

look at a current SDK example, as that will have an SES project - use that to guide you

[Meera Shah]

When I ported nRF5_SDK_12.3.0_d7731ad\nRF5_SDK_12.3.0_d7731ad\examples\dfu\bootloader_secure project in Segger Embedded studio

#elif defined (__GNUC__)

#define BOOTLOADER_START_ADDR        (uint32_t)&__isr_vector.

But when I look into current SDK nRF5_SDK_15.3.0_59ac345\nRF5_SDK_15.3.0_59ac345\examples\dfu\secure_bootloader\pca10040e_ble\ses

#elif defined(__SES_ARM)  <= It will be under this compiler. So no __isr_vector in this when we use SES compiler

#define BOOTLOADER_START_ADDR (CODE_START)

[awneil]

So the other thing is to look at the Keil Project, and see how it gets its Bootloader start address.

Remember: the chip neither knows nor cares what IDE or toolchain you use - it just runs the code that's in the flash.

So, with any porting exercise, the object is to ensure that whatever ends up in flash is equivalent.

[Meera Shah]

In keil it is

#elif defined (__CC_ARM)
    #define BOOTLOADER_START_ADDR        (uint32_t)&Image$$ER_IROM1$$Base

[awneil]

So you know what Image$$ER_IROM1$$Base is?

[Meera Shah]

No

[awneil]

Look it up:

http://www.keil.com/support/man/docs/armlink/armlink_pge1362065952432.htm

A key part of any porting exercise is a solid understanding of what you're porting - and what you're porting it to!