AVR-Chat

I think you should contact the company and tell them what you want if the code is good.  If the code is junk then do it from scratch.

PJ

--- On Wed, 6/24/09, David VanHorn <microbrix@gmail.com> wrote:

From: David VanHorn <microbrix@gmail.com>
Subject: Re: [AVR-Chat] REVERSE ENGINEERING
To: AVR-Chat@yahoogroups.com
Date: Wednesday, June 24, 2009, 1:23 PM











    
            
            


      
      >  Unless you are only trying to change a couple of constants in the code

> your odds of success here are pretty marginal.  The code may not have

> been written in assembly, and assembly instructions are all that you

> will be able to read back.  I've yet to see an assembly to C translator

> or assembly to Basic translator, depending upon the original language

> the developers used to create the code.



Well, it's called a human being.  :)



Walk thru the asm, work out what's being done, and write new code.

You can also try to work out what parts are the variables that need

tweaking, if that's the problem.



Question is, is it less expensive to just write it from scratch,

knowing where the I/Os are and what it's supposed to do?



-- 

There is no computer problem which cannot be solved by proper

application of a sufficiently large hammer.


 

      

    
    
	
	 
	
	








	


	
	

[Non-text portions of this message have been removed]

On Wed, Jun 24, 2009 at 8:09 PM, PEZHMAN BOUSSINA <pbpc@yahoo.com> wrote:

> I think you should contact the company and tell them what you want if the
> code is good.  If the code is junk then do it from scratch.
>

Amazingly often, the answer is "NO", even when the prospective client is
willing to pay very well.

I've been on both sides of that one. Ex:  Verifone refused all advances for
several years, eventually one outfit wrote their own ROM for the
applications they wanted to do.  They bought our terminals (at full price)
popped out our roms, and put theirs in.

I never heard a coherent explanation of why we refused this so strongly.  In
the end, it was a win-win except for the lost time to market while they
developed their rom.  It never caused us any grief.

Sometimes those little customers turn into big customers, and I've found
that they frequently remember who helped them get there, and who didn't.

I've never thought that it was a good idea to say "no" when a customer is
willing to buy a product, even if there are changes needed.  "That will be
expensive" is definitely acceptable to say, but I really try to avoid
telling paying customers I don't want their money. (For the pedants, this
does not include agreements to do illegal things, or rip someone off)


> --
> There is no computer problem which cannot be solved by proper application
> of a sufficiently large hammer.
>


[Non-text portions of this message have been removed]