• State Suggested Answer
  • Replies 25 replies
  • Answers 1 answer
  • Subscribers 73 subscribers
  • Views 1291 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 330547
Options

Toolchain very slow on Windows machines

Peter Haas

Dear Nordic Team,

we are using the adafruit_feather_nrf52840 and nrf52840dk for our prototypes and recently the toolchain around nrf and zephyr has become a problem.

Build times (especially compilation of the device tree according to logs) became very long such that one reload of our cmake project takes up to 15 minutes.

It had worked in reasonable time previously, at some point the toolchain slowed down on 2 individual machines.
This has happened on 2 different machines with 3 different versions of zephyr and the nrf toolchain (v2.6.0, v2.6.1, v2.7.0).

I tested using standalone zephyr for the build which doesn't seem to work trivially, however it does build an image in less than 10 seconds.
Also on a Linux machine I have available, the build times are much shorter.

Is anybody aware of any windows specific problems or problems with dtc.exe that may cause this?

Is there some cache we directory or temporal files we may have missed to clean?

We have been investigating for some time now as it really slows down our development iterations severely.

Parents
  • 0

    Hi Alex

    Okay, glad to hear we found the root of the issue at least. I think in order to better the performance on the internal network the firewall will need to whitelist some of the resources VS Code is pulling from. I'll get back to you on what exactly these are. I believe you can check the Online Services in VS code to see what is enabled to fetch straight from URLs. I think JSON, Git and CMake at least are some of these.

    Also, we see that you're using the stable version of the VS code extension. In NCS v2.7.0 you need to use the pre-release version of the nRF Connect VS Code extension.

    Best regards,

    Simon

  • 0 in reply to Simonr

    Hi Simon,

    I will update the nRF VS Code extension to the pre-release version.

    Still, we don't think this problem comes from VS Code. My colleague Peter who started this thread, uses CLion with CMake to build the project (Always worked fast before like my setup with VS Code) and we started to get the slow down builds at the same time so we both faced the same issue with and without VS Code so we are pretty sure the build issue doesn't come from VS Code or the extension. 

    If you can tell us what would need to be whitelisted would be great but still we think that this is probably a timeout that should be updated or an option to disable the wait since we are not sure if IT team here at Sony and probably in other companies would allow to change the firewall configuration.

    In any case, we are grateful for your help.

    Best regards,

    Alex

Reply
  • 0 in reply to Simonr

    Hi Simon,

    I will update the nRF VS Code extension to the pre-release version.

    Still, we don't think this problem comes from VS Code. My colleague Peter who started this thread, uses CLion with CMake to build the project (Always worked fast before like my setup with VS Code) and we started to get the slow down builds at the same time so we both faced the same issue with and without VS Code so we are pretty sure the build issue doesn't come from VS Code or the extension. 

    If you can tell us what would need to be whitelisted would be great but still we think that this is probably a timeout that should be updated or an option to disable the wait since we are not sure if IT team here at Sony and probably in other companies would allow to change the firewall configuration.

    In any case, we are grateful for your help.

    Best regards,

    Alex

Children
Related