Go to Post In the end any amount of time can work, just be smart about how you use it. - Jay O'Donnell [more]
Home
Go Back   Chief Delphi > Technical > Programming
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #11   Spotlight this post!  
Unread 09-12-2004, 10:22
Unsung FIRST Hero
Mike Betts Mike Betts is offline
Electrical Engineer
no team
Team Role: Engineer
 
Join Date: Dec 2001
Rookie Year: 1995
Location: Homosassa, FL
Posts: 1,442
Mike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond reputeMike Betts has a reputation beyond repute
Re: c debugger

Continued...

I was going to let my last post stand but this is still sticking in my craw...

First, you are comparing a desktop software package which sells several millions of copies (hence revenues) against an embedded processor software package which sells several thousands (they make their profit in chip sales).

Add to that the fact that Mr. Gates and company make a product which is no longer ANSI compatible (therefore code is not portable).

An embedded processor software package is targeted at degreed engineers who program for a living. An embedded program is usually very small and compact, no megabytes wasted in useless hooks to windows... The embedded programmer's task is to make his code as small and efficient as possible.

The smaller and more efficient the code, the less chance of bugs to begin with. We usually don't need (or want) a lot of fluff...

The design cycle is usually to build a prototype development platform which accepts ICE and also has extra debugging aids added by the engineer. You only build a couple of these. After you have developed your code and debugged your hardware interfaces, you then redesign for a bare bones production system. Debugging in the production system, if required, is usually done by oscilloscope, logic analyzer and (perhaps) by the single LED you left on the board...

Actually, I just exaggerated... We normally do put a diagnostic serial port on the board to aid in maintenance.

I have used a lot of embedded development systems and rate MPLAB as one of the best I have seen (especially for a target chip which costs $5 each).

If you want to work in large computer systems with object oriented code which fill volumes of notebooks (if you were to print it out), go and be at peace.

I, personally, don't want a Pentium with it's inevitable blue screen of death determining if the airbag in my truck is going to deploy or not... I'll take a nice, small uC (with nice, small expertly written code) any day.

'nuff said... Sorry about the rant.
__________________
Mike Betts

Alumnus, Team 3518, Panthrobots, 2011
Alumnus, Team 177, Bobcat Robotics, 1995 - 2010
LRI, Connecticut Regional, 2007-2010
LRI, WPI Regional, 2009 - 2010
RI, South Florida Regional, 2012 - 2013

As easy as 355/113...

Last edited by Mike Betts : 09-12-2004 at 10:30.
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Debugger and Simulation in new IDE? authgeek1218 Programming 1 08-12-2003 18:39


All times are GMT -5. The time now is 14:07.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi