idf.py size-components: Unexpected section name (IDFGH-6801)

[balix-microej]

Environment

• Development Kit: none
• Module or chip used: ESP32-S2
• IDF version: v4.3.2
• Build System: idf.py
• Compiler version : xtensa-esp32-elf-gcc.exe (crosstool-NG esp-2021r2) 8.4.0
• Operating System: Windows
• (Windows only) environment type: PowerShell
• Using an IDE?: No

Problem Description

Trying to get size info on the firmware produced. idf.py size works as expected but not idf.py size-components.

Expected Behavior

Print size info about components in an IDF project.

Actual Behavior

Command failed to run with the following error:

  File "C:\Users\balix\git\cc0158_enkiplatform-esp32-s2\enki-platform-esp32-s2-bsp\Drivers\esp-idf\tools\idf_size.py", line 248, in get_display_name_order
    assert len(split_name) == 3 and split_name[0] == '', 'Unexpected section name'
AssertionError: Unexpected section name
ninja: build stopped: subcommand failed.
ninja failed with exit code 1
Press any key to continue . . .

If I print the sections here is what I got:

['', 'dram0', 'data']
['', 'rtc', 'data']
['', 'dram0', 'bss']
['', 'noinit']

So I assume that this section noinit does not fit the naming scheme to be processed by this script. Is there any way I can work around this?

[dobairoland]

Hi @balix-microej. I'm sorry for the late reply. By any chance, is your project publicly available or could you share at least your MAP file from the build directory? Please be aware that the MAP file could contain sensitive information so don't share it here if it is proprietary.

As a possible fix please try to remove line no. 201:

assert len(split_name) == 3 and split_name[0] == '', 'Unexpected section name'

... and change line no. 182 from

display_name = seg_name + ('' if seg_name != 'IRAM' else split_name[1].replace('iram', '')) + f' .{split_name[2]}'

to

display_name = seg_name + ('' if seg_name != 'IRAM' else split_name[1].replace('iram', '')) + f' .{split_name[2]}' if len(split_name) >2 else ''

Please note that your line numbers could be slightly different.

[balix-microej]

Hi @dobairoland. No problem. I did as you advised and it worked. It seems that in fact this is normal in my case. I have a specific library included in my project that have section names that do not match the expected pattern. Thank you for your help!

[dobairoland]

Thanks for the feedback. The above fix will be probably included in ESP-IDF soon.