Perpetual motion controller

A cheaper alternative is the russian utility Kailinka.

It was originally aimed for smooth transitions from C51 to the CARM compiler, but has proven capable of taking care of the migration from most 8-, 16- and 32-bit controllers but will only target Keil-supported target processors. Note however, that the RealView edition is still in beta, and that some applications may run too fast on the new hardware.

The important distinction with Kailinka is that it auto-generates a platform-translation layer that is automatically linked with the original binary, so there is no need for any recompilation. The original source can continue to be used - and updated - for the original target.

The AP2AC.exe tool can be a bit daunting to use for a beginner, because of the need to correctly select the target controller, but the Kailinka tool only requires that the path to Kailinka is placed before the path to the Keil tools - it will then work as a transparent linker proxy. Since it receives the full set of linker options, there will be no need to specify any configuration. The install program takes care of the path updates, and then it is enough to select "build" or "link".

The Kailinka company are also looking for beta-testers of their new C-Shark tool, that will allow any M$ Visual Studio project to be post-processed for use with Keil-supported microcontrollers. If no undocumented Win32 API are called, then most Windows applications can also be directly run (using a stubbed ntoskrnl.dll) on C51 and ARM platforms.

Note that both of the above two tools do require a valid CARM or RealView license - the evaluation version of RealView will only support smaller PC applications.

A cheaper alternative is the russian utility Kailinka.

It was originally aimed for smooth transitions from C51 to the CARM compiler, but has proven capable of taking care of the migration from most 8-, 16- and 32-bit controllers but will only target Keil-supported target processors. Note however, that the RealView edition is still in beta, and that some applications may run too fast on the new hardware.

The important distinction with Kailinka is that it auto-generates a platform-translation layer that is automatically linked with the original binary, so there is no need for any recompilation. The original source can continue to be used - and updated - for the original target.

The AP2AC.exe tool can be a bit daunting to use for a beginner, because of the need to correctly select the target controller, but the Kailinka tool only requires that the path to Kailinka is placed before the path to the Keil tools - it will then work as a transparent linker proxy. Since it receives the full set of linker options, there will be no need to specify any configuration. The install program takes care of the path updates, and then it is enough to select "build" or "link".

The Kailinka company are also looking for beta-testers of their new C-Shark tool, that will allow any M$ Visual Studio project to be post-processed for use with Keil-supported microcontrollers. If no undocumented Win32 API are called, then most Windows applications can also be directly run (using a stubbed ntoskrnl.dll) on C51 and ARM platforms.

Note that both of the above two tools do require a valid CARM or RealView license - the evaluation version of RealView will only support smaller PC applications.