Segger Embedded Studio: Debug and Release build configurations

RE: Segger Embedded Studio: Debug and Release build configurations

Kenneth — Mon, 28 Mar 2022 13:43:30 GMT

I just opened the nrf_desktop example I referenced and it seems to work here, I did however use NCS v1.7.1.

Kenneth

RE: Segger Embedded Studio: Debug and Release build configurations

Learner — Mon, 28 Mar 2022 12:48:03 GMT

I am using nRF Connect SDK v1.7.0. Zephyr OS build v2.6.99-ncs1
and SES-Nordic Edition v5.60

SEGGER Embedded Studio for ARM
Release 5.60 Build 2021081102.47262
Nordic Edition
Windows x64

© 2014-2021 SEGGER Microcontroller GmbH
© 1997-2021 Rowley Associates Ltd.

segger-as: version 2.11
segger-cc: version 12.2.1
segger-cc-ng: version 12.91.6
segger-ld: version 4.12.1
segger-rtl: version 2.22.0

Thank you for your support.

Kind regards

Mohamed

RE: Segger Embedded Studio: Debug and Release build configurations

Kenneth — Mon, 28 Mar 2022 09:32:13 GMT

Which version of NCS are you working on, and are you using the SES that is bundled with the NCS release or a newer one?

Kenneth

RE: Segger Embedded Studio: Debug and Release build configurations

Learner — Mon, 28 Mar 2022 08:55:49 GMT

Thank you Kenneth.

I should be able to build different build configurations in SES e.g. 'debug' or 'release'

Build > Build Configurations...

However, when I try to do this SES stop responding to any subsequent key presses. I have to press the ESC key to get SES to escape from this strange mode. However, this also means I escaped the Build Configurations... menu. So, I cannot build configurations. The only one available is the default Common configuration shown in the top left hand side above the Project explorer in SES IDE.

Kind regards

Mohamed

RE: Segger Embedded Studio: Debug and Release build configurations

Kenneth — Wed, 16 Mar 2022 14:08:53 GMT

If you take a random application example, e.g. nRF Desktop which have a lot of build types:
nrf\applications\nrf_desktop

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/nrf_desktop/README.html#selecting-a-build-type
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/nrf_desktop/README.html#nrf-desktop-requirements-build-types

Does that work as you expect? I don't understand what problems you may have, since there are examples that already does this that you should be able to compare with.

Kenneth

RE: Segger Embedded Studio: Debug and Release build configurations

Learner — Wed, 16 Mar 2022 14:01:22 GMT

Hi Kenneth,

Maybe I did not make myself very clear in my previous message.

I inherited the CMakelists.txt from a colleague not from ncs.

I would appreciate it a great deal if you could address the following:

I still cannot create debug and release configurations in SES. I asked this question over a year ago in this ticket but I still don't know how to do it. Can you help?

Kind regards

Mohamed

RE: Segger Embedded Studio: Debug and Release build configurations

Kenneth — Wed, 16 Mar 2022 13:55:31 GMT

I searched through all the CMakeLists.txt in ncs, and I could not find these lines used anywhere, do you know where you have gotten these lines of code? In any case, I suggest to remove them and follow the description in the documentation how to set build type.

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/gs_modifying.html#configuring-build-types

RE: Segger Embedded Studio: Debug and Release build configurations

Learner — Tue, 15 Mar 2022 14:50:33 GMT

Hi Kenneth,

Thank you for your on-going support. I do appreciate it.

I have found the root cause of my problem. It is self-inflicted.

I inherited a CMakelists.txt and in there I found these configuration lines,

if (NOT CMAKE_BUILD_TYPE)
set(CMAKE_BUILD_TYPE debug)
endif()

# Set main PID4 configuration file
set(CONF_FILE "${CMAKE_CURRENT_LIST_DIR}/prj_${CMAKE_BUILD_TYPE}.conf")

So, it was always the prj_debug.conf that was used. It seems the content of the CMakelists.txt overrides whatever I specify in SES using -DCONF_FILE=....

Tools > Options > nRF Connect then added -DCONF_FILE=prj_release.conf

Now, I just change the line highlighted in yellow above to switch between debug and release configuration.

However, I still cannot create debug and release configurations in SES. I asked the question over a year ago in this ticket but I still don't know how to do it. Can you hel?

Kind regards

Mohamed

RE: Segger Embedded Studio: Debug and Release build configurations

Kenneth — Mon, 14 Mar 2022 08:48:50 GMT

Have you tried (at least for testing) to compile your project from command line using west and/or visual studio code? That can at least provide information if the issue is related to SES or not.

Kenneth

RE: Segger Embedded Studio: Debug and Release build configurations

Learner — Wed, 09 Mar 2022 15:06:31 GMT

Yes, I have but no success still.

In SES I did

Tools > Options > nRF Connect then added -DCONF_FILE=prj_release.conf

File > Open nRF Connect SDK Project... to re-open the project

Then did a new build in a new empty build folder but the .config file is still not being updated with my config that is in prj_release.conf.

For example I set CONFIG_LOG=n in prj_release.conf but in .config in the new build folder I see CONFIG_LOG=y.

I then ran Cmake, as you suggested,

Project > Run CMake

But nothing has changed in the .config file, see extract from the log trace below,

Creating solution HomeBeacon_dev_sb.emProject
-- Application: C:/Sandbox/HomeBeacon_dev_sb
-- Zephyr version: 2.6.99 (C:/Zypher/v1.7.0/zephyr), build: v2.6.99-ncs1
-- Found west (found suitable version "0.11.1", minimum required is "0.7.1")
-- Board: nrf52833dk_nrf52833
-- Cache files will be written to: C:/Zypher/v1.7.0/zephyr/.cache
-- Found dtc: C:/Zypher/v1.7.0/toolchain/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (C:/Zypher/v1.7.0/toolchain/opt)
-- Found BOARD.dts: C:/Zypher/v1.7.0/zephyr/boards/arm/nrf52833dk_nrf52833/nrf52833dk_nrf52833.dts
-- Found devicetree overlay: C:/Sandbox/HomeBeacon_dev_sb/nrf52833dk_nrf52833.overlay
-- Generated zephyr.dts: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1399_cmake/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1399_cmake/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1399_cmake/zephyr/include/generated/device_extern.h
-- Including generated dts.cmake file: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1399_cmake/zephyr/dts.cmake
Parsing C:/Sandbox/HomeBeacon_dev_sb/Kconfig
Loaded configuration 'C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1399_cmake/zephyr/.config'
No change to configuration in 'C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1399_cmake/zephyr/.config'
No change to Kconfig header in 'C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1399_cmake/zephyr/include/generated/autoconf.h'
-- Application: C:/Zypher/v1.7.0/bootloader/mcuboot/boot/zephyr
-- Zephyr version: 2.6.99 (C:/Zypher/v1.7.0/zephyr), build: v2.6.99-ncs1
-- Found west (found suitable version "0.11.1", minimum required is "0.7.1")
-- Board: nrf52833dk_nrf52833
-- Cache files will be written to: C:/Zypher/v1.7.0/zephyr/.cache
-- Found dtc: C:/Zypher/v1.7.0/toolchain/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (C:/Zypher/v1.7.0/toolchain/opt)
-- Found BOARD.dts: C:/Zypher/v1.7.0/zephyr/boards/arm/nrf52833dk_nrf52833/nrf52833dk_nrf52833.dts
-- Found devicetree overlay: C:/Zypher/v1.7.0/bootloader/mcuboot/boot/zephyr/dts.overlay
-- Found devicetree overlay: C:/Zypher/v1.7.0/bootloader/mcuboot/boot/zephyr/dts.overlay
-- Generated zephyr.dts: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1399_cmake/mcuboot/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1399_cmake/mcuboot/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1399_cmake/mcuboot/zephyr/include/generated/device_extern.h
-- Including generated dts.cmake file: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1399_cmake/mcuboot/zephyr/dts.cmake
Parsing C:/Zypher/v1.7.0/bootloader/mcuboot/boot/zephyr/Kconfig
Loaded configuration 'C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1399_cmake/mcuboot/zephyr/.config'
No change to configuration in 'C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1399_cmake/mcuboot/zephyr/.config'
No change to Kconfig header in 'C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1399_cmake/mcuboot/zephyr/include/generated/autoconf.h'
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1399_cmake/mcuboot
Partition 'mcuboot' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_pad' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_primary' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_primary_app' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_secondary' is not included in the dynamic resolving since it is statically defined.
Dropping partition 'nvs_storage' since its size is 0.
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1399_cmake
Including boilerplate (Zephyr base (cached)): C:/Zypher/v1.7.0/zephyr/cmake/app/boilerplate.cmake
-- Using NCS Toolchain 1.7.0 for building. (C:/Zypher/v1.7.0/toolchain/cmake)

=== child image mcuboot - begin ===
Including boilerplate (Zephyr base (cached)): C:/Zypher/v1.7.0/zephyr/cmake/app/boilerplate.cmake
-- Using NCS Toolchain 1.7.0 for building. (C:/Zypher/v1.7.0/toolchain/cmake)
MCUBoot bootloader key file: C:/Zypher/v1.7.0/bootloader/mcuboot/root-rsa-2048.pem
=== child image mcuboot - end ===

CMake Warning at C:/Zypher/v1.7.0/nrf/modules/mcuboot/CMakeLists.txt:204 (message):

---------------------------------------------------------
--- WARNING: Using default MCUBoot key, it should not ---
--- be used for production. ---
---------------------------------------------------------

Loading solution HomeBeacon_dev_sb.emProject
Loading solution build.emProject
Mapping project information
Mapping project zephyr/merged.hex
Mapping project all

...

Let me know if you would like to see the whole trace.

Kind regards

Mohamed

RE: Segger Embedded Studio: Debug and Release build configurations

Kenneth — Wed, 09 Mar 2022 14:26:33 GMT

Have you tried the other option also?
- Run Cmake with Project > Run CMake.

Kenneth

RE: Segger Embedded Studio: Debug and Release build configurations

Learner — Wed, 09 Mar 2022 14:02:41 GMT

Hi Kenneth,

Thank you for your answers.

[quote userid="2111" url="~/f/nordic-q-a/66226/segger-embedded-studio-debug-and-release-build-configurations/357171#357171"]I am not sure why the documentation says not to choose clean build directory, unless there are some configurations you have set using menuconfig in SES that you may want to keep. [/quote]

I am not aware of any configurations I have in SES that I would like to keep.

How do I check whether I have configurations set in SES using menuconfig?

[quote userid="2111" url="~/f/nordic-q-a/66226/segger-embedded-studio-debug-and-release-build-configurations/357171#357171"]

> When I open the project after performing the actions in Q2/ above, I see in SES logs that prj_debug.conf is being merged instead of prj_release.conf as specified in -DCONF_FILE=prj_release.conf

This is likely because you don't clean the build folder and/or CMake does not run.

[/quote]

I have tried both with and without selecting the 'Clean Build folder' option and I still see prj_debug.conf instead of prj_release.conf being merged in .config. as reported in my previous post.

Kind regards

Mohamed

RE: Segger Embedded Studio: Debug and Release build configurations

Kenneth — Wed, 09 Mar 2022 13:17:48 GMT

Hi,

I am not sure why the documentation says not to choose clean build directory, unless there are some configurations you have set using menuconfig in SES that you may want to keep.

> What is the difference between re-opening and re-loading a project?

If you close and open the same project with "clean build directory" not chosen, then this can cause items from the cache/build folder to impact configuration, and that changes in prj.conf. cmakelist.txt is not applied. To ensure the changes are applied then CMake must run, which can be done by either of the following:

- Open the project again with "Open nRF Connect SDK project", make sure to choose "clean build directory".

- Run Cmake with Project > Run CMake.

> When I open the project after performing the actions in Q2/ above, I see in SES logs that prj_debug.conf is being merged instead of prj_release.conf as specified in -DCONF_FILE=prj_release.conf

This is likely because you don't clean the build folder and/or CMake does not run.

If you reload the project with Project > Reload <project name>, then CMake does not run.

Best regards,
Kenneth

RE: Segger Embedded Studio: Debug and Release build configurations

Learner — Wed, 09 Mar 2022 09:26:38 GMT

Good morning Kenneth,

I appreciate you are trying to get me to migrate to VS Code but unfortunately, the team and management are reluctant to make the switch right now. So, we need to get this sorted as soon as possible. If you cannot solve this problem maybe you can consult with other members in your team.

These are the outstanding questions I would like help with.

Q1/

[quote userid="92434" url="~/f/nordic-q-a/66226/segger-embedded-studio-debug-and-release-build-configurations/356975#356975"]

From the link you sent me, it is stated in step 4 Do not select Clean Build Directory.

Why is this the case?

[/quote]

Q2/

[quote userid="2111" url="~/f/nordic-q-a/66226/segger-embedded-studio-debug-and-release-build-configurations/355585#355585"]That said, the description for SES should be as stated here (seems there are two different ways it can be done in SES if you see the Note also below the first suggestion): https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/gs_modifying.html?highlight=dconf_file#selecting-a-build-type-in-ses [/quote]

If I choose to select the project conf file using the second method as shown below

Tools > Options > nRF Connect > Additional CMake Options -DCONF_FILE=prj_release.conf

File > Open nRF Connect SDK Project... to re-open the project

Can I select to do a 'Clean Build Directory'?

Q3/

What is the difference between re-opening and re-loading a project?

Q4/ When I open the project after performing the actions in Q2/ above, I see in SES logs that prj_debug.conf is being merged instead of prj_release.conf as specified in -DCONF_FILE=prj_release.conf. See logs below.

Creating solution HomeBeacon_dev_sb.emProject C:/Zypher/v1.7.0/toolchain/opt/bin/cmake.exe -GNinja -DBOARD=nrf52833dk_nrf52833 -DBOARD_DIR=C:\Zypher\v1.7.0\zephyr\boards\arm\nrf52833dk_nrf52833 -BC:\Sandbox\HomeBeacon_dev_sb\build_nrf52833dk_nrf52833_rel_v1_3_99 -SC:\Sandbox\HomeBeacon_dev_sb -DNCS_TOOLCHAIN_VERSION=1.7.0 -DCONF_FILE=prj_release.conf -DDTC_OVERLAY_FILE=C:/Sandbox/HomeBeacon_dev_sb/nrf52833dk_nrf52833.overlay -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=C:\Zypher\v1.7.0\toolchain\segger_embedded_studio/html/configure_nordic_project_menuconfig.py
-- Application: C:/Sandbox/HomeBeacon_dev_sb
-- Zephyr version: 2.6.99 (C:/Zypher/v1.7.0/zephyr), build: v2.6.99-ncs1
-- Found Python3: C:/Zypher/v1.7.0/toolchain/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter
-- Found west (found suitable version "0.11.1", minimum required is "0.7.1")
-- Board: nrf52833dk_nrf52833
-- Cache files will be written to: C:/Zypher/v1.7.0/zephyr/.cache
-- Found dtc: C:/Zypher/v1.7.0/toolchain/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (C:/Zypher/v1.7.0/toolchain/opt)
-- Found BOARD.dts: C:/Zypher/v1.7.0/zephyr/boards/arm/nrf52833dk_nrf52833/nrf52833dk_nrf52833.dts
-- Found devicetree overlay: C:/Sandbox/HomeBeacon_dev_sb/nrf52833dk_nrf52833.overlay
-- Generated zephyr.dts: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1_3_99/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1_3_99/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1_3_99/zephyr/include/generated/device_extern.h
-- Including generated dts.cmake file: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1_3_99/zephyr/dts.cmake
Parsing C:/Sandbox/HomeBeacon_dev_sb/Kconfig
Loaded configuration 'C:/Zypher/v1.7.0/zephyr/boards/arm/nrf52833dk_nrf52833/nrf52833dk_nrf52833_defconfig'
Merged configuration 'C:/Sandbox/HomeBeacon_dev_sb/prj_debug.conf'
Configuration saved to 'C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1_3_99/zephyr/.config'
Kconfig header saved to 'C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_rel_v1_3_99/zephyr/include/generated/autoconf.h'

...

Kind regards

Mohamed

RE: Segger Embedded Studio: Debug and Release build configurations

Kenneth — Wed, 09 Mar 2022 08:26:53 GMT

Can you please try building from command line using west and/or transition to Visual Studio code?

Best regards,
Kenneth

RE: Segger Embedded Studio: Debug and Release build configurations

Learner — Tue, 08 Mar 2022 17:42:46 GMT

Hi Kenneth,

From the link you sent me, it is stated in step 4 Do not select Clean Build Directory.

Why is this the case?

I thought starting with a clean build folder is often if not always good practice.

Please clarify.

Thank you.

Kind regards

Mohamed

RE: Segger Embedded Studio: Debug and Release build configurations

Learner — Tue, 01 Mar 2022 14:58:41 GMT

devzone.nordicsemi.com/.../SES_5F00_Creating_5F00_Solution_5F00_Log.txt devzone.nordicsemi.com/.../SES_5F00_Building_5F00_Solution_5F00_Log.txt

Thank you Kenneth.

"You can also specify the build type in the Additional CMake Options field in Tools > Options > nRF Connect. However, the changes will only be applied after re-opening the project. Reloading the project is not sufficient."

I am not sure what the difference is between re-opening and re-loading a project.

In SES I did

Tools > Options > nRF Connect then added -DCONF_FILE=prj_release.conf

File > Open nRF Connect SDK Project... to re-open the project

Then did a new build in a new empty build folder but the .config file is still not being updated with my config that is in prj_release.conf.

For example I set CONFIG_LOG=n in prj_release.conf but in .config in the new build folder I see CONFIG_LOG=y.

Looking closely at the logs when opening the project and creating the solution I can see that it is the content of prj_debug.conf that is merged in the configuration NOT prj_release.conf as expected. This is despite the fact that the cmake.exe command line includes -DCONF_FILE=prj_release.conf.

Creating solution HomeBeacon_dev_sb.emProject
C:/Zypher/v1.7.0/toolchain/opt/bin/cmake.exe -GNinja -DBOARD=nrf52833dk_nrf52833 -DBOARD_DIR=C:\Zypher\v1.7.0\zephyr\boards\arm\nrf52833dk_nrf52833 -BC:\Sandbox\HomeBeacon_dev_sb\build_nrf52833dk_nrf52833_release -SC:\Sandbox\HomeBeacon_dev_sb -DNCS_TOOLCHAIN_VERSION=1.7.0 -DCONF_FILE=prj_release.conf -DDTC_OVERLAY_FILE=C:/Sandbox/HomeBeacon_dev_sb/nrf52833dk_nrf52833.overlay -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=C:\Zypher\v1.7.0\toolchain\segger_embedded_studio/html/configure_nordic_project_menuconfig.py
-- Application: C:/Sandbox/HomeBeacon_dev_sb
-- Zephyr version: 2.6.99 (C:/Zypher/v1.7.0/zephyr), build: v2.6.99-ncs1
-- Found Python3: C:/Zypher/v1.7.0/toolchain/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter 
-- Found west (found suitable version "0.11.1", minimum required is "0.7.1")
-- Board: nrf52833dk_nrf52833
-- Cache files will be written to: C:/Zypher/v1.7.0/zephyr/.cache
-- Found dtc: C:/Zypher/v1.7.0/toolchain/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (C:/Zypher/v1.7.0/toolchain/opt)
-- Found BOARD.dts: C:/Zypher/v1.7.0/zephyr/boards/arm/nrf52833dk_nrf52833/nrf52833dk_nrf52833.dts
-- Found devicetree overlay: C:/Sandbox/HomeBeacon_dev_sb/nrf52833dk_nrf52833.overlay
-- Generated zephyr.dts: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_release/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_release/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_release/zephyr/include/generated/device_extern.h
-- Including generated dts.cmake file: C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_release/zephyr/dts.cmake
Parsing C:/Sandbox/HomeBeacon_dev_sb/Kconfig
Loaded configuration 'C:/Zypher/v1.7.0/zephyr/boards/arm/nrf52833dk_nrf52833/nrf52833dk_nrf52833_defconfig'
Merged configuration 'C:/Sandbox/HomeBeacon_dev_sb/prj_debug.conf'
Configuration saved to 'C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_release/zephyr/.config'
Kconfig header saved to 'C:/Sandbox/HomeBeacon_dev_sb/build_nrf52833dk_nrf52833_release/zephyr/include/generated/autoconf.h'

Please explain what is going on here and help sort this problem out.

Thank you.

Kind regards

Mohamed

RE: Segger Embedded Studio: Debug and Release build configurations

Kenneth — Tue, 01 Mar 2022 14:11:27 GMT

Migrating is very easy:
https://www.youtube.com/watch?v=ptJBEAOIm5w&list=PLx_tBuQ_KSqEt7NK-H7Lu78lT2OijwIMl&index=6

That said, the description for SES should be as stated here (seems there are two different ways it can be done in SES if you see the Note also below the first suggestion): https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/gs_modifying.html?highlight=dconf_file#selecting-a-build-type-in-ses

Best regards,
Kenneth

RE: Segger Embedded Studio: Debug and Release build configurations

Learner — Tue, 01 Mar 2022 12:37:24 GMT

Hi Kenneth,

Thank you for your response but that is not the answer I was hoping for.

Switching IDE at this critical time in the development phase of the project is not an option.

I am aware of the "cache" problem SES suffers from so, I do reload the project after each mod to prj.conf.

Can you please try to find out how I can build a debug and a release version of my project under SES. I would like to be able to achieve this using two project configuration files, prj_debug.conf and prj_release.conf. Note, since I initially submitted this ticket I have moved to a new SES version,

Thank you for your support.

Kind regards

Mohamed

RE: Segger Embedded Studio: Debug and Release build configurations

Kenneth — Tue, 01 Mar 2022 12:02:51 GMT

I suggest to use Visual Studio Code instead of SES, I know that SES may "cache" some of the configuration unless you re-open the project in SES after doing modifications to prj conf files.

Kenneth

RE: Segger Embedded Studio: Debug and Release build configurations

Learner — Tue, 01 Mar 2022 09:13:08 GMT

How can I check if my project configurations have been applied?

Also, are the quotation marks " " necessary?

I built a debug version of my project using prj_debug.conf and a release version using prj_release.conf in two different build folders but when I compare the debug and release .config files I find they are identical. I disabled logs in the release build CONFIG_LOG=n but in it is set to 'y' in .config.

This is not what I was expecting. What am I doing wrong?

Kind regards

Mohamed

RE: Segger Embedded Studio: Debug and Release build configurations

Kenneth — Tue, 01 Mar 2022 08:14:12 GMT

Not tried it myself, but you can try -DCONF_FILE="prj_1.conf prj_2.conf prj_3.conf"

RE: Segger Embedded Studio: Debug and Release build configurations

Learner — Mon, 28 Feb 2022 17:41:33 GMT

Hi Kenneth,

[quote userid="2111" url="~/f/nordic-q-a/66226/segger-embedded-studio-debug-and-release-build-configurations/301449#301449"]ou may find this useful:
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/gs_modifying.html#selecting-a-build-type-in-ses [/quote]

Is it possible to specify more than one prj.conf file via the 'Extended Settings' in the field 'Extra CMake Build Options'. If yes, then what is the syntax?

-DCONF_FILE=prj_1.conf prj_2.conf prj_3.conf

-DCONF_FILE=prj_1.conf -DCONF_FILE=prj_2.conf -DCONF_FILE=prj_3.conf

Thank you.

Kind regards

Mohamed

RE: Segger Embedded Studio: Debug and Release build configurations

Learner — Tue, 23 Mar 2021 21:37:56 GMT

Hi Kenneth,

I've had a look but it looks rather convoluted. Maybe because I am used to setting build configurations from within the IDE I am using for development and debugging. So, it would be great if you could get this information. Otherwise I will just carry on using the two prj-xxx.conf files.

Thank you.

Kind regards

Mohamed

RE: Segger Embedded Studio: Debug and Release build configurations

Kenneth — Tue, 23 Mar 2021 16:57:54 GMT

Isn't this also described in the same page?
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/gs_modifying.html#creating-build-type-files