Using CONFIG_DEBUG_OPTIMIZATIONS with Thingy:91 and Asset Tracker v2

RE: Using CONFIG_DEBUG_OPTIMIZATIONS with Thingy:91 and Asset Tracker v2

Edvin — Wed, 27 Mar 2024 14:32:58 GMT

Hello,

Håkon is out of office, so I will look into your ticket. Please note that I will be out of office as well from tomorrow, due to public holidays here in Norway. We will be back on April 2nd. I am sorry for the inconvenience.

What do you mean by "implement the two stage build with west build"? And what is "awk" and "sed"?

If you are talking about having two different build configurations, you can use different sets of .conf files. Alternatively, you can include configs in your west build command. E.g. if you want to add a config like:

CONFIG_BT=y

You can use the build command:

west build -b <board> -d <build_dir> -- -DCONFIG_BT=y

For several sets of build commands, please see the ncs\nrf\applications\matter_weather_station as an example. It has prj.conf and prj_release.conf. So you can build with one or the other. By changing the name of the build folder, you can have many concurrent builds in your application.

Best regards,

Edvin

RE: Using CONFIG_DEBUG_OPTIMIZATIONS with Thingy:91 and Asset Tracker v2

Cambridge_dev — Fri, 22 Mar 2024 14:20:17 GMT

It built and ran when I followed your instructions carefully :- )

I'm creating bash scripts to automate building different versions e.g debug, lowpower

Could you suggest how I could implement the two stage build with west build ?

I can use sed or awk to modify the .config file between the two build steps, but I'm not sure what arguments to give west build to replicate the vscode workflow.

RE: Using CONFIG_DEBUG_OPTIMIZATIONS with Thingy:91 and Asset Tracker v2

Håkon Alseth — Fri, 22 Mar 2024 11:03:25 GMT

Hi,

[quote user="Cambridge_dev"]

Doing as you suggest does let me build an image with debug optimisations - thanks !

However, when I flash that image to the board it doesn't run the Asset Tracker app. When I try a debugging session with this image the console gives me:

[/quote]

You will need to build the whole project and flash the merge.hex file afterwards, as this changes your application. I suspect that you only updated the zephyr/zephyr.hex, while you should have flashed the zephyr/merged.hex to successfully get it to run.

[quote user="Cambridge_dev"]

I've also tried to define a custom partition map that gives tfm more space, by creating a pm_static.yml file from the partitions.yml file in the build directory.

But the build doesn't pick this up, and continues to use thingy91_pm_static.yml from the SDK.

How can I get the build to use my partition file ?

[/quote]

This is the main issue with using thingy91 as a development platform - it isn't targeted as a full development kit, rather a prototyping platform device.

The .yml file is set in the board itself, more specifically here: https://github.com/nrfconnect/sdk-nrf/blob/v2.5.2/boards/arm/thingy91_nrf9160/CMakeLists.txt#L26

You will need to add your changes to the thingy91_pm_static.yml file, or change the thingy91_nrf9160 board to not load the default board .yml file.

Kind regards,

Håkon

RE: Using CONFIG_DEBUG_OPTIMIZATIONS with Thingy:91 and Asset Tracker v2

Cambridge_dev — Fri, 22 Mar 2024 08:04:16 GMT

I've also tried to define a custom partition map that gives tfm more space, by creating a pm_static.yml file from the partitions.yml file in the build directory.

But the build doesn't pick this up, and continues to use thingy91_pm_static.yml from the SDK.

How can I get the build to use my partition file ?

Thanks again.

RE: Using CONFIG_DEBUG_OPTIMIZATIONS with Thingy:91 and Asset Tracker v2

Cambridge_dev — Thu, 21 Mar 2024 16:58:43 GMT

Doing as you suggest does let me build an image with debug optimisations - thanks !

However, when I flash that image to the board it doesn't run the Asset Tracker app. When I try a debugging session with this image the console gives me:

JLinkGDBServerCLexe: SEGGER J-Link GDB Server V7.94e Command Line Version
JLinkGDBServerCLexe:
JLinkGDBServerCLexe: JLinkARM.dll V7.94e (DLL compiled Jan 15 2024 15:13:39)
JLinkGDBServerCLexe:
JLinkGDBServerCLexe: -----GDB Server start settings-----
JLinkGDBServerCLexe: GDBInit file: none
JLinkGDBServerCLexe: GDB Server Listening port: 58700
JLinkGDBServerCLexe: SWO raw output listening port: 2332
JLinkGDBServerCLexe: Terminal I/O port: 2333
JLinkGDBServerCLexe: Accept remote connection: yes
JLinkGDBServerCLexe: Generate logfile: off
JLinkGDBServerCLexe: Verify download: off
JLinkGDBServerCLexe: Init regs on start: off
JLinkGDBServerCLexe: Silent mode: on
JLinkGDBServerCLexe: Single run mode: on
JLinkGDBServerCLexe: Target connection timeout: 0 ms
JLinkGDBServerCLexe: ------J-Link related settings------
JLinkGDBServerCLexe: J-Link Host interface: USB
JLinkGDBServerCLexe: J-Link script: none
JLinkGDBServerCLexe: J-Link settings file: none
JLinkGDBServerCLexe: ------Target related settings------
JLinkGDBServerCLexe: Target device: cortex-m33
JLinkGDBServerCLexe: Target device parameters: none
JLinkGDBServerCLexe: Target interface: SWD
JLinkGDBServerCLexe: Target interface speed: 12000kHz
JLinkGDBServerCLexe: Target endian: little
JLinkGDBServerCLexe:
=thread-group-added,id="i1"
=cmd-param-changed,param="pagination",value="off"
fih_panic_loop () at /opt/nordic/ncs/v2.6.0/bootloader/mcuboot/boot/bootutil/src/fault_injection_hardening.c:68
68 __asm volatile ("b fih_panic_loop");
[New Thread 1879048192]

and I can't stop the code at breakpoints. If i use an image without DEBUG_OPTIMISATION the debugger works as expected. Looks like the boot process is broken....

RE: Using CONFIG_DEBUG_OPTIMIZATIONS with Thingy:91 and Asset Tracker v2

Håkon Alseth — Thu, 21 Mar 2024 14:33:33 GMT

Hi,

If you add CONFIG_DEBUG_OPTIMIZATIONS=y in your prj.conf, TF-M will also be compiled with debug optimizations, which will cause the partition size to be exceeded.

thingy91_nrf9160_ns will follow this specific partition layout: https://github.com/nrfconnect/sdk-nrf/blob/v2.5.2/boards/arm/thingy91_nrf9160/thingy91_pm_static.yml

One way around this is to configure your project with CONFIG_SIZE_OPTIMIZATIONS, and afterwards go into menuconfig and change the application's optimization level. This will cause TF-M to be left with the default optimization, and only set DEBUG_OPTIMIZATION for the asset tracker v2.

You can do this via vscode nRF Kconfig GUI or manually edit and save the .config file:

The .config file is located in ../asset_tracker_v2/my-build-folder/zephyr/.config - Search for "CONFIG_SIZE_OPTIMIZATION" and comment out this with a "#" and then add CONFIG_DEBUG_OPTIMIZATIONS=y and then press "build" in vscode.

Kind regards,

Håkon