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

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

Esten — Sat, 31 Oct 2020 07:25:15 GMT

[quote userid="8164" url="~/f/nordic-q-a/67699/app-hex-was-loaded-in-bootloader-area-when-using-keil-compiling/277575#277575"]may[/quote]

Thanks for your answer.
The reason is the project included bootloader setting file.
It is compiled with IROM1 BASE ADDRESS within KEIL project, but it does not take effect within GCC project.

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

tesc — Thu, 29 Oct 2020 10:51:37 GMT

Hi,

Can you do a flash erase before programming both SoftDevice and Application?

The fact that the programmer tools says it is the bootloader region may come from a UICR register used for setting the bootloader start address. With full flash erase you also erase the UICR page.

Regarding the startup files, different toolchains have different startup files, and the change that you see of startup file is expected (and required).

In any case, porting a project to a different toolchain is often easiest if you start with a new project in the new toolchain, and then include files and include directories, set preprocessor defines and other project settings, memory settings, etc.

Regards,
Terje

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

Henry_Chou — Thu, 29 Oct 2020 04:25:49 GMT

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.

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

Esten — Thu, 29 Oct 2020 02:35:42 GMT

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?

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

Henry_Chou — Thu, 29 Oct 2020 01:39:17 GMT

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.

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

Esten — Wed, 28 Oct 2020 10:59:42 GMT

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?

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

Henry_Chou — Wed, 28 Oct 2020 08:44:09 GMT

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.