Problem with Keil compiler -

Keil 8051 Tools

Problem with Keil compiler

profile | register | preferences | faq | search

UBBFriend: Email This Page to Someone!

next newest topic | next oldest topic

Author	Topic: Problem with Keil compiler
mamouth New Member	posted June 14, 2007 09:02 AM Hi.I have tried to modify and compile the zigbee Example "NWK_Blinky" for the F121. After applying all changes the project compiles fine with 0 errors and 0 warning (Evaluation versions of the Keil compiler, assembler and linker) I've also try it with another version of Keil(C51V808.a.exe) But the linker refused...and I still have the same problem which is: * ERROR L107: ADDRESS SPACE OVERFLOW SPACE: DATA SEGMENT: ?DT?NWK_BLINKY LENGTH: 003AH followed by 9 oders problem such as : * ERROR L105: PUBLIC REFERS TO IGNORED SEGMENT SYMBOL: PRESSEDFLAGSW6 SEGMENT: ?DT?NWK_BLINKY did someone has alredy got such problem??If so how have you used to fix it??thanks ------------------ michel ronald ------------------ michel ronald IP: Logged
erikm Member	posted June 14, 2007 09:30 AM No, NOBODY has such a problem. If this was a 'problem' then a misspelled 'fox' instead of 'for' would be a 'problem' HOWEVER, many see these error messages. 1) if you have any "UNCALLED SEGMENT .." comment those out in your source. 2) is this 'native' blinbky or a lot of stuff added (I guess you took blinky and used it as a base) 3) you need to list ALL error meaasges you get not "followed by such as) often the key to the first is in the nth Erik [This message has been edited by erikm (edited June 14, 2007).] IP: Logged
mamouth New Member	posted June 14, 2007 09:57 AM Hi Erik I used the network_blinky sample as main project.I just want to change and add others function!!I've put in comment all the uncalled function !!Maybe the problem is comming from the keil configuration??I try another version but still have problem.. those are all error messages I recieve: * ERROR L107: ADDRESS SPACE OVERFLOW SPACE: DATA SEGMENT: ?DT?NWK_BLINKY LENGTH: 003AH * ERROR L105: PUBLIC REFERS TO IGNORED SEGMENT SYMBOL: PRESSEDFLAGSW6 SEGMENT: ?DT?NWK_BLINKY * ERROR L105: PUBLIC REFERS TO IGNORED SEGMENT SYMBOL: PRESSEDFLAGSW5 SEGMENT: ?DT?NWK_BLINKY * ERROR L105: PUBLIC REFERS TO IGNORED SEGMENT SYMBOL: PRESSEDFLAGSW4 SEGMENT: ?DT?NWK_BLINKY * ERROR L105: PUBLIC REFERS TO IGNORED SEGMENT SYMBOL: PRESSEDFLAGSW3 SEGMENT: ?DT?NWK_BLINKY * ERROR L105: PUBLIC REFERS TO IGNORED SEGMENT SYMBOL: DATA_RX SEGMENT: ?DT?NWK_BLINKY * ERROR L105: PUBLIC REFERS TO IGNORED SEGMENT SYMBOL: KEYPRESSSW6 SEGMENT: ?DT?NWK_BLINKY * ERROR L105: PUBLIC REFERS TO IGNORED SEGMENT SYMBOL: KEYPRESSSW5 SEGMENT: ?DT?NWK_BLINKY * ERROR L105: PUBLIC REFERS TO IGNORED SEGMENT SYMBOL: KEYPRESSSW4 SEGMENT: ?DT?NWK_BLINKY * ERROR L105: PUBLIC REFERS TO IGNORED SEGMENT SYMBOL: KEYPRESSSW3 SEGMENT: ?DT?NWK_BLINKY If you have any idea on the way to change the config of Keil C51 that'll be helpfull thanks ------------------ michel ronald IP: Logged
Tsuneo Member	posted June 14, 2007 10:14 AM Do you mean the SiLabs eval version (Keil v7.05) compiles it in no error, but the recent full version doesn't? And the error code is L107: ADDRESS SPACE OVERFLOW, in DATA segment? I remember this case. >"HID Example Blinky: ERROR L107: ADDRESS SPACE OVERFLOW" In this case, 'const' was the culprit. Keil suddenly changed 'const' definition in the version 8. So, 'code' is required to specify it as a constant on code FLASH. const from Keil Is it also your case? Tsuneo IP: Logged
mamouth New Member	posted June 15, 2007 03:06 AM Thanks guy, but in my program 'code' have been usde instead of 'const'; for example I have those definition: void bytehexcat(unsigned char xdata str, unsigned char bydata); void intcat( BYTE xdata str, WORD nt); void bytecat(BYTE xdata str, BYTE nt); void Cstrcpy(BYTE xdata lpDest, BYTE code * lpSrc); void Xstrcpy(BYTE xdata * lpDest, BYTE xdata * lpSrc); void Cstrcat(BYTE xdata * lpDest, BYTE code * lpSrc); void Xstrcat(BYTE xdata * lpDest, BYTE xdata * lpSrc); INT Xstrlen(BYTE xdata * lpStr); INT Cstrlen(BYTE code * lpStr); .I think the problom is not due to that transformation IP: Logged
Tsuneo Member	posted June 15, 2007 04:00 AM a) Compare compiler and linker switches between the eval and full version. Compiler switches are seen as the command line on the listing (.LST) file. Linker switches are also listed up on the the command line of map (.M51) file. "Listing (LST) File" from KEIL http://www.keil.com/support/man/docs/c51/c51_cm_listfile.htm "Listing (MAP) File" http://www.keil.com/support/man/docs/bl51/bl51_ln_mapfile.htm b) Compare memory MAP between the eval and full version. Find which segment is added, or bloated up. This KEIL article shows you the way to decipher the MAP file. "BL51: ERROR 107 (ADDRESS SPACE OVERFLOW)" from KEIL http://www.keil.com/support/docs/1241.htm Tsuneo [This message has been edited by Tsuneo (edited June 15, 2007).] IP: Logged

All times are CT (US)	next newest topic \| next oldest topic
Administrative Options: Close Topic \| Archive/Move \| Delete Topic
	Hop to:

Contact Us | MCU User Forum

Have you seen our MCU Knowledge Base?

Ultimate Bulletin Board 5.47b