Author Topic: How to create our own stable IDE  (Read 8500 times)

0 Members and 1 Guest are viewing this topic.

Offline uncle_bob

  • Supporter
  • ****
  • Posts: 2441
  • Country: us
Re: How to create our own stable IDE
« Reply #25 on: February 13, 2016, 02:25:00 am »
Kinetis Design studio is vanilla Eclipse + gnu arm embedded + open OCD in a nice package.    Save you self some time and just use it.   It is all open source if you feel like working on an IDE

Hi

And you now have the "fully finished" KSDK ver 2.0 to go with it....:)

Bob
 

Offline uncle_bob

  • Supporter
  • ****
  • Posts: 2441
  • Country: us
Re: How to create our own stable IDE
« Reply #26 on: February 13, 2016, 02:39:17 am »
Hi,
    I want to create my own stable IDE.I want to know how to do it???

Hi

If you want a 100% perfect IDE, you will need far more resources that you can afford. I suspect that a "from scratch" bug free IDE is probably well over a thousand man years of effort.

If you hire 100 guys for 10 years, you get an IDE. At this point it is perfect *and* it supports the parts that were out on the market 10 years ago. In those 10 years, you have had ample time to find all the errors in the manufacturer's data sheets. You also have been able to test a few thousand MCU's to find all of the places the silicon it's self has bugs.

Unless you either have a major budget, or are happy working on an IDE pretty much forever, this is not a road to go down. You will spend *far* less time working through the bugs in something like KDS (like by a factor of 1,000) than you will writing an IDE from scratch.

Down the road from us, there is an outfit that has taken a somewhat less ambitious approach. They decided to build their own IDE on top of Eclipse. Nothing super fancy. More an in-house customization than anything else. Last time I checked, they had five guys full time on supporting the effort. That's a lot of expense. For them it made sense. It lets them move designs between different vendors and *know* that the design will work. It eliminates the "tool chain lock in" that binds you to a specific vendor. They can grab an ARM from any of their vendors and swap the designs around.

So, can it be done - sure. Is it a lot of work - yes indeed it is. Do you need a pretty narrow scope to get it working any time soon? Most certainly.

=======

The only rational way to go on Kinetics is KDS if you are doing this as a hobby. If you have a real budget, Kiel and IAR are both out there. They are dependent to some degree on the same "stuff" as KDS. That sort of reduces the advantage you get from them if "perfection" is your goal.

Bob

Bob
 

Offline VIGNESH BALAJITopic starter

  • Newbie
  • Posts: 7
  • Country: in
Re: How to create our own stable IDE
« Reply #27 on: February 13, 2016, 11:27:33 am »
Sure,I used KDS Felt difficult to migrate my earlier project to KDS faced GDB server Errors.

Has Anyone used Bare Eclipse and added The GNU toolchains and used for your Microcontroller Projects?
 

Offline rob-from-perth

  • Contributor
  • Posts: 12
  • Country: au
    • Logicware - Perth's Best Online Electronics Store
Re: How to create our own stable IDE
« Reply #28 on: February 13, 2016, 01:24:51 pm »
If you really are serious about creating your own IDE, it may be worth investigating Atom from Github

It runs on Windows, OSX and Linux and seems like a pretty decent way to go. Its open source and has been
written with developers in mind.

The flight manual, would be a good starting point in terms of 'hacking' the product to your needs.

Offline uncle_bob

  • Supporter
  • ****
  • Posts: 2441
  • Country: us
Re: How to create our own stable IDE
« Reply #29 on: February 13, 2016, 03:07:08 pm »
Sure,I used KDS Felt difficult to migrate my earlier project to KDS faced GDB server Errors.

Has Anyone used Bare Eclipse and added The GNU toolchains and used for your Microcontroller Projects?

Hi

Yes, indeed you can add it all one piece at a time into a bare copy of Eclipse. It does work. It is *far* more complex than simple debugging of KDS. Plan on spending many months getting a custom port working.

Bob
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf