Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

AHaug — Wed, 03 Jul 2024 08:02:41 GMT

Thank you,

[quote user="Victor Groux"]Have a nice day,[/quote]

You too

Kind regards,
Andreas

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

Victor Groux — Wed, 03 Jul 2024 07:22:33 GMT

Of course.

Here's the trace:
devzone.nordicsemi.com/.../cmake_5F00_trace.log

Have a nice day,
Victor

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

AHaug — Wed, 03 Jul 2024 07:16:18 GMT

Happy to hear that it at least worked at the other workstation as it should

If you provide the cmake trace, I can add it to the internal discussion so we have the information for further investigations. There may be something there that could occur for other customers, so it's better to have it than to not have it

Kind regards,
Andreas

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

Victor Groux — Tue, 02 Jul 2024 15:02:18 GMT

Hi,

The installation I've made this week-end at home works perfectly (Windows 10, toolchains v2.6.1, SDK v2.6.1, using the nRF Connect for VSCode extension).

However, on the computer where the issue occurs, I was able to build using PlatformIO CLI in WSL instead of the nRF Connect for VSCode at the Windows layer. So I'm going to work with that solution.

I don't know if you still want the cmake trace. I think I can provide it.

Thank you for the support and the help.

Kind regards,
Victor

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

AHaug — Fri, 28 Jun 2024 13:36:43 GMT

Another suggestion for troubleshooting after some more discussion with my colleagues:

The problem may be that these flags are not set for some reason: https://github.com/nrfconnect/sdk-zephyr/blob/3758bcbfa5cd749d977e2600b6687104b8948243/cmake/modules/FindHostTools.cmake#L76, https://github.com/nrfconnect/sdk-zephyr/blob/3758bcbfa5cd749d977e2600b6687104b8948243/cmake/modules/FindTargetTools.cmake#L31 . If enabled, cmake will skip the test build. My colleague confirmed that that they get the same build error as the customer if I comment these lines.

If it's not an obvious issue, could you make a cmake trace with the following command: $ west build -b nrf5340dk_nrf5340_cpuapp -p -- --trace > cmake_trace.log 2>&1

Kind regards,
Andreas

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

AHaug — Fri, 28 Jun 2024 09:02:19 GMT

Thank you for verifying this for me. I'll relay this to the extension team

[quote user="Victor Groux"]Unfortunately, I didn't have the time yesterday to reinstall a Windows 10 on a machine at home so I'll give you the result on Monday.[/quote]

Allright,

[quote user="Victor Groux"]Have a nice day,[/quote]

Likewise

Kind regards,
Andreas

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

Victor Groux — Fri, 28 Jun 2024 08:48:10 GMT

Hi,

Yes, I'm working behind a corporate firewall but I don't think it restricts git. However I made the installation on an unrestricted network since the firewall was blocking some certs. I used west update and the toolchain manager desktop app like 5 or 6 times but nothing changed about the spinning wheel.
Sure, this is my NCS v2.6.1 directory:

Unfortunately, I didn't have the time yesterday to reinstall a Windows 10 on a machine at home so I'll give you the result on Monday.

Have a nice day,
Victor

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

AHaug — Fri, 28 Jun 2024 06:06:38 GMT

Hi,

Could you do 2 things,

The spinning wheel issue when building seems to be caused by a west issue with using git. Are you by any chance behind a corporate firewall that restricts/blocks git-usage? The developers recommend that you use west update to update the toolchain and SDK as many times as required. You can also do this through the toolchain manager if you can't use command line:
Could you show me a screenshot of your NCS v2.6.1 folder? It should look something like my 2.6.0 SDK installation:

Kind regards,
Andreas

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

Victor Groux — Thu, 27 Jun 2024 09:00:29 GMT

That's perfect,

Thank you.

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

AHaug — Thu, 27 Jun 2024 08:53:49 GMT

Alright,

Let me know about the procedure and I'll let you know when I have some input from the Extension team

Kind regards,
Andreas

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

Victor Groux — Thu, 27 Jun 2024 08:45:21 GMT

Thank.

Currently I don't have an other machine to test with but I'm gonna try on my personal computer this evening.

Kind regards,
Victor

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

AHaug — Thu, 27 Jun 2024 08:07:56 GMT

Thank you for providing this.

There's nothing obvious wrong in the support information but I will bring it to the extension developers for discussion. I've also tried setting up the SDK from a clean Windows machine to see if there's something wrong with the combination of versions in the tools you've listed, but the installation comes out as expected.

If you have one available, could you check with a clean Windows machine if the same thing happens there? Typically (in my experience) when using a machine for a few years I end up with an amalgamation of tools for various programming projects. I have one last hypothesis that the issue is caused by something similar to this, but if you don't think this is the case or you don't have any other machine to test with, then we can wait for some input from the developers w.r.t the fault you're observing.

Kind regards,
Andreas

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

Victor Groux — Wed, 26 Jun 2024 13:16:31 GMT

1) I confirm that the nRF Command line tools is set in my PATH variable.

2) I don't have errors in the Console tab in the Developer Tools

3) Here is the support information generated by the nRF Connect:

devzone.nordicsemi.com/.../nRF_2D00_Connect_5F00_Support_2D00_Informations.txt

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

AHaug — Wed, 26 Jun 2024 12:36:19 GMT

Noted,

Atleast now we've verified that it should not be the installation thats wrong, but there may still be something else going on with the setup.

Could you verify that you have nRF Command line tools in system variable PATH? I.e something like C:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin\ should be present.
Could you open the developer tools in VS Code and see if there are any errors there? You can open it from the command pallet
Could you also generate support information in the command pallett and attach the output here?

Kind regards,
Andreas

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

Victor Groux — Tue, 25 Jun 2024 14:34:22 GMT

I've reinstalled VS Code and follow the guide you send before to reinstall the toolchain, the sdk, etc...

I selected the 2.6.1 version as you asked

Concerning the extension, I only have the nRF Connect for VS Code extension pack installed as you can see in this screenshot

Now when I'm trying to build using the extension, this little wheel spins for like 3min right now without producing any output to the terminal.

It's not even the build that's blocking, it's the creation of the build configuration (I tried with unchecked Build after generating configuration)

I tried to cancel it and build with the command line using:
west -v build -b nrf52840dk_nrf52840

The result are the same that I described in the ticket:

"The toolchain is unable to build a dummy C file"
And the CMakeError.log says "undefined reference to `_exit()`" and then "ninja: build stopped: subcommand failed"

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

AHaug — Tue, 25 Jun 2024 12:42:16 GMT

Ah, so the following did not refer to the sample code

[quote user="AHaug"]Source file was:
int main(void) { return 0; }[/quote]

Good to verify. It looked like it could've been a modified blinky sample. Let me know about the reinstallation procedure.

After you've set it up, if you could also try to build blinky or hello_world with the SDK repository you're using in the workspace (2.6.1 instead of the 2.7.0-rc2 which I currently had up)

As well as make sure that the Toolchain and SDK is set in the extension:

I'm also curious as to how your VS Code extension list looks like, i.e if there is a conflict between MS-CMake and the CMake that the installation procedure sets up, and/or if you have a different priority between these two CMake instances in your system variable PATH

Kind regards,
Andreas

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

Victor Groux — Tue, 25 Jun 2024 12:33:57 GMT

Hi,

It's literally just the Blinky sample, but yes, I can send it to you.

I'm going to uninstall VS Code and follow your suggestions, I'm gonna tell you the result.

Thanks,
Victor

devzone.nordicsemi.com/.../blinky_5F00_sample.zip

RE: Unable to build any sample on Windows 10 - Assertion failed: The toolchain is unable to build a dummy C file.

AHaug — Tue, 25 Jun 2024 12:15:46 GMT

Hi,

[quote user=""]Source file was:
int main(void) { return 0; }[/quote]

Which source file is this? Could you zip me the project you've been using to recreate this?

This does not quite look like standard setup of the SDK, so I believe that you might be better off with a complete pristine installation (not separately reinstallation of either toolchain and SDK). I.e what I suggest that you do is

Uninstall VS Code
Remove nRF Command line tools
Remove nrfutil/nrfjprog and nRF Command line tools from PATH
Uninstall and remove all of your nRF Connect SDK instances and start from https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/lessons/lesson-1-nrf-connect-sdk-introduction/topic/exercise-1-1/ or https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/installation/install_ncs.html

Let me know about the zip file and if you could go through the links supplied to see if you've missed anything.

Kind regards,
Andreas