Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

[New plugin] cbSystemView for embedded development

(1/6) > >>

BlueHazzard:
Hi,
i made a new plugin for codeblocks: cbSystemView https://github.com/bluehazzard/cbSystemView
This plugin allows to read SVD Files and display registers accordingly during debugging sessions.

NOTE: This plugin does not work with current codeblocks. It needs some modification, i have done them on this branch: https://github.com/bluehazzard/codeblocks_sf/tree/debugger/pull_candidate/memory_range_watch/1

i hope they find their way into the main branch. The modifications are discussed here: http://forums.codeblocks.org/index.php/topic,21457.30.html

Who needs this plugin?
If you work with embedded systems (mostly ARM controller) this plugin helps you a lot during the development. Eclipse has it too: https://sourceforge.net/projects/embsysregview/
it still needs some work, but it is a good start and all basic functionality is there.

greetings

Quiss:
Hi,

I've built your modified cb and plugin without error. But this shows up after clicking a menu item (like Help->About):


As I've searched a little bit, I think it has something to do with Windows 10 (and 8 ) and this wx version: https://github.com/pcsx2/pcsx2/issues/853#issuecomment-143596989

Windows 10 - 1703, Tdm-gcc-5.1.0, wxWidgets 3.0.2

BlueHazzard:
I do not use win10 so i can not tell anything about this.
Is this problem also with the normal build of codeblocks?
i build it with wx3.1 so maybe this helps...

Quiss:
I've just built https://github.com/obfuscated/codeblocks_sf (SHA-1: e7d2a6627cd08fb290048026b859dd8a57f7875e), the same problem exists. Let me try with wx3.0.3 before 3.1.

Edit: 3.0.3 is ok. Occurences highlighting does not work but it doesn't work in main cb either.

oBFusCATed:
@bluehazzard:

I'm looking at the memory watches patch and have a question:
Do you add all elements in the tree as memory range watches? Or do you just add the root ones?
To me it seems that you don't just add the root ones as is done in the normal watches.
Does it make sense to do the same thing? Is it to limiting?

I'm asking, because doing it like it is done would affect performance more compared to the way the normal watches are done.
Generally for normal watches it is expected that you have very small number of watches, but with svd files you could have hundreds of registers and their views.

Navigation

[0] Message Index

[#] Next page