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.
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!
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...