• State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 22 subscribers
  • Views 1852 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Hex File for AT89C51RD2

Atta Ul Mustafa

Hi!
Last time the title was mistakenly written as "and".
My query is:
I have read the code from AT89C51RD2 and dumped it into a file. This code worked well when burnt in other AT89C51RD2 controllers. Later i got its source code.
Now i am generating the hex file. This hex file is different from one i copied from the controller. The generated file is in Intel Hex Format (i.e. starts with 0x3A) whereas the coped hex file starts with 0x02. What is the difference between two hex files?

Parents
  • 0 in reply to Andy Neil

    Thanks for the reply but i still have some confusions.
    When i view the file "with 0x02 at start" in UltraEdit, it clearly shows the character strings used in the source code. The same strings can be seen on two row LCD when controller is inserted into the circuit. However when i view the hex file generated by uV3, i cann't see the same character strings.
    If an Intel Hex file is a pure ASCII printable text file, then why i cann't see the character strings?

Reply
  • 0 in reply to Andy Neil

    Thanks for the reply but i still have some confusions.
    When i view the file "with 0x02 at start" in UltraEdit, it clearly shows the character strings used in the source code. The same strings can be seen on two row LCD when controller is inserted into the circuit. However when i view the hex file generated by uV3, i cann't see the same character strings.
    If an Intel Hex file is a pure ASCII printable text file, then why i cann't see the character strings?

Children
No data