Memory report fails

RE: Memory report fails

ColinC — Tue, 28 Jan 2025 12:10:07 GMT

Alright, thanks for the update!

RE: Memory report fails

droberson — Tue, 28 Jan 2025 00:49:31 GMT

For anyone else that comes across this in the future, the specific failure case I encountered was just fixed.

Amanda replied to my private ticket and said "It's fixed by the Build 2025.1.127 which is now published". She is referring to the nRF Connect VS Code extension (plugin).

You can see the release notes here:

https://docs.nordicsemi.com/bundle/nrf-connect-vscode/page/release_notes/connect/2024.12.55.html#bug-fixes

Specifically:

"Fixed an issue with using the correct west command to generate the memory report".

+ ColinC

RE: Memory report fails

ColinC — Thu, 23 Jan 2025 08:23:24 GMT

Hi Derek,

Like you, I am not quite sure how to set the Terminal profile and in which context exactly the Memory report gets executed. In my case, deleting the unused SDK helped set the Terminal Profile to using the correct toolchain.

Especially the documentation on how the `nrf-connect.terminalProfile.shell` setting works is unclear to me. But I think it could be an interessting option for the users who don't want to remove SDKs and Toolchains to get the correct Terminal Profile.

Greetings

Colin

RE: Memory report fails

droberson — Wed, 22 Jan 2025 18:14:17 GMT

Hey Amanda Hsieh

I see that the original poster has closed this ticket. Should I create a new public ticket to track the specific failure I observed? Although similar, I guess it was different from the original poster's failure case.

Thanks,

Derek

RE: Memory report fails

droberson — Wed, 22 Jan 2025 16:54:48 GMT

Hey Colin,

I appreciate the feedback and have reviewed the documentation, but it isn't clear to me what configuration I am supposed to set to force the "Memory report" tool to use a terminal profile that matches the SDK and toolchain of the build configuration. I know how to open a terminal that matches my toolchain and SDK, but the "Memory report" tool still does not use it and continues to generate the error "Failed to generate memory reports".

It would seem that nRF Connect SDK and the "Memory report" tool should use the terminal profile that matches the build configuration of the project by default, but it doesn't.

Thanks,

Derek

RE: Memory report fails

ColinC — Wed, 22 Jan 2025 15:07:53 GMT

Hi, I encountered the same problem as you with the same failure message.

I am developping firmware with SDK v2.7.0 and Toolchain v2.7.0. They are setup correctly in the build configuration and compiling works out smoothly.

I noticed that under "Manage Toolchain" in the Welcome tab, the terminal profile was set to the nRF Connect SDK Toolchain v2.8.0 as I also have SDK and Toolchain v2.8.0 installed on my computer. This was the missmatch that made the memory report fail.

I removed the SDK and Toolchain v2.8.0, and the Toolchain in the Terminal Profile was set to V2.7.0 since it was the only Toolchain I had installed.

From what I understand, when external tools like the memory report are executed, the terminal profile is used and it does not have the same SDK and Toolchain as the build configuration.

Here are some links about Terminal Profile and ways to configure it. I hope this helps

https://docs.nordicsemi.com/bundle/nrf-connect-vscode/page/guides/extension_nrfconnect_profile.html

docs.nordicsemi.com/.../settings.html

Cheers

Colin

RE: Memory report fails

Amanda Hsieh — Fri, 17 Jan 2025 20:07:17 GMT

The team is looking into the issue. I will update the case if we find anything.

RE: Memory report fails

droberson — Fri, 17 Jan 2025 17:24:38 GMT

For anyone that comes across this ticket or is subscribed for updates, Amanda replied to my private case yesterday, 1/16/2025, with the following:

"Thanks for the report. I have forwarded it to the team to investigate the issue. "

Derek

RE: Memory report fails

droberson — Wed, 15 Jan 2025 22:41:50 GMT

Please see private case ID: 339104

It contains the report.

Thanks,

Derek

RE: Memory report fails

Amanda Hsieh — Wed, 15 Jan 2025 20:40:50 GMT

You can create a private case and upload it.

RE: Memory report fails

droberson — Tue, 14 Jan 2025 22:58:52 GMT

Amanda,

How can I share the support information with you securely? It contains a bunch of specific and likely sensitive information about my machine.

Thanks,

Derek

RE: Memory report fails

Amanda Hsieh — Tue, 14 Jan 2025 22:37:06 GMT

Please generate the support information by in the Welcome view and share it. Thanks.

RE: Memory report fails

droberson — Tue, 14 Jan 2025 20:35:28 GMT

Hey Amanda,

They are the same. Please reference my post above. Image copied below for easy reference:

As seen in the image, both the SDK and toolchain are set to v2.6.2.

Thanks,

Derek

RE: Memory report fails

Amanda Hsieh — Tue, 14 Jan 2025 18:51:55 GMT

Please ensure the versions of the SDK and Toolchain are the same every time before building a project.

RE: Memory report fails

droberson — Tue, 14 Jan 2025 17:52:59 GMT

Hey Amanda Hsieh

If I need to open a new ticket for this, please let me know. It isn't my intention to hijack the original posters thread, but I believe they may be encountering the same issue I am seeing. My goal is to provide additional insight into the potential root cause.

I was able to reproduce the issue following the steps below:

1. Install nRF Connect SDK (and toolchain) v2.8.0 and then install nRF Connect SDK (and toolchain) v2.6.2 using VS Code's "Manage SDKs" and "Manage toolchains"

2. Under the nRF Connect section of VS Code (Ctrl + Alt + N), select Create a new application -> Copy a sample -> nRF Connect SDK v2.6.2 -> Blinky Sample

3. Add a build configuration for your board. I used the nrf52840dk. Make sure the SDK and toolchain are set to 2.6.2 at the top of the build configuration page. Leave all other build configuration settings at their default values.

4. Click the "Build Configuration" button and observe the output below.

* Executing task: nRF Connect: Generate config nrf52840dk_nrf52840 for c:\nRFConSDK_Train\blinky

Building blinky
<Redacted because Devzone won't post this log with this line present>

-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: C:/nRFConSDK_Train/blinky
-- CMake version: 3.21.0
-- Found Python3: C:/ncs/toolchains/cf2149caf2/opt/bin/python.exe (found suitable version "3.9.13", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: C:/ncs/v2.6.2/zephyr/.cache
-- Zephyr version: 3.5.99 (C:/ncs/v2.6.2/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: nrf52840dk_nrf52840
-- Found host-tools: zephyr 0.16.5 (C:/ncs/toolchains/cf2149caf2/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.5 (C:/ncs/toolchains/cf2149caf2/opt/zephyr-sdk)
-- Found Dtc: C:/ncs/toolchains/cf2149caf2/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found BOARD.dts: C:/ncs/v2.6.2/zephyr/boards/arm/nrf52840dk_nrf52840/nrf52840dk_nrf52840.dts
-- Generated zephyr.dts: C:/nRFConSDK_Train/blinky/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/nRFConSDK_Train/blinky/build/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: C:/nRFConSDK_Train/blinky/build/zephyr/dts.cmake
Parsing C:/ncs/v2.6.2/zephyr/Kconfig
Loaded configuration 'C:/ncs/v2.6.2/zephyr/boards/arm/nrf52840dk_nrf52840/nrf52840dk_nrf52840_defconfig'
Merged configuration 'C:/nRFConSDK_Train/blinky/prj.conf'
Configuration saved to 'C:/nRFConSDK_Train/blinky/build/zephyr/.config'
Kconfig header saved to 'C:/nRFConSDK_Train/blinky/build/zephyr/include/generated/autoconf.h'
-- Found GnuLd: c:/ncs/toolchains/cf2149caf2/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe (found version "2.38")
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/ncs/toolchains/cf2149caf2/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
-- Configuring done
-- Generating done
-- Build files have been written to: C:/nRFConSDK_Train/blinky/build
-- west build: building application
[2/139] Generating include/generated/version.h
-- Zephyr version: 3.5.99 (C:/ncs/v2.6.2/zephyr), build: v3.5.99-ncs1-2
[139/139] Linking C executable zephyr\zephyr.elf
Memory region Used Size Region Size %age Used
FLASH: 21880 B 1 MB 2.09%
RAM: 7552 B 256 KB 2.88%
IDT_LIST: 0 GB 32 KB 0.00%
* Terminal will be reused by tasks, press any key to close it.

5. Now, navigate to nRF Connect (Ctrl+Alt+N), select your build configuration, then select Memory report under "Actions" and observe the error "Failed to generate memory reports" with the the following output:

[12:15:01] nRF Command Line Tools 10.24.2 are up to date
[12:15:13] =========== Toolchain validation report for nRF Connect SDK Toolchain v2.6.2 ===========
 Using the nRF Connect SDK v2.6.2 at c:\ncs\v2.6.2
No issues were detected with the toolchain.
<Redacted because Devzone won't post this log with this line present>
[12:17:20] =========== Toolchain validation report for nRF Connect SDK Toolchain v2.6.2 ===========
 Using the nRF Connect SDK v2.6.2 at c:\ncs\v2.6.2
No issues were detected with the toolchain.
[12:17:56] Success.
[12:28:52] Command failed: west build -d c:\nRFConSDK_Train\blinky\build -t footprint
Traceback (most recent call last):
  File "C:\ncs\v2.6.2\zephyr\scripts\footprint\size_report", line 30, in <module>
    from elftools.elf.elffile import ELFFile
  File "C:\ncs\toolchains\2d382dcd92\opt\bin\Lib\site-packages\elftools\elf\elffile.py", line 41, in <module>
    from ..dwarf.dwarfinfo import DWARFInfo, DebugSectionDescriptor, DwarfConfig
  File "C:\ncs\toolchains\2d382dcd92\opt\bin\Lib\site-packages\elftools\dwarf\dwarfinfo.py", line 17, in <module>
    from .structs import DWARFStructs
  File "C:\ncs\toolchains\2d382dcd92\opt\bin\Lib\site-packages\elftools\dwarf\structs.py", line 10, in <module>
    from logging.config import valid_ident
  File "<frozen zipimport>", line 259, in load_module
  File "logging\config.py", line 30, in <module>
  File "<frozen zipimport>", line 259, in load_module
  File "logging\handlers.py", line 26, in <module>
  File "<frozen zipimport>", line 259, in load_module
  File "socket.py", line 51, in <module>
ImportError: Module use of python312.dll conflicts with this version of Python.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\2d382dcd92\opt\bin\cmake.EXE' --build 'c:\nRFConSDK_Train\blinky\build' --target footprint

Command failed: west build -d c:\nRFConSDK_Train\blinky\build -t footprint
Traceback (most recent call last):
  File "C:\ncs\v2.6.2\zephyr\scripts\footprint\size_report", line 30, in <module>
    from elftools.elf.elffile import ELFFile
  File "C:\ncs\toolchains\2d382dcd92\opt\bin\Lib\site-packages\elftools\elf\elffile.py", line 41, in <module>
    from ..dwarf.dwarfinfo import DWARFInfo, DebugSectionDescriptor, DwarfConfig
  File "C:\ncs\toolchains\2d382dcd92\opt\bin\Lib\site-packages\elftools\dwarf\dwarfinfo.py", line 17, in <module>
    from .structs import DWARFStructs
  File "C:\ncs\toolchains\2d382dcd92\opt\bin\Lib\site-packages\elftools\dwarf\structs.py", line 10, in <module>
    from logging.config import valid_ident
  File "<frozen zipimport>", line 259, in load_module
  File "logging\config.py", line 30, in <module>
  File "<frozen zipimport>", line 259, in load_module
  File "logging\handlers.py", line 26, in <module>
  File "<frozen zipimport>", line 259, in load_module
  File "socket.py", line 51, in <module>
ImportError: Module use of python312.dll conflicts with this version of Python.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\2d382dcd92\opt\bin\cmake.EXE' --build 'c:\nRFConSDK_Train\blinky\build' --target footprint

What I suspect is happening is that the Memory Report defaults to pointing to the newer 2.8.0 toolchain even though the project was built using 2.6.2. See the following lines taken from the logs above.

From the build log:

Found Python3: C:/ncs/toolchains/cf2149caf2/opt/bin/python.exe

From the memory report log:

File "C:\ncs\toolchains\2d382dcd92\opt\bin\Lib\site-packages\elftools\elf\elffile.py", line 41 ...

It appears the memory report is referencing elffile.py in toolchain directory 2d382dcd92 (presumably v2.8.0) but the build script is referencing the toolchain directory cf2149caf2 (presumably v2.6.2).

Question: Why is this happening and how can it be fixed or mitigated?

Please note I am new to Zephyr so please forgive my ignorance on how these toolchains work.

Thanks,

Derek

RE: Memory report fails

Amanda Hsieh — Fri, 10 Jan 2025 14:04:32 GMT

It seems the toolchain v2.9.0 is there. Maybe it partially failed. Try to reinstall it.

RE: Memory report fails

KentOverton — Thu, 09 Jan 2025 20:52:03 GMT

I believe they are.

Note that I tried to install 2.9.0 - but the installation failed

RE: Memory report fails

Amanda Hsieh — Thu, 09 Jan 2025 20:16:16 GMT

Hi,

[quote user=""] File "C:\ncs\v2.6.0\zephyr\scripts\footprint\size_report", line 30, in <module>[/quote][quote user=""] File "C:\ncs\toolchains\b620d30767\opt\bin\Lib\site-packages\elftools\elf\elffile.py"[/quote]

Seems you are using toolchain v2.9.0 to build SDK v2.6.0.

Please ensure the versions of the toolchain and SDK are consistent.

Regards,
Amanda H.

RE: Memory report fails

droberson — Thu, 09 Jan 2025 17:58:50 GMT

I have the same issue. I have SDK 2.8.0 and 2.6.2 installed. When I build for 2.6.2, I receive the exact same error when trying to generate a memory report (ImportError: Module use of python312.dll conflicts with this version of Python). When I build for 2.8.0, generating a memory report works fine. Figured I would report my findings here as well to corroborate your findings. Hopefully Nordic can shed some light on this.

Side note, I had to install 2.6.2 to do the Developer Academy training modules since 2.7.0+ isn't supported by some of the modules.

Derek