public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: "Trenton D. Adams" <tadams@theone.dnsalias.com>
Cc: "'Trenton D. Adams'" <tadams@extremeeng.com>,
	'eCos Discussion' <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] objdump for binary file
Date: Tue, 21 Aug 2001 13:28:00 -0000	[thread overview]
Message-ID: <20010821152957.A1338@visi.com> (raw)
In-Reply-To: <000801c12a7c$99c8ceb0$090110ac@TRENT>

On Tue, Aug 21, 2001 at 02:05:18PM -0600, Trenton D. Adams wrote:

> > > I compiled an eCos program and then copied it to a binary file.
> > > Is there a way of dumping the assembly now?
> >
> > No.
> >
> > Run arm-elf-objdump --source on the ELF file.

> Ok, if the arm-elf tools can't do it, how would I do it? 

It can be done by converting the file back into ELF format.

> I want to reverse engineer a driver for the PCMCIA controller
> I'm using.  I think it's in plain binary form, but I'm not
> sure.

You've got an eCos program in binary-only and you need to
reverse-engineer it?  Ouch.

Have you reverse-engineered machine-level stuff before? You
probably need to find a good interactive disassembler that lets
you annotate stuff as you figure it out. I don't know of any
for ARM.

-- 
Grant Edwards
grante@visi.com

  reply	other threads:[~2001-08-21 13:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-21 12:23 Trenton D. Adams
2001-08-21 12:33 ` Grant Edwards
2001-08-21 13:02   ` Jonathan Larmour
2001-08-21 13:07     ` Trenton D. Adams
2001-08-21 13:08       ` Jonathan Larmour
2001-08-21 13:20         ` Trenton D. Adams
2001-08-21 13:22     ` Grant Edwards
2001-08-21 13:27       ` Trenton D. Adams
2001-08-21 13:32         ` Grant Edwards
2001-08-21 14:02           ` Trenton D. Adams
2001-08-21 13:05   ` Trenton D. Adams
2001-08-21 13:28     ` Grant Edwards [this message]
2001-08-27  8:02 Andre Asselin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010821152957.A1338@visi.com \
    --to=grante@visi.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=tadams@extremeeng.com \
    --cc=tadams@theone.dnsalias.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).