Create a new project in Segger Embedded Stuido

RE: Create a new project in Segger Embedded Stuido

kalmesh — Fri, 07 Jan 2022 05:35:57 GMT

Hi everyone

Even i have the same issue i mean creating the new project is simple but adding the related files to it seems difficult one

Can anyone suggest me how can i add the remaining files to the newly created project..??

Regards

Kalmesh

RE: Create a new project in Segger Embedded Stuido

haakonsh — Wed, 20 Nov 2019 13:48:32 GMT

Then you will have to edit every path.

RE: Create a new project in Segger Embedded Stuido

jbmillard — Tue, 19 Nov 2019 18:39:34 GMT

Would you expand on this? How would you copy a project? I tried this and it looks like I'm going to have to edit every path in the project file. I don't want all my projects in the SDK examples directories.

RE: Create a new project in Segger Embedded Stuido

haakonsh — Tue, 20 Aug 2019 12:50:00 GMT

No, not to create one from scratch. If you want to customize the project I suggest you copy an example and modify the project file itself. The segger embedded studio project file is an XML file that's fairly easy to read and re-write.

RE: Create a new project in Segger Embedded Stuido

nngohel — Sat, 10 Aug 2019 10:06:12 GMT

haakonsh There is no such video which give a help to create a new project.

RE: Create a new project in Segger Embedded Stuido

haakonsh — Wed, 12 Jun 2019 13:39:54 GMT

Not that I've heard. Most of the focus of our work with SES is on functionality with the future nRF Connect SDKs.

To be quite frank, I will always base my new projects on existing example projects.

RE: Create a new project in Segger Embedded Stuido

EvanJohnson — Wed, 12 Jun 2019 13:01:05 GMT

Hey Haakonsh,

Any update on if the "New Project Wizard" is in the works? Creating new projects still haunt me.

RE: Create a new project in Segger Embedded Stuido

haakonsh — Thu, 26 Apr 2018 07:45:44 GMT

This really is an IDE problem and not a SDK folder structure problem. Automated search paths for header files should have been a solved problem by now, IDE development for embedded systems is lagging years behind the rest of the SW world.

I am as annoyed as you are whenever is have to manually input paths of a newly added driver or library, let alone starting a project from scratch.

It would be nice if the IDEs search path was fully recursive from the SDK root folder.

As Robert suggests a "New Project Wizard" is a good idea, but its a lot of work when we have to support Keil, IAR, SES, and every other GCC/CLANG based IDE.

I will forward your requests to the SDK team, maybe we can influence the architecture of our next major SDK release, next year.

RE: Create a new project in Segger Embedded Stuido

rdpoor — Wed, 25 Apr 2018 16:17:36 GMT

FWIW, the search path chaos isn't limited to the Nordic SDK -- the NXP Kinetis Development Studio and corresponding SDK suffers a similar problem.

In addition to (or in lieu of) your suggestions, Nordic could offer a "New Project Wizard" that sets up all the search paths for you. I'd be fine with that.

RE: Create a new project in Segger Embedded Stuido

robert — Wed, 25 Apr 2018 14:33:41 GMT

Hi Haakonsh,

Thanks for your comment. My intention is to reduce the number of folders by merging some sub-directories, not to put "all" modules in a single folder. That would make every one crazy if all files are in a single folder.

RE: Create a new project in Segger Embedded Stuido

haakonsh — Wed, 25 Apr 2018 08:53:40 GMT

This is the way I do it too. Alternatively you can init git on the whole SDK and add the files and folders that you do not use to gitignore.

RE: Create a new project in Segger Embedded Stuido

haakonsh — Wed, 25 Apr 2018 08:35:27 GMT

Hey Robert,

I fully agree with point (1), but I have to disagree with point (2), by putting all the modules in a single folder we loose the architectural oversight inherent in the current SDK folder structure and the accompanying SDK API documentation.

sdk_config.h is huge and growing, that's why the CMSIS Configuration Wizard is necessary.

Cheers,

Håkon.

RE: Create a new project in Segger Embedded Stuido

robert — Wed, 25 Apr 2018 02:12:47 GMT

One of the biggest issue of nRF SDK is the "include searching path". They are really messy. I think Nordic need to re-organize the directory structure and the syntax used while including a header file. I have few suggestions for Nordic:

(1) Use sub-directory name in the #include syntax. Sometimes it is better to use "#include <dirA/module.h>" instead of "#include <module.h>" and add full path of dirA to the include-searching path.

(2) For each component in the components directory, there is no need to create so many sub-directories. Take "components/ble" for example, there are totally 12 subdirectories there. So, we probably need to add 12 paths in the searching path. A better way is to simplify the structure such as putting most of the .c and .h files directly under components/ble/ instead of components/ble/xxxx/. For the ble_services folder, sure, we can keep it.

The above two rules can be applied to the whole nRF5 SDK. If Nordic can do this for the next SDK release then your issue will be gone.

Btw, do you notice that sdk_config.h is getting bigger and bigger (12,954 lines so far). This is definitely not a good thing for software engineering.

Robert.

RE: Create a new project in Segger Embedded Stuido

rdpoor — Tue, 24 Apr 2018 21:16:23 GMT

One technique that works for me is described here:

https://devzone.nordicsemi.com/f/nordic-q-a/28196/graduating-from-example-to-production-project-file-structure

It's a little bit cheating, but here's the summary. (Below, I'm using $SDK as a shorthand for the directory containing the SDK of your choice):

1. Create a "myprojects/" directory under the example directory of your SDK:

$ mkdir $SDK/examples/myprojects

2. Copy an example project of your choice into the myprojects directory, renaming it if you wish:

$ cp -rp $SDK/examples/peripheral/timer $SDK/examples/myprojects/test_a

3. Open the .emProject inside that directory, e.g.:

$ open $SDK/examples/myprojects/test_a/pca10040/blank/ses/timer_pca10040.emProject

Now you can modify, compile and run the app according to your needs.

I only call this "cheating" because you're still building inside the SDK directory rather than a sandboxed directory of your choosing, but it works. The biggest advantage of this approach is that you don't need to update all the links to the include files and libraries and whatnot (which is really tedious). A few points:

Theoretically, you could create a symbolic link from $SDK/examples/myprojects into a sandboxed directory of your choosing. (I haven't tried this).
One advantage of this approach is that myprojects and all code under it is tied to the SDK that its built on. If you update the SDK, it will be obvious that you need to re-build your code.
You might wish to rename your .emProject file (and some of the references inside that file) to your actual project name, e.g. `test_a` in the above example.

The above approach works for me. Its quick and easy. Your mileage may vary.

RE: Create a new project in Segger Embedded Stuido

rdpoor — Tue, 24 Apr 2018 19:37:42 GMT

Coming from the Eclipse / workspace view of the world, I second this question! Like Tony, I'd like to start with a copy of an example project rather than modify the example code in place. The video series is helpful, but it doesn't address this key question.

RE: Create a new project in Segger Embedded Stuido

Tony — Tue, 24 Apr 2018 19:29:14 GMT

I also want to say that one of the main reasons to want to do this is because I don't want to be modifying the existing examples and saving them in place. I want to make sure the examples stay the way they are and copy them to my new project.

It would also be nice if I could reference files in another place that I won't be changing, but ensure that any files I will be modifying will be my own copies and not the originals.

RE: Create a new project in Segger Embedded Stuido

Tony — Tue, 24 Apr 2018 19:27:40 GMT

I watched the tutorials and they don't really talk about creating a new project either from scratch or from an existing project.

I tried opening one of the examples and then doing Save As on the solution. It let me save it, but then all of the files in the project would not open. For example when I double click on the main.c file it says it can't fine C:\main.c. That is not where I saved the solution. When I double clicked on another files it said it couldn't find a file at some path like ..\..\components\ etc.

It looks like all of the paths are relative to the project solution file.

You see, the main thing is that I don't want to be saving my own project files inside of the examples folder inside of the SDK folder. That doesn't seem like a very good idea since someday I might want to update / upgrade the sdk and having my own projects files inside of it doesn't make sense.

So the big question everyone wants to know is what is the proper way to start a new project and save it in your own location and have all of the relative paths get fixed without having to do that all myself?

RE: Create a new project in Segger Embedded Stuido

haakonsh — Thu, 01 Mar 2018 09:59:18 GMT

Hey Arsenii,

Take a look at our Introduction to SES videos.

You should also use one of our example projects as a template.

Cheers,

Håkon.