• State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 21 subscribers
  • Views 906 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

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

Difference in hex files with m8051 / DW8051

rupal parikh

I have compiled C code using target as DW8051(synopsys) and have a hex format output file for it. I used the same C code and changed target to m8051 (mentor graphics) and have a hex format output file. I noticed that these files were identical. Is this to be expected ?

Parents
  • 0

    I wouldn't be surprised, especially if you didn't change the source code. Most of the 8051 variants are very similar.

    Even if the m8051 has different standard SFR addresses than the DW8051, you'd still have to change your code to account for those differences.

    The "target" is uVision is really just some pre-defined configuration for which peripherals are available, CPU clock rate, size of various memories, and so on. It doesn't really affect code generation or linking.

Reply
  • 0

    I wouldn't be surprised, especially if you didn't change the source code. Most of the 8051 variants are very similar.

    Even if the m8051 has different standard SFR addresses than the DW8051, you'd still have to change your code to account for those differences.

    The "target" is uVision is really just some pre-defined configuration for which peripherals are available, CPU clock rate, size of various memories, and so on. It doesn't really affect code generation or linking.

Children
No data