I have read the number of threads here on using Eclipse with uVision. But I have not found a thread that stated that someone had completed the interface. I understand we can use Eclipse with .bat files and make files. I still like the ease of use of the automake files in uVision although I know Erik would not agree with me. I repeat the several threads, has anyone interfaced Eclipse with uVision? Bradford
i am not sure why you meant by "completed the interface" or "interfaced eclipse with uvision" - I am not sure if the latter is even possible.
if you were asking to compare and contrast the two, I could. I spent lots of time on hi-tide (eclipse) and then just started on uvision (3.70 demo).
in my experience, uvision is a lot faster, more stable and less bug-prong. It also provides some very powerful features, like the logic analyzer and graphic presentation of the registers / variables - I have found that to be of great help in debugging.
sure, but some have suggested to make many of the features of uv3/4 an eclipse plugin, thereby enjoying from its powerful editor. I tried eclipse once (for ARM gcc) - it was nice, not straight forward configuration, though.
Thank you both for your replies. I ask the question because it had been ask several times before with no good answer. Search this forum for Eclipse. I am a user of Eclipse by default. In my many design tools, scripts and editors are implemented with Eclipse and Tcl. With one client way across the pond, I must maintain my source files on their server using Eclipse and CVS. Not by choice, by edict and I live and work by the golden rule. Them that has the gold makes the rules.
Frequently I move from toolset to toolset and different editors. In the past I have used about every programmers editor from EMAC to Brief to Codewrite, etc. I have used Keil since before it was Keil in the US. I love it. I love the simulator. I love the automake. I'm not crazy about some of the search abilities of uVision but all in all I just like it! So, my point is if Eclipse will allow me to move between different editors or tools, maybe I should spend some time to learn to implement Eclipse. Remember, I start this with " I'm a user" by default. But at the same time, I don't want to bang my head against a wall that someone can quickly identify as tall and hard. In this thread I re-ask the question. Has anyone been able to configure Eclipse to interface directly with Keil's uVision or must we configure Eclipse to be just a glorified script editor to run command line batch files and make files? Oh yes, Codewrite "was/is" a great editor until Borland killed it just as they killed Brief. If there is any Eclipse expert that can say the task is too simple to discuss, I would appreciate that answer also. Then I can start beating my old head against the Eclipse wall. Thanks again. Bradford
"In this thread I re-ask the question. Has anyone been able to configure Eclipse to interface directly with Keil's uVision or must we configure Eclipse to be just a glorified script editor to run command line batch files and make files?"
I am not entirely sure if I understood your objective. Are you trying to find out ways so that Eclipse can use RVDK?
uVision is nothing but a GUI, like Eclipse. the work is done by RVDK (command line compilers / linkers / etc.). uVision is just a presentation tool that helps you work with those not-so-user friend compiler / linker / etc.
so I am not sure why you want to interact with uVision through Eclipse. But I do see a reason to interact with RVDK through Eclipse.
Again, I am not sure if that's your goal.
if it is, I do think it is possible, but not sure if that can be done legally - if I were Keil, I would be quite unhappy about it.
No, that's not true.
uVision essentially combines two things:
1. An IDE (like Eclipse) - for editing & compiling source files, and managing projects;
2. A Simulator and Debugger.
It is the 2nd part that is unique to uVision and is not part of Eclipse.
Thus, I think the question really boils down to, "how to integrate the uVision Simulator and Debugger into Eclipse"
(IMO, the IDE part of uVision is not that great).
"It is the 2nd part that is unique to uVision and is not part of Eclipse."
if so, how does Eclipse handle the simulation / debugging part?
Eclipse (the framework) doesn't - that's what you have to provide as a "plugin" (or whatever the Eclipse-speak is)
There are various debug "plugins" available for various Eclipse-based IDEs.
It seems to me that selling you the debug "plugin" is how many companies make their money out of the "free" Eclipse framework...
Keil do publish some details of APIs for external access to uVision (look in the 'Support' section) - so you'd have to start from there, I guess...
got, Andy.
so in the case of hi-tide/picc from htsoft, I got Eclipse, picc compilers / linkers, etc., and then I got those debug plug-ins that allow Eclipse to simulate / debug programs.
given that uVision is used for many processors, and can be installed by itself, I would imagine the general framework (above) is also true for uvision.
That may or may not be true.
Eclipse is specifically designed as an open framework for building IDEs (note that Eclipse is not, itself, an IDE)
uVision, on the other hand, is Keil's propreitary product which is only made available integrated with their (quite limited*) range of Compilers.
As far as I can see, the uVision debugger/simulator is an integrated part of of uVision - it's not a standalone tool (like the compilers) which is simply "front-ended" by uVision...
* I dare say Keil would prefer to use a word like "focussed"; they don't seem interested to provide tools for all & every architecture - just focus on the 8051, C166, and ARM architectures. Which is fair enough.
I guess if you were to (try to) integrate/interface it with Eclipse (or anything else) this would be a good place to start:
"The uVision Socket Interface (UVSOCK) enables uVision to be controlled and monitored by one or more third party applications (Clients). It enables the Client(s) to perform: * Application configuration * Application building * Application debugging The Client has access to the power of uVision's device database, build system, and features such as advanced debugging with the Real-Time Agent. The Client and uVision work together to provide a seamless experience for the end-user."
See: http://www.keil.com/appnotes/docs/apnt_198.asp
See also http://www.keil.com/appnotes/list/uvision.htm for other uVision app notes...
Andy; Thank you for your replies and links. I have been out of the office for several days so I could not closely follow the thread. Had a lot of good information when I returned. I have downloaded the files. From the first reading, they appear to be a good starting point. I will need to start up the learning curve of Eclipse but now I feel it's not the great tall and hard wall I first envisioned. This effort will be a low priority item but I will post my successful efforts and hide my failures. Thanks again all. Bradford
This also might be of help frozentux.blogspot.com/.../switching-gnu-toolchains-in-eclipse.html
Eclipse I believe needs to have some tools for it to manage building such things. It doesn't make much sense to require people to know JAVA and to create plugin's for something that is an interface (CDT based really) for C/C++ compilers.
Eclipse is OK however lately I've been giving Code::Blocks a serious look over (http://www.codeblocks.org/ ). Eclipse does do a great job for writing code, the nasty part though is compiling that code (the CDT does not address this properly as what is the point of writing code without having a well organized standard access method to compilers and tool chains). I have numerous compilers however, I am no Java programmer, and I don't think writing a pile of XML files for configuration is a good idea either. It's far too hands on (who has the time is a better way to look at it).
Erstwhile hopefully the above links are of use.
Stephen
Stephen; Thanks for the input. The GNU link looks like a cheatsheet for me to interface uVision to Eclipse. I did not understand all of the technique at this time but I'm sure as I move into this effort I will return to review the info. The CodeBlocks link was very interesting. I plan to review that effort in more detail before Eclipse. Thanks again. I will post my successes. Bradford
Code::Blocks is a really nice IDE. Definitely one of the better around.
Per; I agree with you and Stephen about Code::Block until my pea sizebrain realizes once again that I'm trying to use multiple toolsets that already use Eclipse. So, good as Code::Block looks, I feel the Eclipse wall still beckons. Bradford
Just be sure to bring your rope and grappling hook.