We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
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
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.