It's not possible to install the plugin in Eclipse Neon. The same thing happens no matter if I use Marketplace, stable or beta update site. The error I'm getting is:
Cannot complete the install because one or more required items could not be found.
Software being installed: Embedded Systems Register View (SFR) 0.2.5 (org.eclipse.cdt.embsysregview_feature.feature.group 0.2.5)
Missing requirement: Embedded Systems Register View (SFR) 0.2.5 (org.eclipse.cdt.embsysregview_feature.feature.group 0.2.5) requires 'org.eclipse.cdt.debug.mi.core 5.0.1' but it could not be found
I think this is related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=489483 , https://dev.eclipse.org/mhonarc/lists/cdt-dev/msg30668.html and https://github.com/gnuarmeclipse/plug-ins/issues/116
Hi Freddie,
I took a short look at the problem, and with neon and cdt 9.x the api that is used in embsysregviw to get the memory of the device is no longer available.
The DSF (Debugger Framework) part was written years ago by edubec, when the old framework was removed vom CDT.
There are a few mailinglist entrys from the GNU ARM Eclipse developer (https://dev.eclipse.org/mhonarc/lists/cdt-dev/msg30708.html) having the same problem.
Problem seems to be, that there is no easy way to support pre neon and neon in one plugin repository.
I've not looked further into this issue, because of time shortness. I hoped it would be a simple updating dependecies, but this does not look like I could fix it in an hour.
So for now, sorry, no Neon support.
Maybe the developers of CDT would be able to help you with porting this plugin to new CDT framework (as they helped Liviu with his GNU ARM Eclipse plugin)? As for pre-Neon users, I think that having an older version of plugin available (from separate update site?) would be enough - the "data" part of plugin will be compatible with both variants of CDT, only the core plugin has to support Neon.
The GNU ARM Eclipse plug-ins used DSF from the very beginning, not the old API, and the incompatibility introduced by Neon.0 and fixed by changing both CDT and the plug-ins was related to the new debug consoles, not the memory API, so keeping everything alive was significantly easier.
I've ripped out the part that is no longer available. I've got it running on the new Oxygen. Are you interested in the patch?
I understand the desire to have it working on both pre- and post neon; but hasn't time shifted so much that backward compatibility can be sacrificed? Another solution could be to fork the code for modern Eclipse.
Hi Morten,
sure I am interested.
You are right, time shifted enough to dump backward compatibility.
I'm thinking about a third update site. Stable for Neon+ and preNeon for the old release. The beta update site stays for tests. All three will be using the same data package so this should not be too much work.
So while I'm waiting for your patch, I start updating the data package with new svd/xml files.
-Robert
Well, wait no longer. :-) Patch attached. I've also deleted
GDBInterfaceStandard.java as it wasn't referenced. I can't see that in the
patch.
/Morten
Last edit: Morten Kristiansen 2017-07-08
Hi Morten, can you explain how to apply this patch?
Sorry, Osama Gamal Khafagy. Is missed that one. The patch is applied to the source code. Are you looking for directions to build the code yourself, you is it just to get EmbSysRegView installed on a modern Eclipse?
If it's just for installing, please install from http://embsysregview.sourceforge.net/update. Aparently there are some problems with the official site; but installing from the above link should be fine.
Cool!
I'm looking forward to having this plugin running on Oxygen.
Last edit: Sérgio Aurélio Ferreira Soares 2017-07-14
The update-beta site now hosts the (debug)-untested 0.2.6 version that runs with oxygen.
http://embsysregview.sourceforge.net/update-beta
Please give feedback
-Robert
Robert, thanks for working on the new release !
I attempted to install 0.2.6 from the Eclipse software update using http://embsysregview.sourceforge.net/update-beta but the installation failed at the end with the following errors:
'Installing Software' has encountered a problem.
An error occurred while collecting items to be installed
session context was:(profile=DefaultProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Artifact not found: http://embsysregview.sourceforge.net/update-beta/plugins/org.eclipse.cdt.embsysregview_0.2.6.jar.
http://embsysregview.sourceforge.net/update-beta/plugins/org.eclipse.cdt.embsysregview_0.2.6.jar
Artifact not found: http://embsysregview.sourceforge.net/update-beta/plugins/org.eclipse.cdt.embsysregview.data_0.2.6.r191.jar.
http://embsysregview.sourceforge.net/update-beta/plugins/org.eclipse.cdt.embsysregview.data_0.2.6.r191.jar
Artifact not found: http://embsysregview.sourceforge.net/update-beta/features/org.eclipse.cdt.embsysregview.data_feature_0.2.6.r191.jar.
http://embsysregview.sourceforge.net/update-beta/features/org.eclipse.cdt.embsysregview.data_feature_0.2.6.r191.jar
Artifact not found: http://embsysregview.sourceforge.net/update-beta/features/org.eclipse.cdt.embsysregview_feature_0.2.6.jar.
http://embsysregview.sourceforge.net/update-beta/features/org.eclipse.cdt.embsysregview_feature_0.2.6.jar
I'm using MCUXpresso v10.0.2 which is based on Eclipse Neon v4.6.3
I'm encountering this issue attempting to install to KDS 3.2.0. Has anyone found a workaround?
Yes. Install from http://embsysregview.sourceforge.net/update. It worked for me.
AFAIK that site is used to host beta versions; but it seems identical to the latest version and definitely installs.
I still get the same errors when attempting to install into MCUXpresso v10.0.2, even using the regular update site (http://embsysregview.sourceforge.net/update) noted above:
Errors:
An error occurred while collecting items to be installed
session context was:(profile=DefaultProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Artifact not found: http://embsysregview.sourceforge.net/update/plugins/org.eclipse.cdt.embsysregview_0.2.6.jar.
http://embsysregview.sourceforge.net/update/plugins/org.eclipse.cdt.embsysregview_0.2.6.jar
Artifact not found: http://embsysregview.sourceforge.net/update/plugins/org.eclipse.cdt.embsysregview.data_0.2.6.r191.jar.
http://embsysregview.sourceforge.net/update/plugins/org.eclipse.cdt.embsysregview.data_0.2.6.r191.jar
Artifact not found: http://embsysregview.sourceforge.net/update/features/org.eclipse.cdt.embsysregview.data_feature_0.2.6.r191.jar.
http://embsysregview.sourceforge.net/update/features/org.eclipse.cdt.embsysregview.data_feature_0.2.6.r191.jar
Artifact not found: http://embsysregview.sourceforge.net/update/features/org.eclipse.cdt.embsysregview_feature_0.2.6.jar.
http://embsysregview.sourceforge.net/update/features/org.eclipse.cdt.embsysregview_feature_0.2.6.jar
Last edit: Geoff S 2017-10-28
I've been digging and it seems there are some mess in the way downloads are handled by source forge.
I'¨ve attached a small shell script that downloads the relevant files. I was able to install from there, though I can't say for sure whether my Eclipse is playing tricks on me, e.g. by caching previous downloads.
Let me know if it works.
Hi, how to install this addon, after I've downloaded it using your script?
Last edit: pavvel1610 2017-11-03
Click help -> Install new software...
Click add
Click on "Local" and browse to the location where you downloaded the files. Click OK
Now fill in with some suitable name like "embsysregview local download"
Click ok
Now, under "Work with" select the site you just added
You should now be able to select and install embsysregview
As I wrote above, it work on my computer; but I'm not 100% sure it will work for everybody, so if it works for you, could you please confirm? This will allow other to see this is a working workaround. And if it isn't, I might be able to determine how to fix it.
Your workaround is working, thank you!
Hi Morten,
Thank you!
I was stuck with this exact same issue on Eclipse Oxygen. For whatever reason, installing via MarketPlace just fails miserably ... Having no idea how all this is supposed to work, I manually followed your script since I am on Windows host :-( and after a couple of missteps, following the intent of your script and writeup, this procedure works just great.
Again, thank you for providing a workaround. Your workaround out to be more visible ...
Regards,
Ajay