Eugene Hutorny

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.

(Continued)

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 registers¹. With addition of a timer driver, it becomes a time-triggered RTOS.

(Continued)

This post collects and organizes discussion theses posted on different forums.
(Continued)

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.
(Continued)

I envision the following benefits of using e#

1. It will allow writing better quality code in shorter time
2. It will reduce maintenance cost by providing abilities for regression testing (on a simulator or in-circuit debugger)
3. It will reduce impact of migrating to another device/platform

(Continued)

1. Refine vision
2. Establish requirements
3. Design a device metamodel

(Continued)

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.

(Continued)

Pages: 1 2 3 4

This post presents results of my research regarding to assembler history, my thoughts and speculations on assembler syntax.
(Continued)

This post provides my look on MP ASM and an attempt to analyze and decompose it on parts. Despite this post provides ‘partitioning’ of a MP ASM only, many similarities can be found in other assemblers.

(Continued)

This post expresses my thoughts on assembler vs HLL use for an embedded project.

(Continued)