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,ve installed the Compiler and I can,t get even the simplest code to compile properely.
Anyone know where the fix for this bug is?
Or is it a limit of the demonstration version?
void main(void) { cout << "Hello world!"; }
Hi Carsten,
Nice to hear from somebody who's tried something similar :)
Yes, you're right about the IAR demo limitation - It is fully functional but limited to 30 days use and not to be used for commercial applications. Now the demo has been done successfully, I have the funds to buy the full package.
With regards to the Ceibo demo package, I wasn't sure that it was actually using the Keil compiler underneath???
When I looked at the code it produced (i.e., assembler listing files) it seemed more like that of the SDCC package - But I might well be wrong about that.
I would say that the word 'complex' in this environment is a relative term. Fortunately for me, code and data space are decent (512Kb each using banking) and speed is not critical. If the project goes further forward, I would probably recommend a higher speed core (probably Dallas) for the next boards to compensate for the extra overhead of the C++.
I can understand that for more pressured hardware, the use of C++ is probably not the best choice. As for me, I'm glad I pursued it.
Hi Filip,
the CEIBO produces C code from your C++ source for the KEIL compiler. When you install the CEIBO package, you can work from the KEIL IDE writing your program in C++ . When you hit the compile button, the CEIBO makes C code out of your *.cpp files and then hands it over to the KEIL compiler. You never get to see the actual C code.
Well, 'complex' of course was meant with respect to the 8051 environment. With 512 KB of available space, you certainly can handle a lot of C++ overhead. But usually much more code takes much more execution time when running on your system. On the one hand, you state that speed is not critical on the other hand you say that you might need a faster core to compensate... To get the desired performance you have to decide what's the better approach for you. When you are faster in development using C++ you can probably afford a (more expensive) high speed core. But when you're aiming to sell many units of your product, you might better be using C only, even if it takes you longer to write your program. (Of course you could also switch to another core architecture. When the requirement is 'C++ and speed', an 8051 is not necessarily the first thing, to come in mind...)
As usual, there's not always just black and white but for me, C++ is no longer an option in my 8051 applications.
Carsten
Hmmm ... When I installed the Ceibo demo package it was on a clean PC (i.e., no Keil etc) and the only thing I got was the Ceibo IDE.
I've just looked back in the 'bin' folder and found the givaway SDCC.EXE and SDCCLIB.EXE. No Keil components to be found.
Ok ... I see ... It uses Keil if installed.
On the one hand, you state that speed is not critical on the other hand you say that you might need a faster core to compensate...
Sorry, what I mean is that future requirements for the project might need more processing - That might justify a faster core.
I take your point concerning costs but, fortunately for me here, this project will only ever be small(ish) quantities and the processor etc is not a real issue.
However, that said, I may venture into ARM ;)