Wednesday, December 6, 2006
This example for PIC12F675 implements set of “actuators” and “generators” controlled via USART. Actuators produce one 300 ms pulse when it receives command ‘ON’ and three 100 ms pulses delimited with 100 ms spaces (pauses) on command ‘OFF’. Generators, when turned on, produce pulses and spaces of the specified duration (1..255).
Monday, November 20, 2006
VELOOS is an object-oriented message-triggered cooperative operating system for 8-bit Microchip microcontrollers licensed to public under the Open Software License Release 1.0 includes VELOOS kernel and two timer drivers (TMR0 and TMR2 based). It has been tested on the following devices: PIC12F675, PIC16F690, PIC18F248. Download VELOOS v.1.0
Wednesday, November 15, 2006
This post continues series of examples and describes how VELOOS can be used for implementing time-triggered applications.
Friday, November 10, 2006
The previous post gave a brief introduction to VELOOS design idea. VELOOS assumes that an application is decomposed on PDOs (Process Data Objects). This post describes by example features provided by VELOOS for implementing PDO.
VELOOS – Very Low Overhead Operating System VELOOS is a message-triggered cooperative operating system designed to run in places were a large vehicles can not run. Its implementation for PIC12F takes less than 200 instructions and 20 data registers1. With addition of a timer driver, it becomes a time-triggered RTOS.
Friday, September 15, 2006
This post collects and organizes discussion theses posted on different forums.
Saturday, September 9, 2006
In this post I present my vision of e# reflected through history of assemblers. For each stage in the assemblers’ history I am providing presumptive equivalents in e#, incrementing the complexity of each next example.
Saturday, September 2, 2006
I envision the following benefits of using e# It will allow writing better quality code in shorter time It will reduce maintenance cost by providing abilities for regression testing (on a simulator or in-circuit debugger) It will reduce impact of migrating to another device/platform
Wednesday, August 30, 2006
Refine vision Establish requirements Design a device metamodel
Preface I would like to discuss with you my ideas on new programming language for embedded applications, denoted further as e#. I value your time and therefore in this post I am trying to be short and precise as much as possible.