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

Keil3 vs Keil compiler,Linker differnces

Hello All,

I have compiled legacy code in Keil 3 and generated lst,map,hex files.When the same legacy code is compiled in Keil5 I am able to see difference in code size const size etc in lst ,map,hex files while using LX51 Linker.

Could you please let us know what causes this differences in hex ,map, lst files apart from the compiler/Linker change?

Regards,
Neil

Parents
  • So it's likely that the linker is locating segments in a different order. A detailed comparison of the MAP file would probably tell you what.

    If you really had the need/incentive/understanding, you might be able to come up with a link specification that orders the segments in the original order.

    But if you get the same order with BL51, then I can't understand your concern. Simply stick with BL51.

Reply
  • So it's likely that the linker is locating segments in a different order. A detailed comparison of the MAP file would probably tell you what.

    If you really had the need/incentive/understanding, you might be able to come up with a link specification that orders the segments in the original order.

    But if you get the same order with BL51, then I can't understand your concern. Simply stick with BL51.

Children