app.hex was loaded in bootloader area when using KEIL compiling.

[Esten]

Hey experts,

We encountered a problem about project porting and using KEIL compiling. 

Here are detailed:

Our products are using gcc+makefile method to compile and generate .hex file, it works fine.
We want to debug product in hardware situation, so we port the project from gcc+makefile to keil.
According to the configuration of makefile and linker file, we added all necessary parameters in options of KEIL.
We didn't change anything of codes. But the startup file was replaced with arm_startup_nrf52.s, not gcc_startup_nrf52.S.

The process of compiling and linking are successful, .hex file was also generated, it sounds good. 

But when we loaded the .hex file generated by KEIL compiler, the application couldn't work.
We found the application was loaded in bootloader area, althoungh we didn't download any bootloader file to chip.

We checked the .map file, it showed all address information are same with we has set. 

Here are some detail figures to explain what happened:

Options for keil:

the .map file:


Thanks for your answer.

[Henry_Chou]

May you try the nRF connect programer for your case?

Actually the MBR(Boot load) , SD (softdevice) ,App (main code) should arrange like above.

If the app hex code is normal the address offset should be 0x29000 in your case.SD should be 0x1000.

If your case is app 0x0000, I think the keil C flash will be conflict with SD.But,....It's seems like

not happen conflict? How?....

The direct way to debug, You may check the hex generate by keil C. Make sure the address offset is 0x0000 or not.

Actually will not be 0x0000. 

[Esten]

Thanks henry.
The cause looks easy to know...
Although all source files are same with gcc project, the output hex file is regarded as a BOOTLOADER type, not applicaition type.
 What can cause the issue when using keil dev situation, or which configuration will cause a app regarded as a bootloader. What is the difference between bootloader and application when generating the goal file?

[Henry_Chou]

In my experience, the easy way to transfer the project code from SES or Iar to keil C. You may take care the project option such as memory allocation, the definition parameter,  device family pack, and device startup assembly code( **starup** .s)

For some reason, you may copy the example project (keil) . Then modify which you want. It's the best way.

[Esten]

Maybe the method is more reliable.
Why the application file regarded as a bootloader type, do you have any idea?
What parameters or configuration will cause this?

[Henry_Chou]

Hex code format will not be include the memory type. If the debug tools, it is located at 0x0000. That means, Finally the hex file start address offset is wrong. The reason usual is the memory map definition. SES is depend on ld file. The Keil C is decided by project file. Even thought, your map file is okaye. But I think that it must be something wrong from your project file or startup .s file.