Hello, Since this is my first post I will introduce myself: I'm Christian, I'm Italian and I work as a developer, building any kind of application using C# (web/windows/compact). I have some experience in building application on smart devices since I wrote apps using compact framework. Long time ago (5 years ago) I built a custom linux distribution on a 1.72mb floppy with a working compiler (tcc) using uClinux, at that time I used to have only 1 os on my p133: slackware. I know lot of languages: Sql / Java / RapidQ / Q-Basic / 3 kind of differents assembly / Brainf. / pascal-delphi blah blah blah...
I would like to start developing something for the 8052, I want know if there is a standard emulator for testing code and try to build something on it. I''m interested in opengl-es and I would develop how mono:8052 works
Thanks.
"I want know if there is a standard emulator for testing code"
No. They are specific to one device, or a family of devices.
But Keil's uVision does include a software Simulator...
"I''m interested in opengl-es"
What's that?
Remember: the 8051 is a small, simple microcontroller - it is not at all suited to the kinds of "big system" applications you are used to!
For an 8051, 32K of code is a "big" application!
Another way: A couple of kB of variables represents a big application - not really room for any graphical deskop image :)
For your OpenGL ES work you would be better off looking at an ARM chip. Preferably an ARM chip with LCD interface and 2D acceleration.
Look through the OpenGL ES documentation - it would probably contain a list of supported hardware. If that is just raw chips or the the target hardware is full platforms is something for you to find out.
I suspect that's true!
Also, ARM chips have a ((much) more) standard debug interface - so you (probably) wouldn't need different debug adaptors for different chips...
http://www.keil.com/ulink2/
would be to use SILabs chips, they have built-in emulation and the software is free.
Erik
but they are still "just" (sic?) 8051s - so (potentially) easier to program & debug, but no more suited to "Big System" applications like 3D graphics!
en.wikipedia.org/.../OpenGL_ES
I would like to start developing something for the 8052 and a 100MHz one clocker can do quite a bit.
It isn't so much a question of speed, as a question of memory adress ranges.
I do not think that a C51 processor is suitable for controlling 320x200 pix graphical LCD display. Think about the LCD on your mobile phone or your MP3 player.
People shouldn't start using a C51 in a project unless it is an advantage to select the C51 family. In case of a tie, then a more general processor should be selected, since that improves the chances of future migration of the sw to another processor.
I would like to start developing something for the 8052 is out of the question.
I agree that a full graphix LCD is not a '51 app.
"a 100MHz one clocker [8052] can do quite a bit."
You are speaking from the posisiton of knowing the 8052 and its capabilities; But look at the context the OP is coming from - in that context, I think he might find even a 100MHz one-clocker rather limited...
;-)
It's all relative...
"...I would develop how mono:8052 works..."
Develop mono for an 8052 ??!!
I wish you luck (even on a 100MHz one-clocker).