Strange BL51 behaviour under uVision

Hi,

I've a project for which I have many linker directives contained in a command file. Invoking the linker from within uVision with the command file specifile via the '@ filename' option, always throws up a linker error. Yet, if I run BL51 from a dos prompt (c:\c51\bin\bl51 @ link.cfg) it works. Is there a subtle difference between how BL51 is invoked when under uVision?

Thanks!

Parents
  • Precisely what error do you get?
    It's hard to debug an error if we don't know what it is! ;-)

    Why are you passing a command file if you're using uVision?
    The idea is that you just check the options in the uVision dialogues.

    I guess this might be the root of your problem: uVision creates a command file from the dialogue options, and you're trying to give it another one!
    Check the documentation to see how/if this is supposed to be supported (I dunno off hand).

Reply
  • Precisely what error do you get?
    It's hard to debug an error if we don't know what it is! ;-)

    Why are you passing a command file if you're using uVision?
    The idea is that you just check the options in the uVision dialogues.

    I guess this might be the root of your problem: uVision creates a command file from the dialogue options, and you're trying to give it another one!
    Check the documentation to see how/if this is supposed to be supported (I dunno off hand).

Children
More questions in this forum