Segger Embedded Studio is not Eclipse based and it is written in Qt. It has a much cleaner interface, but I haven't used it, because I don't have a Jlink or a spare STLink that I could "switch" to Jlink mode.
It looks a lot like Eclipse, so I thought it was a heavily customised version of Eclipse.
Personally I didn't find it that easy to use, so I uninstalled it.
Its also rather expensive at around $1000.
@Roger: As I wrote above you need a small fw mod, but no idea how to do it..
http://www.stm32duino.com/viewtopic.php ... 448#p18757
UPDATE: tried here (for my educational purpose only) and it upgraded fine, recognized as .
No "nag" screens, no annoying messages or warnings. Works like a standard J-Link.
UPDATE1: downgraded back to ST-link ok.
UPDATE2: upgraded again and read BPill's flash via J-Flash .
NOTE: I did not try to run it as the Debugger inside Sloeber or Ozone. It should work fine, however
UPDATE3: I downgraded back to ST_Link as it is not allowed to use it outside the eval-boards
Limitations (from their web page):
May be used with ARM based ST devices only
Only debugging on evaluation boards is allowed. Debugging on custom hardware is not supported and not allowed
No production flash programming support
Unlimited breakpoints in flash available for evaluation only
No support is given
Pukao Hats Cleaning Services Ltd.