Hello :-)
As the work on SWD is done, I want to move to another planned part of the
development - internals (re)organization. I would like to discuss changes
and make some plannig before it turns out that changes conflict with some
existing works or are there any other objections...
I want OpenOCD to be less 'linux like' in internals and mode superflous,
correct and readable. This implies generating stable API and program flow.
OpenOCD is already most powerful embedded development utility in the open
source world and I want it to be even better and more extensive :-)
I propose to divide program into modules that would create something like
ISO model of the TCP/IP where each layer can only communicate with one up
and one down. This would allow to create generic API of each layer and set
clear program flow. This organization will also be reflected in supeflous
variable and constant names which is extremely helpful in code analysis,
undestanding and debugging.
The layers can look like.
1. OOCD Core.
2. Interface.
3. Transport.
4. Target.
5. Peripherals (bus, gpio, flash, debug, ...).
6. Applications (os, gui, ...)
Please let me know how you like the idea, feel free to ask questions and
make requests, this is the right moment for this :-)
Best regards :-)
Tomek
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
