I compile my program and get the following errors ========================================= linking... *** ERROR L107: ADDRESS SPACE OVERFLOW SPACE: CODE SEGMENT: ?PR?SETTHERMODEDETECTIONENABLED?TCU LENGTH: 000009H *** ERROR L138: CODE GENERATION: PROBLEM WHEN PROCESSING INSTRUCTIONS CAUSE: JUMP TARGET OUT OF RANGE ADDRESS: 0C701H Program Size: data=233.7 xdata=3788 const=2422 code=56249 Target not created =========================================
I used the following tools:
Device: C8051F020
IDE-Version: µVision3 V3.31 Copyright (c) Keil Elektronik GmbH / Keil Software, Inc. 1995 - 2006
Tool Version Numbers: Toolchain Path: C:\Keil\C51\BIN\ C Compiler: C51.Exe V8.04 Assembler: A51.Exe V8.00 Linker/Locator: LX51.Exe V4.06 Librarian: LIBX51.Exe V4.24 Hex Converter: OHX51.Exe V1.36 CPU DLL: S8051.DLL V3.04 Dialog DLL: DCYG.DLL V2.45 Target DLL: BIN\CygC8051F.dll V1.33 Dialog DLL: TCYG.DLL V2.45
How can I resolve these errors?
"I compile my program and get the following errors"
Note that they are Linker Errors; it is the Linker's job to join all your separate object files together, and fit them into your target's memory space.
http://www.keil.com/product/devproc.asp?t=c51&h=1
*** ERROR L107: ADDRESS SPACE OVERFLOW SPACE: CODE SEGMENT: ?PR?SETTHERMODEDETECTIONENABLED?TCU LENGTH: 000009H
The message means exactly what it says - do you understand what the word overflow means?
">http://www.keil.com/support/man/docs/bl51/bl51_l107.htm
"How can I resolve these errors?"
Ensure that your software does not overflow the CODE space!
See the linked articles on the above-mentioned Manual page.
hi that address space overflow is due to lack of data memory. i mean if u r allocating the data memory more than whatever available it gives the error addres space overflow,u comment few varaible declarations. another one i dont know
"that address space overflow is due to lack of data memory."
No, it is not!
Read the message again, carefully:
Now, what address space has overflowed...?
then it maight be code memory overflow. decrease the code size and chek/
"it maight be code memory"
There is no "might" about it - the message very clearly and explicitly says that it is CODE memory that has overflowed!
"SPACE: CODE"