• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 55 subscribers
  • Views 1970 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linking failed (in IAR)!

Flo
Intellectual 360 points
Other Parts Discussed in Thread: CC2533, CC2530, REMOTI, CC2430, CC2510

Hello everybody!

I am  new to IAR and CC2533 RF4CE Basic Development Kit (Actually, I am on a training period and I have to test a remote).

In the forum, someone else had a similiar problem to mine but I need a different file.

I have just downloaded the last version of IAR (v8.10), and I had to convert files (it was in an older version).

When I rebuild the workspace, I have get the following errors:

Fatal Error[e72]: Segment PDATA_Z must be defined in a segment definition option (-Z, -b or -P)
Error while running Linker

I use  the rsa_cc2530-CC2530F64.

Apparently, rsa_cc2530.d51 doesn't exist (the errror is located in rsa_cc2530.map).

Otherwise, I use also ti_51ew_cc2530f64.xcl.

Please, can anybody help me??

Ps: if ever you need further information, don't hesitate.

 

  • 0
    TI__Genius 14940 points

    I'm not sure if this is the correct answer as I haven't loaded up the 8.x version yet.  But there was a similar issue in going from the 7.5x to the 7.6x versions.  In this case, the conversion of the older project file selects a generalized form of the CC2530 and you need to select the exact form of the target.  This should be in the directory

    $TOOL_KIT$\8051\config\devices\Texas Instruments

    You select this from the project options dialog under the generalized catagory and the Target tab.  Make sure you update the code model to be large and make sure the stack used is the XDATA_REENTRANT form as selecting this target may change those fields on the tab pane.

    Jim Noxon

  • 0
    TI__Intellectual 1250 points

    Floriane,

    Same answer as another post you create:

    http://e2e.ti.com/support/low_power_rf/f/159/p/120972/431477.aspx#431477

     use IAR version 7.60 with all patches (so IAR v7.67) instead of v8.10.

     

    anyway, if you really want to use IAR8.1. first you will need add the description file as explain above.

    and you will will to do the folllowing modification in the linker file (linker file are in :Projects\RemoTI\common\cc2530, file *.xcl)

    change

    -Z(XDATA)XDATA_Z,XDATA_I=_XDATA_START-_XDATA_END
    to

    -Z(XDATA)PDATA_Z,XDATA_Z,XDATA_I=_XDATA_START-_XDATA_END

    Cordialement,

    Calimero

     

     

  • 0 in reply to _Calimero_
    Intellectual 360 points

    Calimero,

     

    After following your instructions, the problem of linking is solved.

    Thanks a lot.

    Flo.

  • 0 in reply to Flo
    TI__Intellectual 1250 points

    Floriane,

     

    Did you stick with IAR 8.10 or did you change to IAR 7.60?

     

    Regards

  • 0 in reply to _Calimero_
    Intellectual 360 points

    I stuck with IAR 8.10

    Regards

  • 0 in reply to _Calimero_
    TI__Genius 14940 points

    Thanks for adding this addition to the post.  However, it seems a bit uncomfortable that we need to be modifying IAR specific files.  Is there a target specific .xcl file for the CC2530's just like there is for the .i51 files?  If so, would it be better to utilize that instead of modifying the linker command file itself?

    The real question, I am still working with IAR on, is why the conversion process cannot provide proper conversions for the CC2530 yet it can for so many other CC parts.

    Jim Noxon

  • 0 in reply to Jim Noxon
    TI__Intellectual 1250 points

    im

     

    the .*.xcl files are not IAR specific, but create by TI.

     

     

    Regards,

    Calimero

  • 0 in reply to Jim Noxon
    Intellectual 360 points

    Sorry for my last answer (I had problems with the Internet).

     

     

     

     

     

     

     

    Actually, when I first installed IAR (its most recent version), the linker file by default was

    ti_51ew_cc2530.xcl  (it doesn't exist in TI directories). I replaced the file by ti_51ew_cc2530f64.xcl.

    Then, I modified the .xcl file by adding

    PDATA_Z.

    Moreover, IAR kept the wrong target-specific debbugger files (it targets

    cc2530.ddf whereas this file doesn't exist in directories of T.I), I replaced the file by ioCC2531F64.ddf.

    It is the same thing for other CC (cc2530f128 for example).

    Hope being a little clear.

    If ever you have other question or it is a little confuse to you, don't hesitate to ask me.

    Regards.

  • 0 in reply to Flo
    TI__Genius 14940 points

    Yes, I recognized ths as well.  This change in file architecture was initiated in the 7.6 version.  The problem is if you have a project from 7.5x or earlier and you run the conversion routines, the project is not properly updated.  I'm sure this is partly because the earlier versions didn't require specification of the memory layout and you simply chose either the non-banked form or the banked form and made the specific modifications for the specific memory layout according to comments within the .xcl file.  Unfortunately there are no default CC2530.xcl files to point converted projects from earlier builds to the same default .xcl types as before.  From what I see, if you were to choose a general CC2530 part, you should be defaulted to the CC2530F64.xcl file and if you choose a banked memory model you should be defaulted to the CC2530F256.xcl file.

    I understand itshould be the responsibility of the user to select the appropriate memory layout as it is the linker's responsibility to map the object code to the physical memory of the target but it seems like IAR or TI (whoever) has made a change in file architecture but only partially implemented it.  Thus, coverting an older project file for a CC1110 still utilizes a general CC1110.xcl file which is targeted for the 32kB flash version.  Similar for the CC2510 and CC2430.  So 1) why only the CC2530 has had it's file architecture (naming conventions) changed and 2) why does the project conversion operation break the ability of the project to link by not managing this change in file architecture?

    Jim Noxon

  • 0 in reply to Jim Noxon
    Intellectual 360 points

    I don't know. I use the files for the first time.

    I am working on it for a week, I made some researches in provided documents. I simply followed what is said in "RempTI Sample Application User's Guide" (swru201A) and it wasn't updated. I wanted to install the version indicated by this document and I didn't find the older version. Consequently, I had to install the 8.10 version. When I opened the provided workspace, I met these problems (and I  don't know the software IAR very well, I discovered it only a week ago).

    Regards,

    Flo.