This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

It takes a super long time to build and run nRF5340 code

Previously, I used SEGGER to build and run programs on nRF52 DK very quickly (5-20 seconds).

However, for nRF5340 DK, it usually takes about 8-15 min to build and run just 1 example program. For example, here is the nRF5340 DK beacon example project build and run time duration (17min 45sec in total):

Especially for this step, it takes a long time: 

Is that normal? Why nRF5340 DK takes so long time to build and run the program, please? If I need to upgrade my laptop hardware, what's the key performance which my new laptop need to improve (such as better CPU, multiple processors)? Here is my laptop performance data: 

Thanks! 

Parents
  • StevenW807 said:
    Thanks again for your patient support! The Nordic Support Team is the best I have ever seen. 

    Thanks a lot, Steven! We are glad to hear that. Your feedback is really appreciated :-)

    Well, let’s see if we can speed up your computer a little bit, then.

    StevenW807 said:
    Here is my disk type (see image). I guess it's not the issue.  

    No, a SSD drive should not cause this kind of problems so we might wanna exclude that.

    StevenW807 said:

    Yes, I follow the manual to installed all tools: 

    According to your picture, you have installed the nRF Connect SDK via the Getting Started Assistant? I actually wouldn’t recommend that, since it is designed for Linux and especially macOS. I personally use a Linux OS and installed the nRF Connect SDK manually without using the Getting Started Assistant. But anyway, this does not necessarily have anything to do with the issue you are facing.

    Previously, I used SEGGER to build and run programs on nRF52 DK very quickly (5-20 seconds).

    When building programs for the nRF52 DK, did you use the same installation of the nRF Connect SDK for that as well?

    It might wanna be interesting to find out if this is a Segger Embedded Studio or a toolchain issue. If you build the same program outside of SES from a terminal, does that make any difference?

    Regards,

    Markus

  • Thanks, Markus, 

    I have tried to use SEGGER to build the project (beacon example), and then use nRF Connect Software --> Programmer to upload the zephyr.hex file to the nRF5340 board. It's successful! 

    Note: zephyr.hex locates at ...\ncs\v1.5.1\zephyr\samples\bluetooth\beacon\build_nrf5340dk_nrf5340_cpunet\zephyr

    However, I cannot use SEGGER to directly download the "build and run" project to the board (see screenshot). Any idea why, please? Thanks! 

Reply Children
No Data
Related