Searching \ for 'Best way to dissassemble a hex file' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/index.htm?key=best+way+dissassemble
Search entire site for: 'Best way to dissassemble a hex file'.

Truncated match.
PICList Thread
'Best way to dissassemble a hex file'
2005\08\13@190800 by John Nall

picon face
The subject says it all.  I have a hex file and need to disassemble it.  
What is the best way to do that?

John

2005\08\13@191208 by Marcel Birthelmer

flavicon
face
John Nall wrote:
> The subject says it all.  I have a hex file and need to disassemble it.  
> What is the best way to do that?
>
> John
>

gpdasm in the gputils package (for linux) does this quite well.

2005\08\13@191240 by John J. McDonough

flavicon
face
Import it into MPLAB and open a program memory window.

--McD

----- Original Message -----
From: "John Nall" <spam_OUTjwnallTakeThisOuTspamgmail.com>
To: <.....piclistKILLspamspam@spam@mit.edu>
Sent: Saturday, August 13, 2005 7:07 PM
Subject: Best way to dissassemble a hex file


> The subject says it all.  I have a hex file and need to disassemble it.  
> What is the best way to do that?
>
> John
>
> --

2005\08\14@150047 by John Nall

picon face
Marcel Birthelmer wrote:

> > gpdasm in the gputils package (for linux) does this quite well.

Well, actually it did NOT do it quite well!  It complained about the
checksum and didn't do any disassembly.  Importing the hex file into
MPLAB did work, which presumably implies that the hex file is OK.  I'm
kind of curious about why gpdasm didn't work -- may well have been
cockpit error.  I called it with "gpdasm -p 18f452 file.hex" and it just
said "Checksum error" and quit.  I then called it with "gpdasm -p 18f452
-i file.hex" and it said "hex file format:  inhx16" and "number of
bytes: 8".  That number of bytes thing is kind of worrisome, because
file.hex has 566 bytes.

So any suggestions on what I am doing wrong?  (Although MPLAB solves the
problem, I'd like to be able to use gpdasm)

John

2005\08\14@155433 by Marcel Birthelmer

flavicon
face
John Nall wrote:
> Marcel Birthelmer wrote:
>
>> > gpdasm in the gputils package (for linux) does this quite well.
>
>
> Well, actually it did NOT do it quite well!  It complained about the
> checksum and didn't do any disassembly.  Importing the hex file into
> MPLAB did work, which presumably implies that the hex file is OK.  I'm
> kind of curious about why gpdasm didn't work -- may well have been
> cockpit error.  I called it with "gpdasm -p 18f452 file.hex" and it just
> said "Checksum error" and quit.  I then called it with "gpdasm -p 18f452
> -i file.hex" and it said "hex file format:  inhx16" and "number of
> bytes: 8".  That number of bytes thing is kind of worrisome, because
> file.hex has 566 bytes.
>
> So any suggestions on what I am doing wrong?  (Although MPLAB solves the
> problem, I'd like to be able to use gpdasm)
>
> John

Hmm, looknig at the source, I'd guess that the problem might be related
to a bad kind of line break. Are you passing this file between windows
and unix? Try running unix2dos on it. But that's just a guess.
- Marcel

2005\08\14@163119 by John Nall

picon face
Marcel Birthelmer wrote:

> > Hmm, looknig at the source, I'd guess that the problem might be
> related to a bad kind of line break. Are you passing this file between
> windows and unix? Try running unix2dos on it. But that's just a guess.

Yeah, that was my first guess also, since I did indeed pass the file
from Windows to Linux.  I ran dos2unix (which is what I think you meant
to say) on the file.  It is the same either way.  I'll play around with
it some  That thing about gpdasm saying "8 bytes" seems to indicate that
it only read the first line.  I have some of Wouter's old hex files on
the system (they came with the Wisp628 stuff) so will see if it does the
same thing with one of those files.

John

More... (looser matching)
- Last day of these posts
- In 2005 , 2006 only
- Today
- New search...