Ruell-
Include files are not going to help to recreate C code. To customize a
codec in object form, you will need to look at assembly code using CCS,
and painstakingly -- going line by line -- determine where key codec
functions are called. Then you can "hijack" those functions, replacing
call addresses with your own code, and perform customized functions. This
process will take many months -- it's not easy to determine what asm
functions are doing. Think of a big "code map" on the wall where it takes
days to fill in each small area. Did the provider include the symbol
table in the object code? If so that makes a huge difference.
It would help if the codec is a standards-based implemementation and has
"reference C code" available online. Then you might have some idea of
what to look for, assuming you have the symbol table. That's always a
good thing to check before purchasing the codec -- what standard did they
follow? What code base did they start with?
That's the hard way. The easy way is to purchase source code from the
provider, although it can be expensive. If you needed customization, why
did you go with this particular provider in the first place?
-Jeff
> I need your expert advice on this;
> we have the header for the JPEG codec purchased from a 3rd party
> vendor, this header file contains hex codes for DSP for JPEG
> decoding., this header file contains code to be loaded to DSP.
> AS what i KNOWN this header file is generated using coff2c FROM a .out
> source ( DSP binary ). We want to debug/customize the codec but the
> 3rd party vendor doesnt provide the source code to it ( and they will
> not give the source code . How can we do it? Is there a way to reverse
> engineer the .H file header to convert it back to .out and or to assembly?
>
> Ex:
> coff2c generated Header -> .Out -> Assembly -> C code
>
> Is this posible or not?
>
> *damn these costcutting theyre letting me solve the problem the hard
way.