Segger Embedded Studio cannot find include

[Georgi Valkov]

Using the nRF Connect SDK from Nordic Semiconductor is a terrible experience. One reason it being unreliable with many broken samples. And another being the Segger Embedded Studio, which takes ages to open a project, requires a reload every time a project is changed, forgets the project settings each time a new project is opened. Once we reach the point of building the project, many undefined symbol errors are reported during the linking phase. These can be resolved by adding correct CONFIG_ flags in the .prj file, yet this is is not obvious in any way, and finding the correct flags required by a project is a long and painful experience. Once we get past that point, and we try to program our application, Segger cannot find some headers. And it keeps asking again and again, I've had cases of more than 20-30 prompts. The whole process is extremely tedious and unproductive.

https://youtu.be/BOM5gGFlUQ8

[Georgi Valkov]

Another tedious behaviour in Segger Embedded Studio:
Why does it ask to rebuild the project every time I try to program and debug the board?
I rebuilt the entire project in the beginning, I have not made any changes.

https://youtu.be/62KLOy434Zk

[Georgi Valkov]

Why did you close this case without any comment?

[ketiljo]

i didn't see a question here.

If you use nRFConnnect to program the device instead of Segger Embeddes Studio, you can re-use the hex-file.

In any case, you should ask Segger about this. 

[Georgi Valkov]

Hello Ketiljo!

Since the Segger Embedded Studio is offered as part of the nRF Connect SDK, Nordic Semiconductor is obliged to ensure it operates properly. Segger will put much more efforts if the request comes from a large company such as Nordic Semiconductor.

[Georgi Valkov]

Quote from Segger support:

Sorry to say that, but these are not generic Embedded Studio issues, but seem to be related to how the project is set up.

Therefore, please understand that we can only provide limited support to this case.

However, the reason why Embedded Studio a) cannot find the include files and b) does not recognize that the output is up to date is most probably related to how the build system is set up.

To a) This may happen when the output is built with relative paths. Since Embedded Studio does not know to which a path is relative, it cannot resolve it. A fix would be to make the compiler/linker use absolute paths.

To b) This may happen when input files are updated during build and as such have a newer timestamp than the output.

Unfortunately, both cases are heavily related to the project.

Since the Nordic SDK uses an external toolchain we can not provide any guidance on where things could be configured.

We asked Nordic to provide better support to this case.

You might want to go back to their forums with the new information.

Best regards,

Johannes Lask

Product Manager