nRF Connect with VSCode: how to generate assembly files

RE: nRF Connect with VSCode: how to generate assembly files

Mattias — Mon, 08 Jan 2024 21:23:24 GMT

Hi again,

yes both methods worked as expected.

Thanks again,

Mattias

RE: nRF Connect with VSCode: how to generate assembly files

mkjones — Mon, 08 Jan 2024 18:28:08 GMT

I can confirm that CONFIG_OUTPUT_DISASSEMBLY=y does indeed produce a zephyr.lst file.

It would still be nicer if we could easily get the disassembly for just one (or specified) source files; but this is almost as good (and in some cases would be more useful).

RE: nRF Connect with VSCode: how to generate assembly files

Håkon Alseth — Mon, 08 Jan 2024 08:21:33 GMT

Hi Mattias,

Glad to hear that it worked.

[quote user="mathae"]With the minor difference is that I use arm-none-eabi-objdump.[/quote]

Did you try the CONFIG_OUTPUT_DISASSEMBLY=y ? As mentioned, this is highly likely the easiest option to create a list file (build/zephyr/zephyr.lst).

My apologies for missing this configuration earlier.

Kind regards,

Håkon

RE: nRF Connect with VSCode: how to generate assembly files

Mattias — Fri, 05 Jan 2024 15:39:35 GMT

Yes that worked!

With the minor difference is that I use arm-none-eabi-objdump.

RE: nRF Connect with VSCode: how to generate assembly files

Mattias — Fri, 05 Jan 2024 15:38:03 GMT

Thanks Håkon, that works fine!

RE: nRF Connect with VSCode: how to generate assembly files

Håkon Alseth — Fri, 05 Jan 2024 15:04:49 GMT

Hi Mattias and mkj,

There is a configuration, CONFIG_OUTPUT_DISASSEMBLY, that can be set and it'll create a .lst output.

I'll leave the former CMakeLists.txt hack, in case you actually need to run a post-process command, but I would recommend just setting the above kconfig if you want to see the assembly lst file.

My deepest apologies for missing this configuration..

Kind regards,

Håkon

RE: nRF Connect with VSCode: how to generate assembly files

Håkon Alseth — Fri, 05 Jan 2024 14:12:34 GMT

Hi Mattias,

I spent some extra time on this, and found that this seems to work:

# SPDX-License-Identifier: Apache-2.0

set(MY_OBJDUMP /opt/zephyr-sdk/zephyr-sdk-0.16.0/arm-zephyr-eabi/bin/arm-zephyr-eabi-objdump)

set_property(GLOBAL APPEND PROPERTY extra_post_build_byproducts
  COMMAND ${MY_OBJDUMP} -S --disassemble ${CMAKE_BINARY_DIR}/zephyr/zephyr.elf > ${CMAKE_BINARY_DIR}/zephyr/zephyr.asm
)

cmake_minimum_required(VERSION 3.20.0)
find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
...rest of file

Note that the placement is before find_package(...) in the projects CMakeLists.txt file.

Could you try this and see if it works in your project as well?

Kind regards,

Håkon

RE: nRF Connect with VSCode: how to generate assembly files

Mattias — Fri, 05 Jan 2024 09:53:39 GMT

Hi,

isn't the a way to get assembly files to be kept in the build folder? I'm so far using arm-none-eabi-objdump to get assembly from zephyr.elf but would prefer to get it automatically at every build. I have tried different directives in CMakeLists.txt without any success.

Mattias

RE: nRF Connect with VSCode: how to generate assembly files

Håkon Alseth — Thu, 02 Nov 2023 09:58:51 GMT

Hi mkj,

Glad to hear that this helped!

[quote user="mkjones"]once I remembered to add the "nRF Connect" shell in VSCode, since it has the correct PATH already set up[/quote]

Sorry about this, I should have added a c:\PATH\to\ in my former post. You can do an absolute path towards objdump if you want to add this to some sort of "post build operation" in vscode, , ie. : c:\ncs\toolchains\...\bin\arm-zephyr-eabi-objdump <file.elf>

Kind regards,

Håkon

RE: nRF Connect with VSCode: how to generate assembly files

mkjones — Wed, 01 Nov 2023 15:29:52 GMT

That did the trick (once I remembered to add the "nRF Connect" shell in VSCode, since it has the correct PATH already set up). And, with the DEBUG build anyway, there is enough context from the C code to easily find the functions I was interested in.

Thanks so much for the quick response!

--mkj

RE: nRF Connect with VSCode: how to generate assembly files

Håkon Alseth — Wed, 01 Nov 2023 11:29:50 GMT

Hi mkj,

As you mention, normally you output .asm via the "-S" switch in GCC.

Adding custom compiler switches can be done using "CONFIG_COMPILER_OPT", but the adding the -S switch does not combine well with the build system in zephyr.

What you can do is, after the fact, use objdump to disassemble your .elf file:

arm-zephyr-eabi-objdump -S --disassemble my-build-folder/zephyr/zephyr.elf > disassembly.lst

Kind regards,

Håkon