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

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
  • Jon

    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
    
    

    I truncated the code and funnily enough it linked all the non existent files which are now not included and came up with the same error.So I am not sure where the enviroment is pointing but not the one I have changed has this ever happened to you or have you heard of such a thing?
    I am baffled as this project was all working 3 yrs ago.

Reply
  • Jon

    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
    
    

    I truncated the code and funnily enough it linked all the non existent files which are now not included and came up with the same error.So I am not sure where the enviroment is pointing but not the one I have changed has this ever happened to you or have you heard of such a thing?
    I am baffled as this project was all working 3 yrs ago.

Children
  • That is not the error.

    Can you post the error message as it appears at the bottom of the MAP file?

    Also, can you post the command line as it appears in the MAP file?

    Jon

  • Is the map file the file with extesion M51?

  • Jon
    Here is the map file

    BL51 BANKED LINKER/LOCATER V4.02              09/29/2003  16:27:05  PAGE 1
    
    
    BL51 BANKED LINKER/LOCATER V4.02, INVOKED BY:
    C:\KEIL\C51\BIN\BL51.EXE  C:\V10001E\C\CLOCK
    >> .OBJ, C:\V10001E\C\CLOCKDAT.OBJ, C:\V10001E\C\CODES.OBJ, C:\V10001E\C\COM_T
    >> EST.OBJ, C:\V10001E\C\COMMS.OBJ, C:\V10001E\C\CONFIG.OBJ, C:\V10001E\C\CONT
    >> ROL.OBJ, C:\V10001E\C\CRC.OBJ, C:\V10001E\C\DATATRAN.OBJ, C:\V10001E\C\DISP
    >> LAY.OBJ, C:\V10001E\C\E2_DATA.OBJ, C:\V10001E\C\ENG_COD.OBJ, C:\V10001E\C\H
    >> OLS.OBJ, C:\V10001E\C\IND_INIT.OBJ, C:\V10001E\C\INITMOD.OBJ, C:\V10001E\C\ 
    >> INPUTS.OBJ, C:\V10001E\C\INT10MS.OBJ, C:\V10001E\C\INTERCOM.OBJ, C:\V10001E
    >> \C\KEYBD.OBJ, C:\V10001E\C\KEYIN.OBJ, C:\V10001E\C\LCD_DAT.OBJ, C:\V10001E\ 
    >> C\LCD_MOD.OBJ, C:\V10001E\C\MAN_COD.OBJ, C:\V10001E\C\MODE_MOD.OBJ, C:\V100
    >> 01E\C\OUTPUTS.OBJ, C:\V10001E\C\OVERIDE.OBJ, C:\V10001E\C\PRINT_C.OBJ, C:\V
    >> 10001E\C\PRINT_M.OBJ, C:\V10001E\C\PRINT_R.OBJ, C:\V10001E\C\PRINT_S.OBJ, C
    >> :\V10001E\C\PRINTER.OBJ, C:\V10001E\C\R_INPUT.OBJ, C:\V10001E\C\R_OUTPUT.OB
    >> J, C:\V10001E\C\R_SENSOR.OBJ, C:\V10001E\C\R_ZONE.OBJ, C:\V10001E\C\RAMDATA
    >> .OBJ, C:\V10001E\C\RECORDS.OBJ, C:\V10001E\C\S_CODES.OBJ, C:\V10001E\C\S_LU
    >> X.OBJ, C:\V10001E\C\S_OUTPUT.OBJ, C:\V10001E\C\S_SENSOR.OBJ, C:\V10001E\C\S
    >> _W_SNSR.OBJ, C:\V10001E\C\S_ZONE.OBJ, C:\V10001E\C\SENSORS.OBJ, C:\V10001E\ 
    >> C\SETTIME.OBJ, C:\V10001E\C\SETUP.OBJ, C:\V10001E\C\SITE_COD.OBJ, C:\V10001
    >> E\C\START.OBJ, C:\V10001E\C\STRINGS.OBJ, C:\V10001E\C\TEST.OBJ, C:\V10001E\ 
    >> C\UTILS.OBJ, C:\V10001E\C\ZONE.OBJ, C:\V10001E\C\TIME.OBJ TO C:\V10001E\V10
    >> 001 RS (128) PL (68) PW (78)
    
    
    *** FATAL ERROR L210: I/O ERROR ON INPUT FILE:
        EXCEPTION 0021H: PATH OR FILE NOT FOUND
        FILE: C:\V10001E\.OBJ
    
    

  • Jon
    thanks for all your help sorry for my level of ignorance on the Keil.I have just realised I have done a mess of a lot of things as I have renamed one project file yet I think all the associated are linking the ols project.
    I have never actually have had set up a compiler where I worked with the motorola all of that was done by senior engineers. I just wrote C all day sorry If I have p$$$ed you off never meant to.

  • I have in this project
    link.ctl
    but no .lin file
    what is the difference between these 2?
    I posted what I thought was the linker file but now I think I may have been wrong all along.
    Here are the files and folders as listed in widows explorer with their extensions
    from the original file I have been working from.

    Top folder is V10001e
    inside this I have
    C folder
    h folder
    d ms-dos batch file
    link.bak
    link.ctl
    o.bat
    v10001.ABS
    v10001.LER
    V10001.prj
    V10001e.abs
    V10001e.hex
    v10001e.M51

    why some file end with e and why some don't I am not sure.
    Is there a linker file here??

  • It looks like your linker command file is corrupt.

    You mentioned before something about funny characters - that would certainly mess things up!

  • You are clearly very confused. I suggest you create a new project directory, then work through the "Getting Started" manual and create an entirely new project from scratch. This should give you a better understanding of what is going on.

    Stefan

  • Did both of these listings come from the same map file?

    Jon

  • This doesn't match your previous error of:

    Linking
    *** FATAL ERROR 204: INVALID KEYWORD

    It looks you are just guessing at what the problem could be and randomly changing things to see if they fix it. This technique has a very low likelihood working.

    Jon

  • As Stefan says, you seem to be very confused by all this; and it doesn't sound like you have anyone else to hand who really knows the
    tools to assist you?

    If you're in Southern England, maybe we could help you out with a day's
    on-site Consultancy - look at this problem and give you a general
    walk-though on the Tools?

    If you're interested, mail

    Sales
    at
    Antronics
    dot
    co
    dot
    uk
    (I trust you can decipher the anti-spam tactics there)

    Good Luck!

    Andy Neil,
    Technical Director, Antronics Ltd.

    PS
    Yes, I did OK this with the forum moderator.

    PPS
    In the Midlands, maybe you could try the guys at Hitex: http://www.hitex.co.uk.

  • I finally solved the problem as I reverted back to the original version of software but using a dongle of another version as the original dongle along with the original software cannot be found at the moment.

    So all the problems disappeared once I got the version back using the original installed directory copied over the C51 and Keil directories so I have a working enviroment of sorts.
    As you said I have little experience with the Keil tools and as you guessed I am working completely on my own with no one to assist me but at the moment I don't see any likelyhood of the company paying for seminars.
    So anyway I will persevere for the moment. Still in the case Im in up to my eyeballs with problems I will have to seek external consultancy.

  • "I don't see any likelyhood of the company paying for seminars."

    Your 1st post on this subject was 24 Sep; you apparently got someting working on 7 Oct.

    For the benefit of the bean-counters, you might like to tot-up the cost of those 10 lost working days (I assume you didn't work weekends?) against a day's training/consultancy.

    Not forgetting, of course, to use your company's full overhead rate - probably at least 2x your hourly rate... :-0