HOME  |  NEWS  |  BLOGS  |  MESSAGES  |  FEATURES  |  VIDEOS  |  WEBINARS  |  INDUSTRIES  |  FOCUS ON FUNDAMENTALS
  |  REGISTER  |  LOGIN  |  HELP
Blogs
Sherlock Ohms

Simple Programming Fixes

NO RATINGS
View Comments: Oldest First|Newest First|Threaded View
Page 1/2  >  >>
bobjengr
User Rank
Platinum
PROGRAMMING FIXES
bobjengr   3/3/2014 5:30:24 PM
NO RATINGS
Excellent posts Keith.  I DO remember the punch cards. The university I attended had a "punch-card / computer system" and we all thought it was absolutely star wars. Little did we know the technology that was to come.  I learned programming using Pascal, which I understand is the "teaching" language.  That's really when I determined mechanical engineering was right for me and not the programming profession.  You have to have the patience of Job to be a programmer and there are probably no type "A" individuals that could stand to be involved with this area.  I think it's a fascinating profession and occasionally I write a few C ++ programs to prove I can still do it. 

 

 

rebeccaB
User Rank
Iron
Re: PROGRAMMING FIXES
rebeccaB   3/5/2014 3:56:35 AM
NO RATINGS
Nice post! Most of us can do proggramming but not that successful.

William K.
User Rank
Platinum
Interesting post, good detective work
William K.   3/20/2014 5:11:28 PM
NO RATINGS
Interesting indeed. Not really a software problem, nor really a hardware failure. One of those firmware faults where setting a switch that "seemed like a good idea at the time" had some later unintended consequences. I once fought what appeared to be a hardware noise problem for a week, and it wasn't until I got the software guy to add a way to view the input readings directly that it became clear that it was a path-dependant multi-tasking problem. He had used the same name for two different variables used in separate parts of the program, and depending on the timing between the two parts, that could cause errors. A software problem found by the hardware guy, (me). But it took a week of chasing to convince others that it was not hardware.

mr_bandit
User Rank
Iron
common strings
mr_bandit   3/21/2014 11:44:57 AM
NO RATINGS
Some compilers have a switch that allows you to put strings into flash for embedded systems, They can also check for strings that are exactly the same and only put one copy into flash.

The problem becomes one or two places that use the string as a prototype, ie "The wall is XXX feet wide". where XXX gets replaced. there are proper ways to do this (ie use "%u" instead of XXX.)


I was porting code from a system with lots of RAM - where the strings lived - to a system where the strings needed to live in flash.

Took me a while to find that one...

Hey, Keith! Good to hear from you.

tekochip
User Rank
Platinum
Re: common strings
tekochip   3/21/2014 12:27:33 PM
NO RATINGS
Some micros are a little picky about memory space because the op-code used for fetching from RAM is different than fetching from ROM (or FLASH).  If the compiler is forgiving it will allow you to mix and match where the string is located without objecting.  As always, just because it builds doesn't mean it's correct.  The better compilers keep track of the string's location and issue an error if you try to fetch a variable in RAM instead of variable that is really a constant FLASH.  As a rule I try to make as many objects constant as possible because RAM is typically in much shorter supply than FLASH.


johnr
User Rank
Gold
Re: PROGRAMMING FIXES
johnr   3/21/2014 12:45:19 PM
NO RATINGS
I remember punch cards, too.  That's the reaon I became an electrical engineer rather than a software engineer:  I couldn't imagine spending my time sitting at a keypunch machine or waiting in line at the card reader to run my program.  Obviously, I'm not a good person to ask about the future of technology!

Cabe Atwell
User Rank
Blogger
Re: PROGRAMMING FIXES
Cabe Atwell   3/26/2014 4:43:38 PM
NO RATINGS
Those programming cards had to be punched just right or they wouldn't run correctly. Man what a pain those were.

The fear of dropping the bundle too... geez

Nancy Golden
User Rank
Platinum
Re: PROGRAMMING FIXES
Nancy Golden   3/26/2014 11:18:48 PM
NO RATINGS
bobjengr, your comment about type "A" personalities and programming caught my eye because as a programmer - I sometimes exhibit Type A personality in my urgency to get the task done - I have spent hours straight into the wee hours on a program not due to patience, but due to both the satisfaction of the programming task and the desire to "make it work." Your comment prompted me to google programmer personality types and I came up with a couple of interesting links. The first one describes several different programmer personalities and the second one is a programmer personality test which I took - it was fun and labeled me fairly accurately...

Programmer Personality Types

Programmer Personality Test

bobjengr
User Rank
Platinum
Re: PROGRAMMING FIXES
bobjengr   3/30/2014 11:20:21 AM
NO RATINGS
Hello Nancy--thank you so much for the Personality Test.  Two great web sites.  I took the test and here are the results for me.  I never though I was a loaner but when programming, I really need peace and quite; door shut, TV and radio off, no grandkids, no impending appointments, etc etc.  (Where do you get a life like that?????? )  Again, many thanks.  Bob 

You're a Doer.
You are very quick at getting tasks done. You believe the outcome is the most
important part of a task and the faster you can reach that outcome the better. After all, time is money.

You like coding at a High level.
The world is made up of objects and components, you should create your programs
in the same way.

You work best in a Solo situation.
The best way to program is by yourself. There's no communication problems, you
know every part of the code allowing you to write the best programs possible.

You are a liBeral programmer.
Programming is a complex task and you should use white space and comments as
freely as possible to help simplify the task. We're not writing on paper anymore
so we can take up as much room as we need.

Larry M
User Rank
Platinum
Re: Interesting post, good detective work
Larry M   4/2/2014 6:55:04 PM
NO RATINGS
WilliamK. wrote: ". I once fought what appeared to be a hardware noise problem for a week, and it wasn't until I got the software guy to add a way to view the input readings directly that it became clear that it was a path-dependant multi-tasking problem. He had used the same name for two different variables used in separate parts of the program, and depending on the timing between the two parts, that could cause errors."



I remember a similar situation. A couple of our co-ops had done a senior project involving an FPGA and some code which monitored a communication bus. During development it was rock-solid, but as they added flourishes (and approached their deadline), the device began declaring faults when there were none. The two hardware co-ops asked me to step in. (At that stage, I had a reputation for magic fingers.)

By this point they had done everything they could think of to suppress noise, ground wires everywhere, copper foil tape everywhere else, but still a problem. After looking at a few signals which seemed very clean, I asked to look at the code.

The co-ops apologized that the third co-op, who had written the software, wasn't there to explain it, but they showed it to me nevertheless. It was pretty obvious from the code indentation and white space that the programmer had written the main function and later slapped a loop around it to repeat. What he had not done was to re-initialize a variable used inside the loop. I noticed this after just a minute or two of study.

I added one statement to set the problem variable to 0 and commented it heavily. The project ran as it was supposed to. Later on the programmer co-op called me to ask what I had found, and how I had found it. I pointed out that C automatically sets all integer variables to 0 at first usage and so he had not re-initialized it at each iteration. Had he been programming in FORTRAN he wouldn't have made this mistake because variables aren't initialized. (Probably why I was attuned to the error.)

This success did nothing to diminish my "magic fingers" reputation, either.

Page 1/2  >  >>
Partner Zone
More Blogs from Sherlock Ohms
Sherlock Ohms highlights stories told by engineers who have used their deductive reasoning and technical prowess to troubleshoot and solve the most perplexing engineering mysteries.
Sherlock Ohms highlights stories told by engineers who have used their deductive reasoning and technical prowess to troubleshoot and solve the most perplexing engineering mysteries.
Sherlock Ohms highlights stories told by engineers who have used their deductive reasoning and technical prowess to troubleshoot and solve the most perplexing engineering mysteries.
Sherlock Ohms highlights stories told by engineers who have used their deductive reasoning and technical prowess to troubleshoot and solve the most perplexing engineering mysteries.
Sherlock Ohms highlights stories told by engineers who have used their deductive reasoning and technical prowess to troubleshoot and solve the most perplexing engineering mysteries.
Design News Webinar Series
10/7/2014 8:00 a.m. California / 11:00 a.m. New York
9/25/2014 11:00 a.m. California / 2:00 p.m. New York
9/10/2014 11:00 a.m. California / 2:00 p.m. New York
7/23/2014 11:00 a.m. California / 2:00 p.m. New York
Quick Poll
The Continuing Education Center offers engineers an entirely new way to get the education they need to formulate next-generation solutions.
Nov 3 - 7, Engineering Principles behind Advanced User Interface Technologies
SEMESTERS: 1  |  2  |  3  |  4  |  5  |  6


Focus on Fundamentals consists of 45-minute on-line classes that cover a host of technologies. You learn without leaving the comfort of your desk. All classes are taught by subject-matter experts and all are archived. So if you can't attend live, attend at your convenience.
Last Archived Class
Sponsored by Littelfuse
Learn More   |   Login   |   Archived Classes
Twitter Feed
Design News Twitter Feed
Like Us on Facebook

Sponsored Content

Technology Marketplace

Copyright © 2014 UBM Canon, A UBM company, All rights reserved. Privacy Policy | Terms of Service