Searching \ for '[PIC:] Tools for editing/validating Intel 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/microchip/devices.htm?key=pic
Search entire site for: 'Tools for editing/validating Intel Hex file'.

Exact match. Not showing close matches.
PICList Thread
'[PIC:] Tools for editing/validating Intel Hex file'
2003\12\16@191036 by Ed Sutton

flavicon
face
part 0 44 bytes
his is a multi-part message in MIME format.
part 1 541 bytes content-type:text/plain; charset=us-ascii; format=flowed (decoded 7bit)

I just manually edited an Intel hex file with my programming editor. I
could have easily made a mistake.

Does anyone know of any tools for editing or validating Intel Hex files?

Requested Features
------------------
1 - Validates record checksums and updates checksums when a record is
edited.
2 - Allow editing data in ASCII string format.

Thanks in advance,

-Ed

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email spam_OUTlistservTakeThisOuTspammitvma.mit.edu with SET PICList DIGEST in the body




part 2 297 bytes content-type:text/x-vcard; charset=utf8;
(decoded 7bit)

begin:vcard
fn:Ed Sutton
n:Sutton;Ed
org:Nomadics, Inc.
adr:;;1024 S. Innovation Way;Stillwater;OK;74074;USA
email;internet:.....esuttonKILLspamspam@spam@nomadics.com
tel;work:405-372-9535
tel;fax:405-372-9537
x-mozilla-html:FALSE
url:http://www.nomadics.com/
version:2.1
end:vcard


2003\12\16@193943 by Jim Korman

flavicon
face
Ed Sutton wrote:

> I just manually edited an Intel hex file with my programming editor. I
> could have easily made a mistake.
>
> Does anyone know of any tools for editing or validating Intel Hex files?
>
> Requested Features
> ------------------
> 1 - Validates record checksums and updates checksums when a record is
> edited.
> 2 - Allow editing data in ASCII string format.
>
> Thanks in advance,
>
> -Ed
>
> --
> http://www.piclist.com#nomail Going offline? Don't AutoReply us!
> email listservspamKILLspammitvma.mit.edu with SET PICList DIGEST in the body

You could try HexWorkshop

http://www.hexworkshop.com/

It has a 30 day trial. ($49.94US )

Jim

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email .....listservKILLspamspam.....mitvma.mit.edu with SET PICList DIGEST in the body

2003\12\16@201925 by Tony Nixon

flavicon
picon face
Most programmers allow HEX file editing and saving.

I would imagine that they also validate HEX files after loading.

regards

Tony

Ed Sutton wrote:

{Quote hidden}

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listservspamspam_OUTmitvma.mit.edu with SET PICList DIGEST in the body

2003\12\17@072332 by Olin Lathrop

face picon face
Ed Sutton wrote:
> I just manually edited an Intel hex file with my programming editor. I
> could have easily made a mistake.
>
> Does anyone know of any tools for editing or validating Intel Hex
> files?

I don't know about editing, but MPASM can generate an Intel HEX file
containing numbers in various formats, strings, etc.

The few times I've had to modify an Intel HEX file, I wrote a program to do
it.  I've got generic Intel HEX file I/O routines, so the app part of the
program is easy.  This has usually been to automatically add things like
serial numbers and date/time stamps.  Why to you want to edit a HEX file?


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com hint: To leave the PICList
@spam@piclist-unsubscribe-requestKILLspamspammitvma.mit.edu

2003\12\17@094357 by Ed Sutton

flavicon
face
part 0 44 bytes
his is a multi-part message in MIME format.
part 1 954 bytes content-type:text/plain; charset=us-ascii; format=flowed (decoded 7bit)

Olin Lathrop wrote:
> I don't know about editing, but MPASM can generate an Intel HEX file
> containing numbers in various formats, strings, etc.

Good idea.

> The few times I've had to modify an Intel HEX file, I wrote a program to do
> it.  I've got generic Intel HEX file I/O routines, so the app part of the
> program is easy.  This has usually been to automatically add things like
> serial numbers and date/time stamps.  Why to you want to edit a HEX file?

We customize our device for different applications by manually editing
the EEPROM.hex file to change control constants and a product ID string.
  I want to automate this as well.

As you did, I eventually expect to end up writing my own utility or
editor that reads and modifies the appropriate data in the Intel hex file.

-Ed

--
http://www.piclist.com hint: To leave the PICList
KILLspampiclist-unsubscribe-requestKILLspamspammitvma.mit.edu




part 2 297 bytes content-type:text/x-vcard; charset=utf8;
(decoded 7bit)

begin:vcard
fn:Ed Sutton
n:Sutton;Ed
org:Nomadics, Inc.
adr:;;1024 S. Innovation Way;Stillwater;OK;74074;USA
email;internet:RemoveMEesuttonTakeThisOuTspamnomadics.com
tel;work:405-372-9535
tel;fax:405-372-9537
x-mozilla-html:FALSE
url:http://www.nomadics.com/
version:2.1
end:vcard


2003\12\17@094813 by Wouter van Ooijen

face picon face
> As you did, I eventually expect to end up writing my own utility or
> editor that reads and modifies the appropriate data in the
> Intel hex file.

If you are not scared of a snake: my xwips.py (PC software for the
Wisp628 programmer) contains a class for reading, manipulating and
writing .hex files. Available as source.

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: http://www.voti.nl
consultancy, development, PICmicro products

--
http://www.piclist.com hint: To leave the PICList
spamBeGonepiclist-unsubscribe-requestspamBeGonespammitvma.mit.edu

2003\12\17@145441 by Robert Rolf

picon face
Rather than rewrite an existing record, why not leave a 'hole' in the
code and then append the changeable info as a separate (or concatenated)
file?

Most programmers don't care about the address order, so you could
program the common code first, then upload the unique info separately.
Or combine the files after they are created. e.g.

DOSPROMPT>copy common.hex+serialxx.hex pgmr.hex

It's probably easier to write a short script (or batch file) to generate serialized
hex files, than to write a full blown hex file editor. The MSDOS batch
processor is quite useful for this.


Robert

Ed Sutton wrote:
{Quote hidden}

--
http://www.piclist.com hint: To leave the PICList
TakeThisOuTpiclist-unsubscribe-requestEraseMEspamspam_OUTmitvma.mit.edu

2003\12\17@165944 by Bob Barr

flavicon
face
On Wed, 17 Dec 2003 12:50:00 -0700, Robert Rolf wrote:

>Rather than rewrite an existing record, why not leave a 'hole' in the
>code and then append the changeable info as a separate (or concatenated)
>file?
>
>Most programmers don't care about the address order, so you could
>program the common code first, then upload the unique info separately.
>Or combine the files after they are created. e.g.
>
>DOSPROMPT>copy common.hex+serialxx.hex pgmr.hex
>

Be sure to remove the 'End of File' record from the end of the first
file if you do it this. Otherwise it will be in the middle of the
output file. I'd expect that most programmers would stop accepting
input right there and never get to the second part of the file.


Regards, Bob

--
http://www.piclist.com hint: To leave the PICList
RemoveMEpiclist-unsubscribe-requestspamTakeThisOuTmitvma.mit.edu

2003\12\17@210256 by Robert Rolf

picon face
Bob Barr wrote:
>
> On Wed, 17 Dec 2003 12:50:00 -0700, Robert Rolf wrote:
>
> >Rather than rewrite an existing record, why not leave a 'hole' in the
> >code and then append the changeable info as a separate (or concatenated)
> >file?
> >
> >Most programmers don't care about the address order, so you could
> >program the common code first, then upload the unique info separately.
> >Or combine the files after they are created. e.g.
> >
> >DOSPROMPT>copy common.hex+serialxx.hex pgmr.hex
> >
>
> Be sure to remove the 'End of File' record from the end of the first
> file if you do it this. Otherwise it will be in the middle of the
> output file. I'd expect that most programmers would stop accepting
> input right there and never get to the second part of the file.

Good point!
The HC11 assembler I was using didn't put out an EOF record so
this wasn't a problem. I had a couple of batch files that did all
the work (back when it was all done in DOS).

R

--
http://www.piclist.com hint: To leave the PICList
piclist-unsubscribe-requestEraseMEspam.....mitvma.mit.edu

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