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 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
The # symbol appeared previously with the error report without it being part of the linker control file. Well I will truncate it somewhat and see what happens. I didnt realise you cannot start a new thread about an ongoing problem. Any way thanks for that.
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 (#
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
"I didnt realise you cannot start a new thread about an ongoing problem." The whole idea behind a thread is that you can see the entire discussion in one place. If I want to see what you've said before and what advice you have been given I can just scroll up and down rather than having to go and locate the other threads that contain bits of the discussion. It just makes sense...
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
Sorry but I havent been on a discussion forum before so I am not sure how they work what you call the MAP? Is that the linker file renamed?
I didnt realise you cannot start a new thread about an ongoing problem. There's no rule that says you can't. But, it does make it a lot harder for anyone to get a complete picture of what's exactly going on. Jon