Recently I saw a another embedded tool solution around great Code::Blocks IDE
[Code::Blocks(EPS edition) with GNU compiler only. They provide 25% of FLASH capacity in FREE version.](http://www.comsytec.eu/en/online-store/detail/detail/34-nastroje-pre-vyvoj-softveru-software-development-tools/flypage|eps/112-embedded-plugin-suite-embedded-plugin-suite?sef=thcfp&vmcchk=1)
Bought an STM32F4Discovery board awhile back, been looking for a decent IDE setup as well.mindthomas:
I totally agree with you on the CooCox IDE - it’s a great solution for hobbyists who don’t have thousands of dollars to spend on a Keil license.We have been using the CoIDE for quite a while now and we really like it. Especially because it also contains the repository which makes a new project even easier to create.
Is this CooCox IDE still a relevant option as far as freebies go?
About the only other option I’ve considered is one of the mikroe compilers even at $250USD (probably leaning more towards mikroBasic for ARM, I’m not too fluent in C, and don’t really feel like relearning myself completely unless it’s absolutely necessary).
CooCox is an option although you are going to have to forego any idea (very highly recommended) of using BASIC.skimask:
Bought an STM32F4Discovery board awhile back, been looking for a decent IDE setup as well.mindthomas:
I totally agree with you on the CooCox IDE - it’s a great solution for hobbyists who don’t have thousands of dollars to spend on a Keil license.We have been using the CoIDE for quite a while now and we really like it. Especially because it also contains the repository which makes a new project even easier to create.
Is this CooCox IDE still a relevant option as far as freebies go?
About the only other option I’ve considered is one of the mikroe compilers even at $250USD (probably leaning more towards mikroBasic for ARM, I’m not too fluent in C, and don’t really feel like relearning myself completely unless it’s absolutely necessary).
Are you recommending to use BASIC?rmteo1:
CooCox is an option although you are going to have to forego any idea (very highly recommended) of using BASIC.skimask:
Bought an STM32F4Discovery board awhile back, been looking for a decent IDE setup as well.mindthomas:
I totally agree with you on the CooCox IDE - it’s a great solution for hobbyists who don’t have thousands of dollars to spend on a Keil license.We have been using the CoIDE for quite a while now and we really like it. Especially because it also contains the repository which makes a new project even easier to create.
Is this CooCox IDE still a relevant option as far as freebies go?
About the only other option I’ve considered is one of the mikroe compilers even at $250USD (probably leaning more towards mikroBasic for ARM, I’m not too fluent in C, and don’t really feel like relearning myself completely unless it’s absolutely necessary).
When it comes to microprocessors and even programming in general I would disrecommend using or even learning Basic.
I did that mistake in my early days, making programs for Windows. And look at me know, right now I am stuck making programs in Visual Basic .NET instead of the more feature rich Visual C# .NET, which is used more commonly on the market.
So for microprocessors especially, programming in C makes all your development a lot more versatile and easier to use on different devices if necessary.
But that’s just my opinion!
No, I am not recommending the use of BASIC that the previous poster indicated he wanted to stay with. It is good that you realized your mistake of going with BASIC. The issue is that many beginning developers are under the misconception that BASIC is easier to use and has all the features/capabilities of C when in reality BASIC encourages sloppy/bad programming habits and has nowhere near the breadth of C which is the industry standard (whether MCU or PC applications).
Ya, I knew that.rmteo1:
CooCox is an option although you are going to have to forego any idea (very highly recommended) of using BASIC.
Two totally different worlds.
meh…may as well prep myself for a steep learning curve.
Ahh, sorry for my misunderstanding. It was the word "forego" in your previous comment that I must have missed :)rmteo1:
No, I am not recommending the use of BASIC that the previous poster indicated he wanted to stay with. It is good that you realized your mistake of going with BASIC. The issue is that many beginning developers are under the misconception that BASIC is easier to use and has all the features/capabilities of C when in reality BASIC encourages sloppy/bad programming habits and has nowhere near the breadth of C which is the industry standard (whether MCU or PC applications).
I totally agree with your statement about the misconception of BASIC - and I can only say that I’ve been in the same situation.
That sounds like a case of the 'pot calling the kettle black'. If you are trying to imply that C encourages good programming habits then you could not be further from the truth. OK - it might be marginally better than BASIC and has improved a little since the 1970's but it is far from ideal.rmteo1:
when in reality BASIC encourages sloppy/bad programming habits
Do you mean stuck because you haven't learnt C# yet? Otherwise you are not stuck - you could start using C# today without having to throw away your VB code. .NET is specifically designed so that you can intermix code from different languages (more than 40 the last time a counted a few years ago). We regularly use a mix of C# and Component Pascal. In your case you could even decompile your VB code to C# code if you wanted to.mindthomas:
And look at me know, right now I am stuck making programs in Visual Basic .NET instead of the more feature rich Visual C# .NET, which is used more commonly on the market.
Actually it is not so much a (steep) learning curve as much as a mindset change. For someone already familiar with programming/coding concepts like yourself it can be accomplished in a very short time frame (I am talking about just a few days) - at least that was the case in my experience.skimask:
Ya, I knew that.rmteo1:
CooCox is an option although you are going to have to forego any idea (very highly recommended) of using BASIC.Two totally different worlds.
meh…may as well prep myself for a steep learning curve.
BTW, these days I work with a programmming language called MQL4 (which is based on C) for applications in the financial investment arena - totally unconnected with microcontrollers and such but it does illustrate the leverage you derive from a knowledge/familiarity with C. Here is an example code fragment:
if(myOrderType == 2 && ContinueOpening)
{
if((LastPrice-Ask) >= Pips*Point || OpenOrders < 1)
{
BuyPrice = Ask;
LastPrice = 0;
//----
if(TakeProfit == 0)
tp = 0;
else
tp = BuyPrice + TakeProfit*Point;
//----
if(InitialStop==0)
sl = 0;
else
sl = BuyPrice - InitialStop*Point;
//----
if(OpenOrders != 0)
{
mylotsi = lotsi;
for(cnt = 1; cnt <= OpenOrders; cnt++)
if(MaxTrades > 12)
mylotsi = NormalizeDouble(mylotsi*1.5, 1);
else
mylotsi = NormalizeDouble(mylotsi*2, 1);
}
else
mylotsi = lotsi;
//----
if(mylotsi > 100)
mylotsi = 100;
OrderSend(Symbol(), OP_BUY, mylotsi, BuyPrice, slippage, sl, tp, NULL, 0, 0,
Blue);
return(0);
}
}
I guess that's what I've been thinking.rmteo1:
totally unconnected with microcontrollers and such but it does illustrate the leverage you derive from a knowledge/familiarity with C.
Once you get over the syntax of your generic C style programming, it seems like damn near everything else is based off that same style of thinking, but with different keywords.
Ok, surely it’s not that simple, but then again, surely it’s not that complex.
aw hell…just painted myself into a corner 