• AVR Freaks

[FAQ]MPLINK error: section '<sectionname>' can not fit the absolute section

Page: < 123 Showing page 3 of 3
Author
ric
Super Member
  • Total Posts : 28004
  • Reward points : 0
  • Joined: 2003/11/07 12:41:26
  • Location: Australia, Melbourne
  • Status: online
Re:MPLINK error: section '<sectionname>' can not fit the absolute section 2015/01/25 21:51:36 (permalink)
0
marec, you're about 2.5 years too late to this topic.
What is your point about the 16F84A LKR file?
SHAREBANK is the correct directive there, as the registers at 0x0C to 0x4F also appear at addresses 0x8C to 0xCF.
 
What problem were you having that making this change fixed?
 

I also post at: PicForum
Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
NEW USERS: Posting images, links and code - workaround for restrictions.
To get a useful answer, always state which PIC you are using!
#41
1and0
Access is Denied
  • Total Posts : 10999
  • Reward points : 0
  • Joined: 2007/05/06 12:03:20
  • Location: Harry's Gray Matter
  • Status: offline
Re:MPLINK error: section '<sectionname>' can not fit the absolute section 2015/01/25 22:46:03 (permalink)
0
ric
marec, you're about 2.5 years too late to this topic.
What is your point about the 16F84A LKR file?
SHAREBANK is the correct directive there, as the registers at 0x0C to 0x4F also appear at addresses 0x8C to 0xCF.
What problem were you having that making this change fixed?

My crystal ball tells me 'marec' is using UDATA instead of UDATA_SHR to reserve his variables.  Besides, his change to
DATABANK   NAME=gpr0       START=0x0C              END=0x4F           
DATABANK   NAME=gpr0       START=0x8C              END=0xCF           PROTECTED

would generate a duplicate definition error of 'gpr0'.
#42
marec
Starting Member
  • Total Posts : 51
  • Reward points : 0
  • Joined: 2015/01/25 20:03:55
  • Location: Brazil
  • Status: offline
Re:MPLINK error: section '<sectionname>' can not fit the absolute section 2015/01/26 09:43:58 (permalink)
0
Ok, thanks super members for corrections.
It is valid the advice: Check if you´re using correct section of device (udata x udata_shr, for instance).
#43
Page: < 123 Showing page 3 of 3
Jump to:
© 2020 APG vNext Commercial Version 4.5