 | Discussion Forum |  |
|
|
How to read in an Intel Hex file into the dscopeNext Thread | Thread List | Previous Thread Start a Thread | Settings | Details | Message |
|---|
Read-Only Author mike finnerty Posted 13-Dec-2001 00:32 GMT Toolset C51 |  How to read in an Intel Hex file into the dscope mike finnerty I am using dScope251/51 for windows Version 1.2c and cannot seem to load in an Intel hex file by itself, without first compiling or assembling it with uVision.Does anyone know how to do this, please let me know Thanks Mike Finnerty | | Read-Only Author Jon Ward Posted 19-Dec-2001 15:45 GMT Toolset C51 |  RE: How to read in an Intel Hex file into the dscope Jon Ward ...cannot seem to load in an Intel hex file by itself, without first compiling or assembling it with uVision...
I'm curious to know how you compile or assemble an Intel HEX file.
In the debugger, to load a HEX file you simply type:
load file.hex
Refer to the following knowledgebase article:
http://www.keil.com/support/docs/1936.htm
Jon | | Read-Only Author mike finnerty Posted 19-Dec-2001 16:24 GMT Toolset C51 |  RE: How to read in an Intel Hex file into the dscope mike finnerty Thanks for the responses, I figured out that the problem was the first line in my hex file it should read as follows.
:03000000020003F8 /* correct first line */
The following line was the source of my problems
:020000040000FA /* incorrect first line */
I always though hex was hex, but I must be wrong. Oddly enough the original hex file worked with my device programmer. | | Read-Only Author Jon Ward Posted 19-Dec-2001 17:25 GMT Toolset C51 |  RE: How to read in an Intel Hex file into the dscope Jon Ward
:020000040000FA
That is an Intel HEX-386 extended address record. That's why it won't work. Take a look at:
http://www.keil.com/support/docs/1584.htm
Jon | |
Next Thread | Thread List | Previous Thread Start a Thread | Settings |
|