Adding CMSIS-SVD Files to EmbSysRegView 0.2.6.r192 and Eclipse

In “EmbSysRegView 0.2.6 for Eclipse Neon and Oxygen” I have described how to add CMSIS-SVD register detail files to Eclipse using the EmbSysRegView plugin.

But what I need to add vendor or any other SVD files to it? Here is how:

EmbSys Registers View

EmbSys Registers View

CMSIS-SVD Files

With the installation method described in , all the data comes in a large .jar file inside the plugins folder:

org.eclipse.cdt.embsysregview.data_0.2.6.r191.jar

org.eclipse.cdt.embsysregview.data_0.2.6.r191.jar

A .jar file is nothing else than a .zip archive file, so I can open the file as any other .zip file:

Content of Jar File

Content of Jar File

So the approach is to add extra SVD files (extension .xml) to that structure and .jar file.

Kinetis Design Studio 3.2.0

KDS 3.x uses the unchanged/stock EmbSysRegView plugin, this makes it very easy. The data files are located in

<KDS installation folder>\eclipse\plugins\org.eclipse.cdt.embsysregview.data_0.2.4.freescale\data

Copy the files into the data folder of the plugin, .e.g.

<eclipse>\plugins\org.eclipse.cdt.embsysregview.data_0.2.6.r191\data

You can use any custom folder, e.g. I have used ‘KDS’ as folder below:

Added KDS Files

Added KDS Files

Now I have the files/devices available under that folder in the EmbSysReg selection:

KDS Folder

KDS Folder

That way I have all the extra NXP KDS register files available:

EmbSys Registers View

EmbSys Registers View

NXP S32 Design Studio

If using S32 Design Studio, this Eclipse distribution uses a custom and modified version of EmbSysRegView plugin. So the SVD files are hidden and part of devices support/service packs. You can find them after installation if searching for *.svd in the installation directory:

S32 SVD File

S32 SVD File

Copy the files into the data .jar file. Change the extension from .svd to .xml.

Other SVD files are inside device specific .jar files, inside the eclipse\plugins folder:

Plugins file

Plugins file

The files are named in the following format:

com.freescale.s32ds.cross.gnu.<device>
com.nxp.s32ds.cross.gnu.arm.<device>

With this I get a set of S32 Design Studio SVD files I can add to my collection:

S32 SVD Files

S32 SVD Files

Inside the EmbSysRegister view, I can now open them under the S32 group:

S32 SVD Files in EmbSysRegister

S32 SVD Files in EmbSysRegister

Summary

Knowing the EmbSysRegView data structure and data file makes it possible to extend it with extra CMSIS-SVD files. A good place is to grab them from existing IDE installations: that way I can build up my set of SVD files for easier debugging.

Happy SVD-Jaring 🙂

Links

 

Advertisements

What do you think?

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s