I am looking for a devlopment board specifically for the 8051 family of microcontrollers. My budget is approximately $70. I want the board to help me write small/medium programs, just to start off my embedded endeavours. But of course I want it to be helpful in the long run as well. My actual ambition to create my own embedded OS because I feel that is the best way to learn about embedded systems. For the time being I shall be content with the 2K keil evaluation compiler and other free assemblers.
I have been following up previous posts in this group but so far not been successful enough in finding a satisfactory answer to my quest.
I live in India hence an Indian vendor would be preferrable. More specifically I live in Pune, which is a city near Bombay so that I can always get my board from Bombay in case I can find a vendor there.
Other suggestions regarding foreign based companied would also be helpful.
Thanks in advance for any of your suggestions and assistance.
Wishing you Happy embedding! regards, Seemanta Dutta
In my opinion the best way to start is to take a flash programmable
8051 controller like the atmel ones - either the simple "S"-family like 89S52 or the more complex "X2" ones - and build your ISP-cable. Should be done in half an hour. There is also a free C-compiler out there: sdcc. Take a look at
formatting link
. A very thourogh source of information is the forum on
I looked up atmel website and found some stuff. But please clear one doubt for me. Even if I build my own ISP cable ( I also searched the net for it too..) won't I need specialised software for programming the chip ulness of course I decide to write my own programmer.
There is free software readily available. For example, I did some projects using the 89S53 and I used a simple STK300-compatible ISP dongle with PonyProg. A schematic for the dongle is available on PonyProg's website.
Irrelevant. (besides most serious engineers can't afford free tools.)
(inefficient)
optimising? Not compared to any of the commercial compilers. In fact it has a very LOW code density and virtually the worst data density..
And you can justify that statement? Remind me, which test suites has it passed? I doubt very much if it is remotely complies to the C standard.
Besides if it is fully ISO-C compatible if will need a lot of extensios for the 51.
Very few use that these days There are over 550 51 types out there using many different cores
Knowing how difficult it was for the commercial compiler vendors to support it with the support of Dallas I am very surprised that it can. This memory models.
I know it is that far different that KEil for example use a different linker for it to their standard linker.
that explains why it is so inefficient.
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ \/\/\/\/\ Chris Hills Staffs England /\/\/\/\/\ /\/\/ snipped-for-privacy@phaedsys.org
ROFL. A little disingenuous, no? So, what exactly is Keil supplying in their GNU package?
I would say, they are bowing to the inevitable. There are more reference materials and real products out there using free compilers and assemblers than buyware. Open-source operating systems (which, I remind you, are designed to be compiled with open-source compilers - and are exceedingly difficult to build with alien proprietary toolchains) are increasing in market share at the expense of closed-source products. I agree in advance with the criticism that these comments are much more applicable to the 32-bit market than the
8-bit market, but I point out that 8-bit cores seem to be bottoming out on price while 32-bit parts are still dropping. For practical purposes, gcc is the "natural" choice for a 32-bit application, and anything else is a maverick choice made because some customer requirement mandates use of a particular operating system that won't build with gcc. A vendor of 32-bit parts who doesn't explicitly support gcc is not going to enjoy significant sales.
Buyware tools are exceedingly low-volume products with long product lifecycles (i.e. slow bug support) and dauntingly high pricetags. It has been my consistent experience that the "support" and "guarantees" bought with the money are utterly worthless. Buyware tools have just as many warts and quirks as free tools. But buyware is maintained at by-the-hour engineering rates, and nobody can or will lift a finger to fix the closed-source problems unless they are paid to do so. Open-source tools are fixed as and when they break, comparatively speaking.
I didn't make the statement, so I don't really need to. It's copied from the first paragraph of the SDCC homepage on sourceforge. I'm offering you a can of Coke and you're challenging me to provide a certified assay proving that it isn't Pepsi, and furthermore launching into a diatribe as to why Coke is inferior to Pepsi.
Free is the future, which in all things encroaches continuously upon the present.
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.