Breaking News
Newest First | Oldest First | Threaded View
Page 1 / 2   >   >>
User Rank
RE: Who copied who?
MeasurementBlues   3/6/2014 12:19:34 PM
My very first task working in Product Engineering at Analog Devices (1980 and fresh out of college) was to compare an ADC module (yes module at that time) with one from the arch competitor, Analogic. I had samples of both and copies of the ADI schematic so I traced them both. They were identical so I asked the department manager "Who copied who?"

His response: "We copied Bernie."

We never mentioned Analogic by company name, just "Bernie."

zewde yeraswork
User Rank
Re: Nature reverse engineering
zewde yeraswork   3/3/2014 12:13:58 PM
I have no experience in that regard, but I find natural RE to be an area of real potential. These kinds of techniques can reap a true reward, and do not run the risk--unlike other forms of RE--of being deemed illegal or unethical, at least I hope not.

User Rank
Reverse Eng.
Hossmann   3/1/2014 3:56:24 PM
Started 1974 and seen so many good and bad reverse eng "copying" or just for evaluation and leverage some. Done some myself in evaluation of NEC's 4K DRAM using 3 trans.

Seen a company copyied our watch and even had our initial still on it. A company approached Align Right Mask making shop and offered $20-25K for our Data Base.

I saw a bad copy of INTELs 2147. And that cost the company millions of dollar. I did a carefull design of 9148 same, one was 4Kx1 and mine was 1Kx4.

Also there was a company in Canada that would do many reverse engineering circuit and "process".

Now with so many metal layers it is a big challenge.

Max The Magnificent
User Rank
Re: Knowing your competitor
Max The Magnificent   3/1/2014 10:41:17 AM
@PR Guy: ...technologists must invest in staying highly aware of what competitors are doing...

I don't have a problem with that -- what I don't like is simply duplicating something that someone else spent a lot of time, money, and creative effort inventing.

Grand PooBah
User Rank
Knowing your competitor
Grand PooBah   2/28/2014 8:37:08 PM
Sounds like "sometimes" RE occurs beneficially far more often than many may beieve. Not a bad thing.

Aside from doing it with your own products when there's missing info, technologists must invest in staying highly aware of what competitors are doing...obeying Sun Tsu's rule: "Know your enemy." DIY RE now is likely far beyond many internal engieering teams' abilities or time capacity. So a few highly focused businesses offer very specialized expertise and services.

Max The Magnificent
User Rank
Re: Sometimes You RE Your Own Products
Max The Magnificent   2/28/2014 5:58:14 PM
@HankWalker: Reverse engineering must also be used when you are making modifications, improvements, additions to an existing hardware or software product with poor or no documentation (or designers) available.

Good point. Early in my carear I spent a lot of time writing functuional test programs for PCBs. I was given a PCB that was claimed to be "known-good" (but after wasn't) and a schematuc that was said to be at the same revision level as the board (but often wasn't) and ... that was it.

It was up to me to try to determine what the board was supposed to do and how it did it, and then write a test program that fully exercised the board. Of course this wa sback in the very early 1980s when boards were much simpler than they are today, but it still gave me a lot of mental exercise.

As a by-product, this was quite possibly the best training I ever received LOL

User Rank
Response to poor documentation
betajet   2/28/2014 1:27:10 PM
I remember when I had to make an RTOS (which we had licensed) interoperate with our code.  The RTOS documentation for the particular instruction architecture was incomplete.  You were supposed to use a "board support package", but if your board wasn't on the list -- e.g., if it was your product rather than a standard development board -- the documentation was simply not there.  (This particular RTOS at one time had excellent, complete documentation for a different architecture, but they had been acquired by a Large Company who obviously felt that complete documentation was unprofitable.)

So I had to disassemble the task switch machine language so that I could see how it was using and saving registers.  Once that was clear, the rest was pretty easy.

User Rank
Re: Sometimes You RE Your Own Products
AZskibum   2/28/2014 12:33:37 PM
Absolutely! Reverse engineering is often an essential skill when you are tasked with modifying your own company's existing product or re-using IP. Designers come & go, and documentation often lacks important details that another designer needs to know in order to successfully modify a product or IP block. Black box reuse (don't change anything) is a luxury you don't always have on a new product. As soon as you hear the words "reuse with a few changes," it's time to bring out those reverse engineering skills!

User Rank
Sometimes You RE Your Own Products
HankWalker   2/28/2014 12:06:48 PM
Reverse engineering must also be used when you are making modifications, improvements, additions to an existing hardware or software product with poor or no documentation (or designers) available. One time I needed to know something, and one designer was on pregnancy leave and the other one was on a honeymoon in Tahiti! At least I knew who the designers were, but I still had to reverse engineer the system to get the answer I needed.

In some sense, reverse engineering is about keeping the system model in sync with the implementation. Or creating a system model if you can't find one.


User Rank
prabhakar_deosthali   2/28/2014 7:17:04 AM
Reverse engineering is a fun, whatever be the legality or illegality behind it.

Way back in 1988, as a free lance assignment, i really enjoyed the reverse engineering of the MS-DOS "debug "program . I used the "debug" program itself to understand its working, its data structures and successfully ported it onto a locally made 8086 development kit.

In my opinion, reverse engineering is a very good learning tool for engineers!



Page 1 / 2   >   >> Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)

What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.

Brought to you by:

Like Us on Facebook
Special Video Section
The LTC2380-24 is a versatile 24-bit SAR ADC that combines ...
In this short video we show an LED light demo to ...
Wireless Power enables applications where it is difficult ...
LEDs are being used in current luxury model automotive ...
With design sizes expected to increase by 5X through 2020, ...
Linear Technology’s LT8330 and LT8331, two Low Quiescent ...
The quality and reliability of Mill-Max's two-piece ...
LED lighting is an important feature in today’s and future ...
The LT8602 has two high voltage buck regulators with an ...
Silego Technology’s highly versatile Mixed-signal GreenPAK ...
The quality and reliability of Mill-Max's two-piece ...
Why the multicopter? It has every thing in it. 58 of ...
Security is important in all parts of the IoT chain, ...
Infineon explains their philosophy and why the multicopter ...
The LTC4282 Hot SwapTM controller allows a board to be ...
This video highlights the Zynq® UltraScale+™ MPSoC, and sho...
Homeowners may soon be able to store the energy generated ...
The LTC®6363 is a low power, low noise, fully differential ...
See the Virtex® UltraScale+™ FPGA with 32.75G backplane ...
Vincent Ching, applications engineer at Avago Technologies, ...