I had the same problem. That happened because you probably have tried to do your own project with the files provided in the folder TempDemoCoord of the Version 1.0-3.6 of Microchip Stack for the ZigBee™ Protocol instead of open a New MPLAB IDE and then open the  project TempDemoCoord.mcp doing Project>Open... . Be sure that you are not using a expired demo version of MPLAB, because of the Procedural Abstraction, I think.

João Pedro Apóstolo Salgueiro

ORIGINAL: futurX

. . . Here is the message I'm getting

MPLINK 4.14, Linker
Copyright (c) 2007 Microchip Technology Inc.
Error - section '.org_1' can not fit the absolute section. Section '.org_1' start=0x00000005, length=0x00000d2e
Errors    : 1 . . .

It says, "You are trying to stuff 3.4 pounds into a 2 pound box.".

More specifically - you have a chunk of code that assembles to 3374 (i.e., 0x0D2E) instructions, but the largest available piece of memory in your microcontroller is only 2047 (0x07FF) instructions long.  Use a couple more "CODE" directives to break up your program into logical segments.  You can go farther, by explicitly assigning each segment to a particular section of codespace.  Whether you do this or not, remember that your program will be split between two or more codepages, so you will need to use "pagesel" directives (or manually manipulate PCLATH) when moving between them.

Dale

ORIGINAL: pau2756

Hi

I am very new to this and have just installed MPLAB IDE v8.10 and have worked through the first example.

I am a bit stuck as i get an error the same as what others in this thread are reporting.

 . . . .

I have 12f508.lkr as my link file and 12f508tmpo.asm as my source file.


Really hope someone can help me here.

There are several threads on the Forum where this problem, and its solution, are thoroughly discussed.

For now, change your linker file to the "12f508_g.lkr" version supplied with MPLAB 8.10 et seq.

Dale

p.s. - When posting code, please use the "code tags".

ORIGINAL: pau2756


I am sure it is something to do with the line

<%=" org 0 "%>

Yes, I see now that it does.

You are telling the linker to place two different pieces of code at the same address.  The line:

 MAIN    CODE    0x000 

directs the linker to place the following code segment (4 instructions) at address 0x0000 in codespace.

The line

   org 0 

also directs the linker to place the code that follows at the same address, 0x00.  Yes, removing the "  org 0" will solve your problem.

(I am surprised you didn't get another warning or error message, since the ORG directive shouldn't be used when assembling relocatable (i.e., linked) code.)

Dale

ORIGINAL: Olin Lathrop

Unfortunately they have now made it legal.  That means you get less clear notice that there is a ORG lurking in the code somewhere.  The section name is something derived from the fixed address, so each ORG creates a new section.

Hmmm, I see...
thanks for pointing this out.

Hi all
 
Just chiming in with a "me too".  Tried to Build All, got the error message, searched the message board, found this thread, deleted the LKR file, and all's well.  This is a most helpful forum.
 
Oh - just to add to the misery, I ran into the maximum pathname limit before I ran into the org_1 error message.  That was a little harder to figure out, because at first it just said file not found.  It also appears that some functions in the assembler/linker don't like white space or underscores.  So I had to watch the output folder to see what files weren't created, and noticed some truncated filenames.
 
Peace out
MADman

Use #pragma udata to separate your variables into multiple sections. I believe that there is an FAQ in the C18 Getting Started Guide that should help.

Is there some deep-seated, secret business reason that this particular topic remains the most visited of EVERYTHING under development tools? The hopelessly vague response

"Use #pragma udata to separate your variables into multiple sections. I believe that there is an FAQ in the C18 Getting Started Guide that should help."

really is no help. Translated from Inglish, I think this says "I don't remember the details, and I can't be bothered to look it up".

WHERE is the solution to this? Which document EXACTLY? Which page EXACTLY? Why is the typical Microchip response "it is documented somewhere, you just have to hunt for it..."? How about an ACTUAL, COMPLETE EXAMPLE of the solution?

Why isn't the linker documentation installed when you install C18? Is there some deep-seated, secret business reason for keeping it separate? Why isn't the linker file COMPLETELY explained? Is there some reason for keeping so many details secret - especially when so many people run into the EXACT same problems?

The online help with MPLab/C18 isn't just bad, it is WRONG. The explanation of of this particular error says to use the -m option to create a "linker error map". I have the /m option enabled, it creates a map file that contains essentially NO information because there is... a linker error!

After numerous projects with Microchip MCUs of various flavors, I have simply had enough. I will STRONGLY recommend that we change to something else before going to production (min 50K/year, likely 250K/year), and I will never, ever again recommend using one of your MCUs.

I have read few explaination on the error I get:
Error - section '.org_1' can not fit the absolute section. Section '.org_1' start=0x00000004, length=0x00000226

 but I am still not able to figure out why.

the lkr file I use is:
 // Sample linker command file for 16F84A
 // $Id: 16f84a.lkr,v 1.4.16.1 2005/11/30 15:15:29 curtiss Exp $
 
 LIBPATH  .
 
 CODEPAGE   NAME=vectors  START=0x0      END=0x4      PROTECTED
 CODEPAGE   NAME=page     START=0x5      END=0x3FF
 CODEPAGE   NAME=.idlocs  START=0x2000   END=0x2003   PROTECTED
 CODEPAGE   NAME=.config  START=0x2007   END=0x2007   PROTECTED
 CODEPAGE   NAME=eedata   START=0x2100   END=0x213F   PROTECTED
 
 DATABANK   NAME=sfr0     START=0x0      END=0xB      PROTECTED
 DATABANK   NAME=sfr1     START=0x80     END=0x8B     PROTECTED
 
 DATABANK   NAME=gprs     START=0xC      END=0x4F
 
 SECTION    NAME=STARTUP  ROM=vectors    // Reset and interrupt vectors
 SECTION    NAME=PROG     ROM=page       // ROM code space
 SECTION    NAME=IDLOCS   ROM=.idlocs    // ID locations
 SECTION    NAME=DEEPROM  ROM=eedata     // Data EEPROM


and the code is :

    list      p=16F84A            ; list directive to define processor
    #include <p16F84A.inc>        ; processor specific variable definitions

    __CONFIG   _CP_OFF & _WDT_OFF & _PWRTE_ON & _HS_OSC



;  VARIABLE DEFINITIONS
w_temp            equ        0X0C        ; variable used for context saving
status_temp        equ        0X0D        ; variable used for context saving

BL_INPUT        equ        0          
LF_INPUT        equ        1          
RF_INPUT        equ        2           

FLAGBLBL        equ        0          
FLAGLF            equ        1           
FLAGRF            equ        2          
FLAGHZ            equ        3      
FLAGHZB            equ        4   
FLAGTL            equ        5        

datagroup1        idata    0xc
PORTB_temp        db        0x00       
DELAY.001SEC    db        0x00       
DELAY.0001SEC    db        0x00      
delay.001sec    db        0x00      
delay.0001sec    db        0x00      
BLFLASHTIMEMSB    db        0x00      
blflashtimemsb    db        0x00       
blflashtimelsb    db        0x00       
BLFLCYCLE        db        0x00    
blflcycle        db        0x00      
BLNEVERHIGH        db        0x00       
blneverhigh        db        0x00       
BLNEVERLOW        db        0x00      
blneverlow        db        0x00      
flasheronmsb    db        0x00      
flasheronlsb    db        0x00      
HZBLON            db        0x00      
hzblon            db        0x00    
HZBLOFF            db        0x00       
hzbloff            db        0x00      
hzonmsb            db        0x00       
hzonlsb            db        0x00      
TLON            db        0x00       
tlon            db        0x00       
TLOFF            db        0x00      
tloff            db        0x00      
FLAGS            db        0x00      
;**********************************************************************
        ORG     0x000                 ; processor reset vector
        goto    Main                 ; go to beginning of program

        ORG     0x004               ; interrupt vector location
        movwf   w_temp                ; save off current W register contents
        movf    STATUS,0            ; move status register into W register
        movwf    status_temp            ; save off contents of STATUS register   
       
        ; isr code can go here or be located as a call subroutine elsewhere

        movf    status_temp,0        ; retrieve copy of STATUS register
        movwf    STATUS                ; restore pre-isr STATUS register contents
        swapf   w_temp,f
        swapf   w_temp,w            ; restore pre-isr W register contents
        retfie                        ; return from interrupt

; remaining code goes here


Main   
   
        bcf        STATUS,RP0            ; bank0
        movlw    0x0f   
        movwf    TRISA              
        bcf        STATUS,RP0            ; bank0
        clrf    PORTA
        bsf        STATUS,RP0            ; bank1
        movlw    0x00
        movwf    TRISB                ; set all pin on portB as output
        bcf        STATUS,RP0            ; bank0
        clrf    PORTB
etc...


anyone as an idea why

I got a similar problem when I did 'Build All' within MPLab IDE V8.88, for a project which still gets built successfully in a previous version of the MPLab IDE. The error message is:
 
MPLINK 4.45, Linker
Device Database Version 1.10
Copyright (c) 1998-2011 Microchip Technology Inc.
Error - section '.org_9' can not fit the absolute section. Section '.org_9' start=0x00000004, length=0x000009ca
Errors    : 1
I don't have "org_9" anywhere in my programs, and I checked all the settings for the linker (as far as I could) and they look the same as for the previous version of the MPLab IDE.
So, this is strange. Is there a bug in MPLINK 4.45 (too)????