Embedded Systems Programming, June 1990


Vol. 3 No. 6, June 1990

Table of Contents

Phase jitter in the realm of Platonic ideals? Software after-shocks? You need fault-tolerant design, bunkie.

FEATURES

“Lessons in Debugging”
by Anthony M. Castaldo.
When it comes to debugging software, even the best computer-science education is no substitute for realworld experience. Here are some guidelines to help minimize the pain of the debugging cycle.

“Remote Controllers”
by L. Brett Glass.
Upgrading an existing industrial controller often translates into adding support for remote processing and control. As Glass explains, adding these capabilities can be quick and easy—if you're familiar with microcontrollers such as the 8051.

“Launching C”
by Jack Woehr.
The return of the Cookie Monster. Last month, Woehr showed how Forth's multitasking capabilities could be used in debugging assembly language applications. This month, he follows up with a look at how amenable C programs are to the same approach.

“Designing with Tolerance”
by Walter Banks.
Just how reliable is your software? Are your customers becoming fault-intolerant? Applying some simple design rules at the beginning of a project can tremendously improve system reliability.

“Cruising the Seven (Eight?) Cs”

by Tyler Sperry.

COLUMNS

#include: “More Signal, Less Noise”
by Tyler Sperry.

Real-Time: “Paladins of the Realm”
by Tyler Sperry.

When in ROM: “Microsoft's ROMable DOS”
by Ray Duncan.

Programmer's Sourcebook: “Duty Cycles, Part Two”
by Bruce A. Bergman.

Break Points: “The Zen of Diagnostics”
by Jack G. Ganssle.

State of the Art: “Serious Real-Time”

by P. J. Plauger.


All material on this site
Copyright © 2012

CMP Media Inc./UBM Electronics/UBM–All rights reserved.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.