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

Tips on how to use Segger Embedded Studio?

This is more related to the Segger Embedded Studio than Nordic parts or SDK, but I'd like to hear what kind of experience other Nordic users are having with the Segger IDE. 

I have used several Eclipse based IDEs in the past. After installing Segger Embedded Studio, the first impression is not that good. There are many small things that I don't like, here are a couple of examples:

1) the indexing is SLOW! If I right-click any function name and select "find references", it takes 15-20 seconds to complete. Absolutely ridiculous. In Eclipse, it works so fast you don't even think about it. Maybe I need to somehow index the project so that search is faster? (It should be automatic IMHO)

2) I need to jump between different source files a lot, and the most used key shortcut for me in Eclipse is CTRL + Q = "go to last edit". Is there any similar shortcut in Segger IDE?

I also find the FIND feature (CTRL+F) really unintuitive. If I search for some string, I can find the first instance easily. Often times I want to continue searching for more occurrences of the same string and in any program that I can think of (Eclipse, Notepad++, whatever) you can do this by hitting ENTER. For some obscure reason, this does not work in Segger IDE. 

Good thing is that I was able to launch all of the Nordic SDK example projects right out of the box, without any tweaking. But all in all, there are many small annoyances all over the Segger IDE that make me want to switch to some better IDE. Perhaps using just plain Eclipse for editing the code and the building from command line using make.

What are your thoughts? Are you happy with the Segger Embedded Studio? Any things that you like in the IDE? (Something that is handy especially when working with Nordic parts?) 

I have understood that Segger Embedded Studio is now the preferred IDE by Nordic and I would like to give it a chance. But as said, the first impression is not very positive.

It could be that there are some tips & tricks how to make Segger IDE work better, so please share any that you may have...

Parents
  • I know that this post is quite old but I totally agree with you Tyler. I will go it further by saying that SES is by far the most counterproductive IDE I have ever used. Microchip’s MPLab-X, Eclipse, Netbeans, ST’s System Workbench and Cube IDE and of course Microsoft’s Visual Studio (the king of IDEs) ALL have decent code editing and project navigation features. In a framework with tens of source and header files, if you cannot (especially when you starting and learning) navigate through files (eg. going from usage to declaration/definition and find all references etc.) is simply a waste of time and nerve breaking process.

    I really wish that it could be easier and more maintainable to use Eclipse for application development on Nordic’s devices.

    That's what I think of SES.

Reply
  • I know that this post is quite old but I totally agree with you Tyler. I will go it further by saying that SES is by far the most counterproductive IDE I have ever used. Microchip’s MPLab-X, Eclipse, Netbeans, ST’s System Workbench and Cube IDE and of course Microsoft’s Visual Studio (the king of IDEs) ALL have decent code editing and project navigation features. In a framework with tens of source and header files, if you cannot (especially when you starting and learning) navigate through files (eg. going from usage to declaration/definition and find all references etc.) is simply a waste of time and nerve breaking process.

    I really wish that it could be easier and more maintainable to use Eclipse for application development on Nordic’s devices.

    That's what I think of SES.

Children
No Data
Related