The EmbSysReg Viewer (http://embsysregview.sourceforge.net/) has been updated with even more Freescale SVD (System View Description) files, with a current count of 96 devices.
See “How to Add Register Details View in Eclipse” how to install and use the plugin.To install:
- Use the Eclipse updater to install the plugins from http://embsysregview.sourceforge.net/update
- Download the latest zip archive file version from the sourceforge page (https://sourceforge.net/projects/mcuoneclipse/files/Eclipse%20Plugins/EmbSysReg/). Place the files from the archive over your Eclipse installation.
The earlier v0.2 patch file included support for 33 devices:
The new v0.3 zip file now includes 96 devices 🙂 :
Users of the earlier v0.2 can install the new package over the existing files.
To open the view, use the menu Window > Show View and select the EmbSys Register view:
Use the view icon to select the register file to be used:
Then select the device you want to use:
To read/change the register variables, double-click in the item:
❗ Note that the current SVD files from Freescale (and other vendors) do *not* contain the ARM core registers (NVIC, etc). According to ARM, this ‘intentional’ as they expect the debugger to give native access to the ARM core registers, and not to duplicate content in the SVD files. I hope this will change soon (e.g. the SVD files be able to reference the core registers somehow), as otherwise SVD files are somewhat limited. Or has anyone SVD files for the ARM core registers so the community can benefit from it?
❗ Update: see the core register files in the Freescale community.
Happy Viewing 🙂
> Or has anyone SVD files for the ARM core registers so the community can benefit from it?
In a recent discussion with ARM/Keil they mentioned that these files exist, just that it is not yet clear how to include them in the current CMSIS packs. So… work in progress.
I plan to temporarily include them in a future version of GNU ARM Eclipse, to improve the (soon to be released) peripherals viewer, until a final CMSIS solution will be available.
It would be already a plus if the ARM core registers (say one for each M0, M3, M4) would be available. Then I could select them in the EmbSysReg viewer to have at least something. But I guess there won’t be ‘one file for all’, as each licensee of ARM can modify certain aspects of the core (e.g. number of interrupt levels, debug interface, etc).
And I’m looking forward to your peripherals viewer :-). The EmbSysReg viewer is ok, but has several short comings in my view: e.g. it would be nice if the viewer would automatically selected the SVD file based on the device under debug, just to name one thing.
Pingback: Comparing CodeWarrior with Kinetis Design Studio | MCU on Eclipse
The GNU ARM Eclipse v2.4.1-201410142110 already integrates the peripheral registers view in the J-Link plug-in (gnuarmeclipse.livius.net/blog/peripheral-registers/), there is no need to install the separate EmbSysReg plug-in.
Future releases will extend support for OpenOCD.
Pingback: Tutorial: Adafruit WS2812B NeoPixels with the Freescale FRDM-K64F Board – Part 4: Timer | MCU on Eclipse
We have integrated Liviu’s peripheral viewer in SOMNIUM DRT – it works really well (we automatically configure the processor type so it works “out of the box”). We would also like to see the ARM core registers integrated in a future release …
Pingback: Overview: From Snippets to Code Generation | MCU on Eclipse
Any idea why the MKL43Z4 does not show up in the list? I have updated everything, and I can see MKL43Z4.xml along with the files for the other processors, but for some reason it does not show up in the list in Preferences.
It works for me, using default Kinetis Design Studio v3.0.0. Are you using the same?
I am using a custom Eclipse Mars installation that I set up by following the instructions in the article you recently posted on this topic. Since this did not include the EmbSys viewer, I added that afterwards (also following the instructions in one of your articles).
It does show up in KDS 3.0.0, just not in the Eclipse Mars installation. It’s almost like it’s not even looking in the directory containing the SVD files, as the list of processors shown is much shorter than the number of files or what shows up in KDS 3.0.0.
I think I see your problem. Let me write up a short article how I get it working with EmbSysRegView on Mars with Freescale SVD files. I should have it ready tonight my time (in maybe 6 or 8 hours). Would that be ok?
Are you using the EmbsysRegView v0.2.5 too?
I have uploaded the latest SVD files I have to https://sourceforge.net/projects/mcuoneclipse/files/Eclipse%20Plugins/EmbSysReg/, maybe you can use these files?
OF course that would be ok, and very much appreciated! I am using 0.2.5, although the data file version says it is 0.2.5.r168. I tried those files, but there is no difference. I am suspecting that it’s using some built in set of SVDs and not even looking in that data directory.
Correction – it says the data file version is 0.2.5.r180, although the directory is not named to match that version. I tried renaming the directory, but it did not fix anything.
Yes, I have 0.2.5.r180 too. Data is in org.eclipse.cdt.embsysregview.data_0.2.5.r180.
You cannot rename the directory, as the version information is in the plugin.
You need to have the data files in org.eclipse.cdt.embsysregview.data_0.2.5.r180
Yes, that’s where I have them (org.eclipse.cdt.embsysregview.data_0.2.5.r180) – but still not working.
Have you tried my new zip file from SourceForge (http://sourceforge.net/projects/mcuoneclipse/files/Eclipse%20Plugins/EmbSysReg/FSL_SVD_Files_16-Sept-2015.zip/download)?
I have documented my settings here: https://mcuoneclipse.com/2015/09/16/freescale-cmsis-svd-register-files-with-eclipse-mars-and-embsysregview/
Erich – i got it working. The issue was that I was updating the folder under the Eclipse plugins folder. For some reason, when I initially installed 0.24 of the EmbSys plug-in, it created a folder there. However there was also a folder in a hidden directory underneath my Windows profile folder. SO my theory that it wasn’t even looking at the files I was updating was correct. So, I just copied over the Files from the KDE plug-in as you mention in your article, and it’s all working fine now. Thank you so much for all the help; I see now why my friend recommended your blog so highly.
is there a update regarding the combination of core and peripheral registers?
is embsysregview still the tool of choice?