"DS-5 Application Edition
The new Eclipse-based Development Studio 5 (DS-5) supports ARM Linux development on ARM9, ARM11, and Cortex-A application processors."
http://www.keil.com/pr/article/1201.htm
http://www.keil.com/arm/ds5/
That's currently just for Native Linux and Android development on ARM9, ARM11, and Cortex-A8 - but why maintain 2 totally different IDEs?
Will (something like) this replace uVision-4 for use with all Keil toolchains?
Does this mean that Keil are going to resume support for GCC-based development?
I generally agree, but I guess there are other reasons for maintaining uv4, at least for now - mainly: employment issues, the brand, etc. etc. etc.
Although Eclipse has some annoyances of its own, it is fast becoming the de facto standard, and I don't see any compelling reason to retain the uVision interface.
In fact, as uVision has many long-standing limitations, there do seem to be good reasons to drop it!
"If Keil would use eclipse they could put more effort into developing of their configurator, compiler, linker, simulator and debugger support"
Exactly!
See: http://www.keil.com/forum/docs/thread14928.asp
And: http://www.keil.com/forum/docs/thread15179.asp
Hi
I would prefere eclipse as IDE instead of uVision4. The Editor of uVision4 is antiquide from my point of view. If Keil would use eclipse they could put more effort into developing of their configurator, compiler, linker, simulator and debugger support. This could by a win win situation.
Regards
Raphael
Those are differences between UV4 as it stands and GS5 as it stands.
I see no reasons there that UV4 shouldn't be replaced by something Eclipse-based.
After all, why would Keil want to maintain two independent streams?
And there are plenty of Eclipse-based tools around for "small" systems on "small" processors.
I guess that, this is a preparation for the promotion of ARM based smartbook (Cortex-A).
DS-5 Application Edition is the first of three planned DS-5 editions. It supports Linux and Android native application development with a GNU compiler optimized for ARM Linux and an Ethernet or serial connection to the target. Future editions will include kernel and driver debug and trace, and the highly optimizing ARM Compiler.
If ARM wants to defeat Netbook (X86) with their Smartbook, they will need as more as possible useful applications running on smartbooks; then as more as possible useful drivers/devices.
I heard that the Adobe Flash Player for ARM Cortex-A is fully prepared.
IMHO, uV4 will not be replaced. Some differences that comes to my mind: 1) uV4 and MDK-ARM. - MCUs. - Simples OSes o no OS at all (barebones). - Simulator: ton of models. - Debuggers: JTAG. - Applications: Real-Time, Control, etc.
2) DS5 and GCC. - Complex SoCs. - OS: Linux. - Debugger: GDB (JTAG maybe in the future). - Applications: Non-RealTime (or with RT-Linux patch), HMI, networking or everything that a Complete OS like Linux can bring.
View all questions in Keil forum