Keil Started in 1986 with a C compiler for the 8051 family. This was the first 8051 C compiler built from the ground up for the 8051. There is also an 80C251 compiler Keil produce some of the best C compilers in their class.
There are two versions of the C51 development suite
PK51 Professional suite with IDE compiler debuggers
CA51 Compiler suite of Compiler and IDE
The PK51 Professional Developer's Kit for the 8051 microcontroller family supports all 8051 derivatives including new devices with extended memory and instruction sets (like the Dallas 390/5240/400, Philips 51MX, and Analogue Devices MicroConverters) and classic devices and IP cores from companies like Analog Devices, Atmel, Cypress Semiconductor, Dallas Semiconductor, Goal, Hynix, Infineon, Intel, NXP (founded by Philips), OKI, Silicon Labs, SMSC, STMicroelectronics, Synopsis, TDK, Temic, Texas Instruments, and Winbond.
On-chip peripherals and other key features of the 8051 are easy to access with the PK51 Professional Developer's Kit
The PK51 Professional Developer's Kit includes...
µVision |
|
|
|
|
|
Keil Extended 8051 Compilation Tools |
|
|
|
|
|
Keil Classic 8051 Compilation Tools |
|
|
|
|
|
Target Debuggers |
|
|
|
|
|
You should consider the PK51 Professional Developer's Kit if you...
Will work with a variety of 8051 microcontrollers,
Will develop code for the Dallas 390 or Philips 51MX devices,
Need to write code in C,
Require a simulator or don't have an emulator,
Create complex, single-chip applications that require a small real-time kernel.
The CA51 Compiler Kit includes...
µVision |
|
|
|
|
|
Keil Classic 8051 Compilation Tools |
|
|
|
|
|
You should consider the CA51 Compiler Kit if you...
Will work with a variety of 8051 microcontrollers,
Need to write code in C,
Already have a simulator or emulator.
We agree that you can probably create, test, and debug your embedded applications without a simulator. However, there are several reasons why a simulator (like the µVision Debugger) can make your engineering tasks easier and save you lots of development time.
Customers with the simulator spend less time debugging simple program errors. The simulator lets them learn about things like on-chip peripherals and addressing modes without designing real hardware.
It is our experience that customers who have a simulator require LESS technical support and are able to get up-to-speed with the tools faster. The simulator makes it easy to write and test code and learn about programming your microcontroller.
The µVision Debugger provides complete simulation support for on-chip peripherals like PWM, Power saving modes, A/D, Serial I/O, and so on.
It is easier for our support engineers to explain complex problems if you have a simulator.
It is easier to discover if a problem is in the hardware or software when you use a simulator. For example, if the application works in the simulator and if it works in the emulator, there's most likely a problem with the target hardware.
The simulator requires no setup time. An emulator may require configuration and a target board before you can debug.
The simulator is not a replacement for an emulator. A simulator is a different tool entirely. While an emulator allows you to debug software running on your target hardware, a simulator allows you to debug your software as well as your understanding of the microcontroller and the programming language. There are no real-time debugging effects of a simulator.
For debugging embedded applications, we have a general list of favourite tools that Keil use in-house.
Logic Probe
Digital Multi-Meter
High-speed Analogue Oscilloscope
High-speed Digital Storage Oscilloscope
Logic Analyzer (with a disassembly pod)
Emulator
Software Simulator
It is always a difficult trade-off when deciding what you need. However, a simulator is relatively inexpensive and has a great utility value for the price.