From: SourceForge.net <no...@so...> - 2008-01-11 07:57:26
|
Bugs item #1869080, was opened at 2008-01-10 23:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=520074&aid=1869080&group_id=68108 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: External Memory: options mfile / avr-lib doc Initial Comment: When using external memory (e.g. at ATmega128) the old option EXTMEMOPTS = -Wl,-Tdata=0x801100,--defsym=__heap_end=0x80ffff does not seem to work anymore. By this the heap and data+bss section went into the external memory before. Instead a EXTMEMOPTS = -Wl,--section-start,.data=0x801100,--defsym=__heap_end=0x80ffff must be used. So the explanation in the default mfile must be: # 64 KB of external RAM, starting after internal RAM (ATmega128!), # used for variables (.data/.bss) and heap (malloc()). #EXTMEMOPTS = -Wl,--section-start,.data=0x801100,--defsym=__heap_end=0x80ffff # 64 KB of external RAM, starting after internal RAM (ATmega128!), # only used for heap (malloc()). EXTMEMOPTS = -Wl,--defsym=__heap_start=0x801100,--defsym=__heap_end=0x80ffff (In WinAVR20071221 the comments in the mfile is not up-to-date for the first case, the second comment is the new one for the first.) If you choose the option in the mfile menu the result is correct. The avr-lib documenation is also using EXTMEMOPTS = -Wl,-Tdata=0x801100,--defsym=__heap_end=0x80ffff Both should be easy to fix. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=520074&aid=1869080&group_id=68108 |