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!
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).
I am explicitly locating a number of functions via the 'CO' directive. The IDE seems only to permit a small amount (too few) of characters to be entered. -That's why I'm using a command file! Tried a number of things today, but no joy. I'll stick with the 'manual' linking for now.
What version are you using? In v6.1x, on the 'BL51 Misc' tab, there is a 'use linker control file' checkbox, and buttons to Create, Browse & Edit. Alternatively, how about adding your "manual" link in one of the 'Run User Program #' boxes on the 'Output' tab?
Can't say for sure what version I'm using (not at work right now!), and I've seen the add control file option, but when I click on browse to specify the file, nothing happens. The only way I can get it to run using the control file is by manually adding it to the relevant section in the *.prj file. (That's when I get the error.) I'd like to be able to run my linker batch file from the IDE, as you suggest using the 'after make' run user file thing, but this doesn't seem to run if you've got the BL51 linker deselected in the Make options. Maybe I should get the latest version...