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

MDK 4.12 linker issue

Hello,

I have had a few exchanges with Alexander of Keil support concerning a problem with the new linker - it seems to somehow misjudge the load region size required for an application (LPC2478 target), which is problematic for programs that have a tight ROM budget and are on the edge of it (yes, I'm on the edge...). The problem is that linking fails. It does not seem to have any impact on smaller targets nor on the correctness of the code. It can be bypassed by increasing the size of the load/execution regions to allow linking to succeed, but for obvious reason that it inadvisable.

Parents
  • Stuart,

    Thank for your reply. Alexander told me that the compiler/linker teams are working on a patch to address some of the issues. The fact that subsequent builds are smaller is normal and due to optimization (the first build generates the linker feedback file). I have also noticed that if the size of my binary "creeps" upwards to 4[KB] (bootloader size limit), it fits even with MDK 4.11. But if the project is then cleaned - the very same come will never link again...! As I said, they're working on it. I am forced to use 4.11 until these issues are addressed.

Reply
  • Stuart,

    Thank for your reply. Alexander told me that the compiler/linker teams are working on a patch to address some of the issues. The fact that subsequent builds are smaller is normal and due to optimization (the first build generates the linker feedback file). I have also noticed that if the size of my binary "creeps" upwards to 4[KB] (bootloader size limit), it fits even with MDK 4.11. But if the project is then cleaned - the very same come will never link again...! As I said, they're working on it. I am forced to use 4.11 until these issues are addressed.

Children