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
(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)
Saturday, August 26, 2006
This post presents results of my research regarding to assembler history, my thoughts and speculations on assembler syntax.
(Continued)
Saturday, August 26, 2006
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)
Thursday, August 10, 2006
This post presents an alternate implementation of SISAM hardware – a “COM2” plug-in. It is designed for plugging in ahead of a bracket DB9 cable, usually used for accommodating a second serial port. This implementation uses a different MCU – PIC16F88, which allows the application to utilize 30% more RAM for the sampling buffer.
(Continued)
As practice has shown, simple level converter with -12V supply derived from DTR/RTS is not capable to work on high speed. Therefore I have made several tests on speed with the original PNP-based design and a RS232 line driver SN75150 and publish test results in this post. Test summary is given in Table 1.
(Continued)
This post describes how SISAM can be used to build a simple environment for automated testing of embedded applications.
(Continued)
SISAM uses RTS/CTS flow control for reading command and DTR flow control for sending acquired data. This means that PC should set RTS before sending commands and watch for CTS (e.g. use CTS sensitivity option). When PIC goes into data acquisition mode, it sends an ASCII string starting with Y4-MODE:
followed with new mode description. This description can be directly used with mode
command or with BuildCommDCB
function.
(Continued)