FLASH overflow when building for Thingy 53

RE: FLASH overflow when building for Thingy 53

Menon — Fri, 20 Oct 2023 04:48:25 GMT

Hello,

There might be some thingy53-specific configuration. Yes, with the updated version of NCS, I guess there is no support for thingy 53 and the TFM secure partition sample. See the supported boards section for this sample.

Kind Regards,

Abhijith

RE: FLASH overflow when building for Thingy 53

MarioDLH — Tue, 17 Oct 2023 12:54:06 GMT

Hello,

I can now see the reports but the problem is that not even the tfm secure partition sample can be built for the Thingy, as it appears to be unsupported, which is strange since it was supported in previous SDK versions and it has the same flash and RAM memory.

RE: FLASH overflow when building for Thingy 53

Menon — Tue, 17 Oct 2023 07:45:53 GMT

Hello,

Are you able to see the memory reports now? Since you are getting flash overflow and yours is a big project with TFM I would suggest to add the configuration one by one and see which configuration will fit and which one is throwing the error. There might be some Thingy specific configuration which is throwing the error. It's hard to reproduce this here (as your project is quite complex with lot of configuration).

Kind Regards,

Abhijith

RE: FLASH overflow when building for Thingy 53

MarioDLH — Fri, 13 Oct 2023 11:32:20 GMT

Hello,

I have managed to build the project properly for nRF5340DK using 2.4.0. version of the SDK, but I still face the same issue when trying to build for Thingy 53 with the same flash overflow. Is there any possible approach?
Thanks.

RE: FLASH overflow when building for Thingy 53

MarioDLH — Wed, 26 Jul 2023 10:24:06 GMT

Hello,

Sorry I was unclear about the issue. The RAM/FLASH overflow happened with previous version 2.2.0. Now using version 2.4.0 the building process doesn't reach that point, giving the error from my previous reply. When trying to generate the memory report in VSCode it just gives a fatal error without any explanation, probably because the building process failed too soon:

Command failed: west build -d c:\Users\mario\OneDrive\Escritorio\bls-hsm\remote-signer\build_1 -t footprint
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\31f4403e35\opt\bin\cmake.EXE' --build 'c:\Users\mario\OneDrive\Escritorio\bls-hsm\remote-signer\build_1' --target footprint

RE: FLASH overflow when building for Thingy 53

Menon — Tue, 25 Jul 2023 13:31:01 GMT

Hello,

It's bit hard to reproduce/debug the flash overflow error as your project seems quite big with lot of configurations. Why you are not able to generate the memory report? What is the error you are getting when trying to generate the memory report? Have you tried from the VS-code?

Kind Regards,

Abhijith

RE: FLASH overflow when building for Thingy 53

MarioDLH — Thu, 13 Jul 2023 10:12:15 GMT

Hello,

The first error I get is related to a Kconfig warning, giving this output:

warning: the hex symbol USB_DEVICE_PID (defined at C:/Users/mario/OneDrive/Escritorio/bls-hsm/remote-signer/Kconfig:4, subsys/usb/device/Kconfig:25) has a non-hex default USB_PID_CDC_ACM_SAMPLE (undefined)

error: Aborting due to Kconfig warnings

CMake Error at C:/ncs/v2.4.0/zephyr/cmake/modules/kconfig.cmake:339 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  C:/ncs/v2.4.0/nrf/cmake/modules/kconfig.cmake:29 (include)
  C:/ncs/v2.4.0/zephyr/cmake/modules/zephyr_default.cmake:115 (include)
  C:/ncs/v2.4.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/ncs/v2.4.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:97 (include_boilerplate)
  CMakeLists.txt:5 (find_package)


-- Configuring incomplete, errors occurred!

This seems to be solved assigning a hexadecimal value to that config, but then I get these errors when trying to build it again:

[6/309] Generating ../../tfm/CMakeCache.txt
FAILED: tfm/CMakeCache.txt
cmd.exe /C "cd /D C:\Users\mario\OneDrive\Escritorio\bls-hsm\remote-signer\build_2\tfm && C:\ncs\toolchains\31f4403e35\opt\bin\cmake.exe -GNinja -DTFM_TOOLCHAIN_FILE=C:/ncs/v2.4.0/modules/tee/tf-m/trusted-firmware-m/toolchain_GNUARM.cmake -DCROSS_COMPILE=C:/ncs/toolchains/31f4403e35/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi -DCMAKE_BUILD_TYPE=MinSizeRel -DTFM_PLATFORM=C:/ncs/v2.4.0/nrf/modules/tfm/tfm/boards/nrf9160 -DCONFIG_TFM_BUILD_LOG_QUIET=ON -DCONFIG_TFM_SPM_BACKEND="IPC" -DBL2=FALSE -DNS=FALSE -DTFM_ISOLATION_LEVEL=1 -DITS_MAX_ASSET_SIZE=512 -DTFM_EXCEPTION_INFO_DUMP=OFF -DTFM_PARTITION_LOG_LEVEL=TFM_PARTITION_LOG_LEVEL_SILENCE -DTFM_SPM_LOG_LEVEL=TFM_SPM_LOG_LEVEL_SILENCE -DTFM_PARTITION_NS_AGENT_MAILBOX=OFF -DTFM_PARTITION_PROTECTED_STORAGE=ON -DTFM_PARTITION_INTERNAL_TRUSTED_STORAGE=ON -DTFM_PARTITION_CRYPTO=ON -DTFM_PARTITION_PLATFORM=ON -DTFM_PARTITION_INITIAL_ATTESTATION=ON -DTFM_PARTITION_FIRMWARE_UPDATE=OFF -DCRYPTO_RNG_MODULE_DISABLED=FALSE -DCRYPTO_KEY_MODULE_DISABLED=FALSE -DCRYPTO_AEAD_MODULE_DISABLED=FALSE -DCRYPTO_MAC_MODULE_DISABLED=FALSE -DCRYPTO_HASH_MODULE_DISABLED=FALSE -DCRYPTO_CIPHER_MODULE_DISABLED=FALSE -DCRYPTO_ASYM_SIGN_MODULE_DISABLED=FALSE -DCRYPTO_ASYM_ENCRYPT_MODULE_DISABLED=FALSE -DCRYPTO_KEY_DERIVATION_MODULE_DISABLED=FALSE -DQCBOR_PATH=C:/ncs/v2.4.0/modules/tee/tf-m/trusted-firmware-m/../qcbor -DCONFIG_TFM_ENABLE_FP=OFF -DHAL_NORDIC_PATH=C:/ncs/v2.4.0/modules/hal/nordic -DNRF_ALLOW_NON_SECURE_RESET=ON -DCONFIG_TFM_HALT_ON_CORE_PANIC= -DSECURE_UART1= -DCONFIG_TFM_LOG_SHARE_UART= -DNRF_DIR=C:/ncs/v2.4.0/nrf -DZEPHYR_BASE=C:/ncs/v2.4.0/zephyr -DCRYPTO_HW_ACCELERATOR=True -DPLATFORM_DEFAULT_UART_STDOUT=OFF -DPython3_EXECUTABLE=C:/ncs/toolchains/31f4403e35/opt/bin/python.exe -DPYTHON_PREFER=C:/ncs/toolchains/31f4403e35/opt/bin/python.exe -DPROJECT_CONFIG_HEADER_FILE=C:/Users/mario/OneDrive/Escritorio/bls-hsm/remote-signer/build_2/modules/nrf/modules/tfm/zephyr/tfm_config.h -DNRF_SECURITY_SETTINGS="ZEPHYR_DOTCONFIG=C:/Users/mario/OneDrive/Escritorio/bls-hsm/remote-signer/build_2/zephyr/.config GCC_M_CPU=cortex-m33 ARM_MBEDTLS_PATH=C:/ncs/v2.4.0/modules/crypto/mbedtls ZEPHYR_AUTOCONF=C:/Users/mario/OneDrive/Escritorio/bls-hsm/remote-signer/build_2/zephyr/include/generated/autoconf.h" -DTFM_MBEDCRYPTO_CONFIG_PATH:STRING=nrf-config.h -DTFM_MBEDCRYPTO_PLATFORM_EXTRA_CONFIG_PATH:STRING=nrf-config-user.h -DTFM_EXTRA_MANIFEST_LIST_FILES=C:/Users/mario/OneDrive/Escritorio/bls-hsm/remote-signer/build_2/secure_partition/tfm_manifest_list.yaml -DTFM_EXTRA_PARTITION_PATHS=C:/Users/mario/OneDrive/Escritorio/bls-hsm/remote-signer/../secure_partition -DMBEDCRYPTO_PATH=C:/ncs/v2.4.0/nrfxlib/nrf_security/tfm -DTFM_TEST_REPO_PATH=C:/ncs/v2.4.0/modules/tee/tf-m/trusted-firmware-m/../tf-m-tests -DPSA_ARCH_TESTS_PATH=C:/ncs/v2.4.0/modules/tee/tf-m/trusted-firmware-m/../psa-arch-tests C:/ncs/v2.4.0/modules/tee/tf-m/trusted-firmware-m"
-- Found Git: C:/ncs/toolchains/31f4403e35/mingw64/bin/git.exe (found version "2.37.3.windows.1")
-- The C compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/ncs/toolchains/31f4403e35/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
-- Found Python3: C:/ncs/toolchains/31f4403e35/opt/bin/python.exe (found version "3.8.2") found components: Interpreter
Traceback (most recent call last):
File "C:/ncs/v2.4.0/modules/tee/tf-m/trusted-firmware-m/tools/tfm_parse_manifest_list.py", line 723, in <module>
main()
File "C:/ncs/v2.4.0/modules/tee/tf-m/trusted-firmware-m/tools/tfm_parse_manifest_list.py", line 711, in main
context = process_partition_manifests(manifest_lists,
File "C:/ncs/v2.4.0/modules/tee/tf-m/trusted-firmware-m/tools/tfm_parse_manifest_list.py", line 303, in process_partition_manifests
logging.info(" {:40s} ON".format(manifest_item['description']))
KeyError: 'description'
CMake Error at c:\Users\mario\OneDrive\Escritorio\bls-hsm\remote-signer\build_2\tools\CMakeLists.txt:192 (message):
Manifest tool failed to generate files!

-- Configuring incomplete, errors occurred!

(I tried to insert this output as the one above but it didn't let me do it)

I also tried to generate the memory report, but it gives an error when generating too.

RE: FLASH overflow when building for Thingy 53

Menon — Wed, 12 Jul 2023 11:33:53 GMT

Hello,

AFAIK, there is not much configuration changes with latest update (Since you are moving from NCS V2.2.0). Can you share the error logs? Please use insert tab to paste the log as it will help to read through the log easily.

Since it is a flash overflow error I am sharing few thought which could be followed for optimizing the memory:

Disabling debug and logging (you mentioned debug is not enabled).
Next I would recommend you to go through this guide which explains on optimizing the memory footprints in nRF connect SDK. See the Memory footprint optimization section inside or developer page.

You can also share the memory report of your application by using the command "nrfjprog_manager_report" or use the VScode extension for generating the same.

Kind Regards,

Abhijith

RE: FLASH overflow when building for Thingy 53

MarioDLH — Mon, 10 Jul 2023 10:53:00 GMT

Hello,

I tried building with the latest NCS version and it won't even start the bulding process, giving a configuration error at the beginning. Is it possible I need to readapt the whole project to the new version due to changes in configurations in recent NCS versions?

RE: FLASH overflow when building for Thingy 53

Menon — Thu, 06 Jul 2023 10:07:36 GMT

Hello,

[quote user="MarioDLH"]Is there anything that could fix it or has it been fixed in recent updates?[/quote]

I am not sure on this but can you try updating the NCS to latest version and see whether that fixes this issue.

Kind Regards,

Abhijith

RE: FLASH overflow when building for Thingy 53

MarioDLH — Wed, 05 Jul 2023 10:41:57 GMT

Hi.

In addition to the problem with the Thingy 53, we are also facing a similar problem when trying to build the project with additional configurations for nRF9160DK, but the issue is still related to the TFM partition, being in this case a RAM overflow. The error given says "TFM_APP_ROT_LINKER_BSS' will not fit in region `RAM'". Is there anything that could fix it or has it been fixed in recent updates?

Thanks.

RE: FLASH overflow when building for Thingy 53

MarioDLH — Wed, 28 Jun 2023 11:05:48 GMT

Hi.

Thanks for the response. Debug options is not enabled. The options used are only the necessary for the project to work properly, but it still gives the flash overflow error. I hope there is another solution.

Best regards.

RE: FLASH overflow when building for Thingy 53

Menon — Fri, 05 May 2023 13:27:14 GMT

Hey,

Sorry for the long response time I took here.

I was checking with my colleague about this issue. Are you building this with debug options Enabled? This might be the reason for TFM Image not fitting inside default flash region allocated for TF-M.

Kind Regards,

Abhijith

RE: FLASH overflow when building for Thingy 53

MarioDLH — Wed, 22 Mar 2023 10:37:18 GMT

Hello,

There are no updates yet, we're still working on this. Regarding the secure partition sample, I managed to build it following the instructions given in the mentioned ticket at the first post.

RE: FLASH overflow when building for Thingy 53

Menon — Tue, 21 Mar 2023 14:43:43 GMT

Hello,

Sorry somehow I missed this ticket. Is there any update on this issue? I tried to build the TF-M secure partition sample with Thingy53 but it is not working well. I am checking with my colleagues about this and I will get back to you.

Kind Regards,

Abhijith

RE: FLASH overflow when building for Thingy 53

MarioDLH — Fri, 24 Feb 2023 13:58:56 GMT

Hi,

The project main folder is called remote-signer, which uses secure_partition the way it's used in the zephyr tfm secure partition sample. The libraries and includes are located in libs folder. There is no need to make it private as the full project is public in github here, where there is more info about the project. If you need more information about it feel free to ask.

Best regards.

RE: FLASH overflow when building for Thingy 53

Menon — Fri, 24 Feb 2023 11:24:07 GMT

Hello,

Thank you for sharing the project. Could you give me some more context on this. May be explaining the files included in the Zip might give me some more idea. I can make the case private So that the discussion will stay with us. Please let me know if I need to do so.

Kind Regards,

Abhijith

RE: FLASH overflow when building for Thingy 53

MarioDLH — Thu, 23 Feb 2023 10:39:51 GMT

Hi,

Thanks for the support. I've attached the full project if you want to replicate the issue. In order to build it, usb.conf has to be added as a kconfig fragment. I hope it helps.

devzone.nordicsemi.com/.../bls_2D00_hsm_2D00_tfm.zip

RE: FLASH overflow when building for Thingy 53

Menon — Thu, 23 Feb 2023 10:13:33 GMT

Hello,

Letting you know I am looking into this. But I need some more time for finding the proper issue.

Thank you for understanding.

Kind Regards,

Abhijith

RE: FLASH overflow when building for Thingy 53

MarioDLH — Mon, 20 Feb 2023 11:03:22 GMT

Hi,

I'm afraid I cannot reproduce it in a minimal project as it is a problem that comes with all the source code and libraries used in the full project, which I believe causes the flash overflow for Thingy 53, but the .conf files used include these options:

CONFIG_BUILD_WITH_TFM=y

CONFIG_TFM_PROFILE_TYPE_NOT_SET=y

CONFIG_TFM_LOG_LEVEL_SILENCE=y

CONFIG_LOG=y

CONFIG_STDOUT_CONSOLE=y

CONFIG_NEWLIB_LIBC=y

#for u64 serialization

CONFIG_NEWLIB_LIBC=y

CONFIG_NEWLIB_LIBC_NANO=n

CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y

CONFIG_CJSON_LIB=y

CONFIG_MAIN_STACK_SIZE=17408

CONFIG_NORDIC_SECURITY_BACKEND=y

CONFIG_NRF_SECURITY=y

CONFIG_MBEDTLS_PSA_CRYPTO_C=y

CONFIG_PM_PARTITION_SIZE_TFM=0x60000

CONFIG_USB_DEVICE_STACK=y

CONFIG_USB_DEVICE_PRODUCT="Remote Signer"

CONFIG_USB_DRIVER_LOG_LEVEL_ERR=y

CONFIG_USB_DEVICE_LOG_LEVEL_ERR=y

CONFIG_SERIAL=y

CONFIG_UART_INTERRUPT_DRIVEN=y

CONFIG_UART_LINE_CTRL=y

If this isn't enough I could try reproducing it anyway with only the libraries and without source files but at the end all the code would be necessary and I don't think that could help. Also I tried modifying options like CONFIG_PM_PARTITION_SIZE_TFM and CONFIG_MAIN_STACK_SIZE without making any difference as I said before.

RE: FLASH overflow when building for Thingy 53

Menon — Fri, 17 Feb 2023 11:56:08 GMT

Hello,

Are you experiencing this while running the sample from SDK (ncs\v2.2.0\zephyr\samples\tfm_integration\tfm_secure_partition)?

Could you share a minimal project to reproduce this? Or please share the changes you made in the proj.config of the sample file.

Kind Regards,

Abhijith