I'm looking for help disassembling an Ihex data file for a Renesas M16c/62p. I tried the objdump, rec0mpiled for the m16c-m32c series processors, but the assembly that was left over didn't make sense. I'm looking for any information on how the Renesas compiller packages the program for conversion to Ihex and upload to the processor. Or if anybody has an idea of another dissassembler that works on the M16c Hex code.
Thanks In advance.
Mike
On Mon, 12 Nov 2007 20:08:46 -0500, I said, "Pick a card, any card" and mgburr.at.comcast.net instead replied:
Generally speaking, hexes can be removed and/or invoked by animal sacrifice. This is particularly effective at the solstices. There's one coming up in December. Be ready.
-- Ray
Did you check a few opcodes to make sure it was decoding m16c opcodes, and not m32c opcodes?
When I ran OBJDUMP i used the tag for the m16c flag. I dropped the disassembled .asm into the Renesas emulator and tried to build it, that's when it told me I had 61235 bad command lines. It didn't pick up any. The binutils package says it's supposed to have both sets of opcodes, but I tried to build it as cpu with the m32c series and it failed there also. I was poking around the users guide for the processor, and it looked like there was an extra step to compress it for downloading to the processor. Do you know if the binutils takes into account the renesas build utilities?
If the Renesas tools aren't using standard intel hex format, then binutils will not be able to read them.
As a check, you can use objdump's "-h" option to see what memory ranges it thinks it's decoding. If they don't make sense, it probably doesn't understand the file format. Even an SREC file will give meaningful address ranges this way.
I took a look at the memory ranges, they were the ones addressed in the renesas manuals for running as a processor. I also compiled some known asm from inside renesas HEW, and then disassembled it. It didn't come back to the same asm code. I can paste in the decompiled code along with the first parts of the hex file if needed.
If you want to send me a small asm source file and the ihex it produces, I'll see what I can do.
Are there any specific asm calls that you think that might make it easier to find the unique key to decript, or would you prefer some standard lines that should show common progression?
Mike
I tried a know entity for the asm, and compiled it through, then did dump from OBJDUMP. Those work, so now i'm looking at why when th original is dumped it doesn't pickup the original addresses and why i gets split into 5 sections. Thanks for the ideas DJ
Mike
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.