Is anybody intereted in a version of OpenOCD with a GUI.
I was thinking of maybe building a version with a wxWidgets GUI.
I use a Segger JLink for my job and I find the GUI for that really useful.
I would also like to reduce the need for people to make scripts to use OpenOCD too.
The idea there is to allow configuration from the GUI and also to autosense the chip connected.
A nice interface could be added to allow the connected things to be programmed.
What do people think ??
fordp:
Is anybody intereted in a version of OpenOCD with a GUI.…
I would also like to reduce the need for people to make scripts to use OpenOCD too.
The idea there is to allow configuration from the GUI and also to autosense the chip connected.
…
What do people think ??
I would like to have one GUI or some way to generate the scripts… and I don’t know for what more the GUI would be good, since I hope to do debug with Eclipse…
This is an image of the JLink GUI (from the Yagarto Website)
http://www.yagarto.de/images/jlinkgdb1.png
Which is pretty good but could be improved upon.
The idea here is not to change the “Engine” of OpenOCD but to make it easier to use and more accessible to more people.
I think the best way to do that is to give feedback using a GUI and to reduce as much as possible the need for scripts.
The same executble could be made to run as a deamon just like it does now.
Making this GUI with WxWidgets would keep the code cross platform as well!
that would be great 
Simply use mutiple -f parameters to enable different targets ,interfaces and scripts.
Nice to see at least one person wants it.
I would really like to do it but I want it to become the official version, if not there is too much work to keep it tracking chnages in the rapiddly changing openocd.
I guess I need to build one version and see what the other devs think.
This would be really great.
Every one, whos already running a working script whit that target and JTAG Interface could send this script to you. And the GUI just manages the right selection.
One problem i see is the “rapid” development with many SVN releases each month. There must be an installation-package which contains all needed scripts and a special SVN release of openOCD.
This sounds to be hard work, but many people would like it!
Are you already working on it?
fordp:
This is an image of the JLink GUI (from the Yagarto Website)Which is pretty good but could be improved upon.
The idea here is not to change the “Engine” of OpenOCD but to make it easier to use and more accessible to more people.
I think the best way to do that is to give feedback using a GUI and to reduce as much as possible the need for scripts.
The same executble could be made to run as a deamon just like it does now.
Making this GUI with WxWidgets would keep the code cross platform as well!
Recently, After using J-Link/GDB-SERVER and JTAGKey/OpenOCD, I have the same idea as yours. My plan is:
Step 1) to build a GUI only support YAGARTO’s OpenOCD distribution. This is to say, only Windows are supported. However, for the feature, the GUI should use GTK+, TCL/TK or something cross-platform.
Why YAGARTO? Because the command sets of OpenOCD varies from version to version, it’s hard to get a lot of stable targets config files, if the GUI support OpenOCD’s svn.
Step 2) Collect ‘cfg’ scripts of the targets as many as possible.
About the function of this GUI:
It’s nothing but a front-end.
choose the interface manually.
detect the corresponding target ‘cfg’ file automatically, if there are some possibilities, make a list. Then user can choose the right one.
user can input his/her data, through a J-Link-like interactive option, then save it as his/her dedicated ‘cfg’ file. (for instance, init script)
user can choose flash the target and disconnect, other than debug it.
If this GUI grows up, when it has many users, we can easily support the latest OpenOCD’s svn.
