• State Not Answered
  • Locked Locked
  • Replies 24 replies
  • Subscribers 21 subscribers
  • Views 3555 views
  • Users 0 members are here
2025 survey

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.

Options
Related
How was your experience today?
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

Ongoing problem with linker Error 204 Posting linker file

Nick Carter

Hi to you all
thank you for all the suggestions in relation to this problem.
I am posting the linker file for you to examine.I also have talked to the programmer that had previously been working for the company and he tried also to overcome the problem but with no luck.

 clock.obj, codes.obj, com_test.obj, comms.obj, config.obj, control.obj, crc.obj, &
eng_cod.obj, hols.obj, ind_init.obj, &
initmod.obj, inputs.obj, int10ms.obj, intercom.obj, keybd.obj, keyin.obj, &
lcd_mod.obj, man_cod.obj, mode_mod.obj, outputs.obj, overide.obj, &
print_c.obj, print_m.obj, print_r.obj, print_s.obj, printer.obj, &
records.obj, sensors.obj, settime.obj, setup.obj, site_cod.obj, start.obj, &
strings.obj, test.obj, utils.obj, zone.obj , startup.obj, disp_int.obj, &
ramdata.obj, e2_data.obj, s_zone.obj, s_sensor.obj, s_output.obj, &
s_input.obj, s_lux.obj, s_w_snsr.obj, s_codes.obj, r_sensor.obj, &
r_zone.obj, r_output.obj, r_input.obj, clockdat.obj, time.obj, display.obj, datatran.obj &
TO V10001e.abs &
RAMSIZE(256) CODE(0100H) XDATA(?xd?r_zone(00000H), ?xd?r_sensor(000e0H), &
?xd?r_output(00240H), ?xd?r_input(002e0H), ?xd?ramdata(00310H), ?xd?s_codes(0d007H), &
?xd?s_zone(0d037H), ?xd?s_sensor(0da1fH),?xd?s_input(0db67H), &
?xd?s_output(0dd87H), ?xd?s_w_snsr(0deffH), ?xd?s_lux(0df01H), &
?xd?clockdat(0E010H),00000H) &
SYMBOLS PUBLICS

Also all the files compiled and there where some assembly files within here.
However I edit the linker it will always come up with the same error.
Any suggestions would be welcome.
Thanks in advance
Nick

Parents
  • 0 in reply to Nick Carter

    Well, I've just managed to force an L204 error with BL51 v5.03, and it looks like this:

    *** FATAL ERROR L204: INVALID KEYWORD
    POS: 772
    51_lst\Ml_test.map) PAGEWIDTH (132) PAGELENGTH (32760) PRINTCONTROLS (#
    So the '#' is where the Linker thinks the problem lies.

    The "POS: 772" looks like the character position where the Linker thinks the error is (possibly after stripping quotes, newlines, etc?)

    Does your error message look like that?
    Can you post the full message - verbatim?

    Are you trying to put all this on the command line, or using a command file?

    If you're using just a command line, it could well be too long - so the Linker could be getting a truncated command & reporting it as an invalid keyword?

Reply
  • 0 in reply to Nick Carter

    Well, I've just managed to force an L204 error with BL51 v5.03, and it looks like this:

    *** FATAL ERROR L204: INVALID KEYWORD
    POS: 772
    51_lst\Ml_test.map) PAGEWIDTH (132) PAGELENGTH (32760) PRINTCONTROLS (#
    So the '#' is where the Linker thinks the problem lies.

    The "POS: 772" looks like the character position where the Linker thinks the error is (possibly after stripping quotes, newlines, etc?)

    Does your error message look like that?
    Can you post the full message - verbatim?

    Are you trying to put all this on the command line, or using a command file?

    If you're using just a command line, it could well be too long - so the Linker could be getting a truncated command & reporting it as an invalid keyword?

Children
  • 0 in reply to Andy Neil

    I have posted the error message exactly as it is reported also I tried to open the .LER with the textpad editor but icame with some weird characters as you see the compiler is not reporting the position of the error all I get is what I have written

  • 0 in reply to Andy Neil

    I am using a command file called link.ctl not the command except of I am mixing things up and reporting the error properly I have put verbatim error message.In the Code banking linker setup on the command line link options I have the line
    @C:\V10001E\LINK.CTL

    I think I will truncate the file and see what happens