Tips on how to use Segger Embedded Studio?

[TylerD]

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...

[awneil]

TylerD said:

This is more related to the Segger Embedded Studio than Nordic parts or SDK

So maybe the Segger forum would be better:

https://forum.segger.com/index.php/Board/9-SEGGER-Embedded-Studio-related

TylerD said:

What are your thoughts?

It's OK.

As it's free for use with Nordic products, and Nordic use it for all their examples - it makes sense to use it for Nordic work.

The debugging "Just Works" - though only with J-Link.

I wouldn't pay for it.

I agree that its navigation & browsing is inferior to Eclipse.

eg, https://devzone.nordicsemi.com/f/nordic-q-a/47870/embedded-studio-go-to-definition-declaration-not-working-for-functions-outside-of-file/189722#189722

[TylerD]

Thanks for the feedback. The debugging with J-Link works out of the box and no complaints about that side. The biggest problem for me at this point is the code editing / browsing which seems to be a bit clumsy.

I did not go to the generic Segger forum because I wanted to limit the audience to Nordic BLE users. Interested to hear what other nRF52 users think about the tool. Especially looking for some of the "pros" compared to Eclipse or other tools. I'm trying to figure out what is the best set of tools to work with to be as productive as possible.

[awneil]

TylerD said:

the code editing / browsing which seems to be a bit clumsy

Yes. I also find the autocomplete is clumsy - and often just doesn't work at all.

At the end of the day, both SES and Eclipse are just front-ends to GCC - so it's the same tools "under the hood".

If you're competent at setting up Eclipse projects from scratch - properly understanding things like Include Paths and Linker scripts - then it shouldn't be hard to just use Eclipse.

I think the main hurdle would be getting the Linker Script right - as you have to cope with the memory (flash & RAM) size & placement requirements of the SoftDevice. There may also be some reliance on specific Section names. (SES obfuscates this a bit with its "placement" XML files - instead of using the GCC linker script directly).

If you're familiar with Keil, you could also look at those projects for clues ...

There's a blog post (posts?) by Nordic on setting up Eclipse - and some forum posts from users...

Personally, I put up with the SES niggles rather than dive into the (potentially bottomless) pit of Eclipse configuration!

TylerD said:

I did not go to the generic Segger forum because I wanted to limit the audience to Nordic BLE users

Fain enough,

But there are quite a few Nordic users there, and also people with experience of other IDEs (including Eclipse) vs SES ...