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.
Hello I'm want to get into embeded systems design and am wondering what the kit I should obatin to get me onto a good start?
if program means put the code into the device, then it is TOTALLY device dependent.
Any sugestions or examples?
No, the next example is expected to come from you - which specific processor (better specify every single little character/digit in the name) that you are interested in programming.
I will not commit to one device, and if you are sugesting that I must do just that then keil is not for me.
Because someone programes a computer does not mean they have to act like one
The problem isn't with the Keil tools. The Keil IDE will support a large number of chips.
The question is what specific variants of chips do you want to be able to download your firmware into. Most people who buy an IDE or an evaluation board have already decided on a chip family, and can then evaluate the behaviour of a number of chips within that family.
But to my knowledge, there does not exist any tool developer who have a product that contains a turn-key solution, including a fully generic programmer that may send any signals to any chips of any chip. If you can't get a tool that supports everything, then you have to figure out why you would need something with so broad functionality. If I need a wrench for my car, it isn't relevant if it can be used with the tiny nuts in a watch, or if it can be used to remove the huge wheel nuts on a large tractor.
Spending a lot of money on the best GP programmer is good if you work as a consultant, and have to be prepared to support as much chips as possible. But it is a waste of time and resources for most people. A GP solution is more complex to use for a specific problem, and the extra options results in a higher probability of failure. A GP programmer may also be slower, since it can't contain the best algorithms for each and every invented chip.
Once more, this problem isn't Keil-related. It is based on a design decision that only you can make. Before you have made that decision, people can not suggest what programmer to use. They can't even tell you if a specific compiler manufactorer have lacking support for the specific chip. Nor can they tell you if the chip has a questionable availability, or any other facts that can greatly affect your life and your productivity.
that has NOTHING to do with Keil.
The programming algorithm for various non-ISP derivatives of the '51 is (almost) never the same as for another derivative.
However, you do not need to "commit to one device", you just need to limit yourself to truly modern devices. Most modern devices (of course, with the exception of smnall Atmel - why would Atmel make it easy - thus why even consider the brand) can be programmed either via JTAG or via COM port.
Now some i.. eh helpful person is going to suggest you buy/ make an Atmel programming jig - do not - this is the issue that has occupied A LOT of forum discussion (it does not work, what is wrong?).
e.g. if you buy a SILabs JTAG dongle/devboard, you can use all ~100 SILabs derivatives and, in addition without any added investment you can use all comport programmable devices such as NXP p89x51Rx2 NXP lpc92x -up, Atmel AT89c51xx2 and whatever other comport programmable devices may exist.
Erik
HEllo
Well I have set my mind on a C8051f120 MCU Dev board to to get familiar. I have taken your advice, and dropped the idea of a universal programmer, I now see it would be a waste of money
Thanks for all your help
kog