• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 562 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCSV5 link fails after tools update

Robert Wolfe
Mastermind 7860 points
Other Parts Discussed in Thread: CCSTUDIO

Hello,

I have a CCSV5 project, for the DSK6713, which use to compile, build and run without issue.  I unfortunately did an update on the tools, and it's never worked since.  And the "revert" option in installation fails.  The failure comes at the link, and is included below.  I'm not sure where to start looking.  Any advice or insight would be appreciated.

Regards,

Robert

<Linking>
"./workcfg.cmd", line 266: remark #10191-D: object ".printf" is not allocated,
"./workcfg.cmd", line 197: error #10099-D: placement fails for object
but is being placed as part of allocated object "GROUP_1"
.printf (COPY): {}

".hwi_vec", size 0x200 (page 0). Available ranges:
>> Compilation failure
IRAM size: 0x2fc00 unused: 0x3b8 max hole: 0x380
.hwi_vec: {
"./workcfg.cmd", line 289: error #10099-D: placement fails for object ".sts",
size 0x30 (page 0). Available ranges:
IRAM size: 0x2fc00 unused: 0x38 max hole: 0x1c
.sts: RUN_START(STS_A_TABBEG), RUN_START(_STS_A_TABBEG), RUN_END(STS_A_TABEND), RUN_END(_STS_A_TABEND) {
"./workcfg.cmd", line 221: error #10099-D: placement fails for object ".pinit",
size 0xf (page 0). Available ranges:
IRAM size: 0x2fc00 unused: 0x10 max hole: 0x8
.pinit: {} > IRAM
"./workcfg.cmd", line 237: error #10099-D: placement fails for object
".trcdata", size 0xc (page 0). Available ranges:
IRAM size: 0x2fc00 unused: 0x10 max hole: 0x8
.trcdata: {} > IRAM
"./workcfg.cmd", line 262: error #10099-D: run placement fails for object
".LOG_system$buf", size 0x100 (page 0). Available ranges:
IRAM size: 0x2fc00 unused: 0x0 max hole: 0x0
.LOG_system$buf: align = 0x100 {} > IRAM
"./workcfg.cmd", line 264: error #10099-D: placement fails for object
"GROUP_1", size 0xbb (page 0). Available ranges:
IRAM size: 0x2fc00 unused: 0x0 max hole: 0x0
GROUP {
"./workcfg.cmd", line 207: error #10099-D: run placement fails for object
".sem", size 0xb0 (page 0). Available ranges:
IRAM size: 0x2fc00 unused: 0x0 max hole: 0x0
.sem: {} > IRAM
"./workcfg.cmd", line 165: error #10099-D: run placement fails for object
".swi", size 0x84 (page 0). Available ranges:
IRAM size: 0x2fc00 unused: 0x0 max hole: 0x0
.swi: RUN_START(SWI_A_TABBEG), RUN_END(SWI_A_TABEND) {
"./workcfg.cmd", line 233: error #10099-D: placement fails for object
".gblinit", size 0x4c (page 0). Available ranges:
IRAM size: 0x2fc00 unused: 0x0 max hole: 0x0
.gblinit: {} > IRAM
"./workcfg.cmd", line 231: error #10099-D: placement fails for object
".switch", size 0x48 (page 0). Available ranges:
IRAM size: 0x2fc00 unused: 0x0 max hole: 0x0
.switch: {} > IRAM
"./workcfg.cmd", line 183: error #10099-D: run placement fails for object
".idlcal", size 0x4 (page 0). Available ranges:
IRAM size: 0x2fc00 unused: 0x0 max hole: 0x0
.idlcal: {
error #10010: errors encountered during linking; "work.out" not built
gmake: *** [work.out] Error 1

**** Build Finished ****

  • 0
    TI__Guru**** 173310 points
    What was the exact version of CCSv5 you were working with earlier when the build worked? And do you know which updates were picked up?

    Which version of compiler tools are currently being used for the build? You should be able to find that information under Project Properties->General.
  • 0 in reply to AartiG
    Mastermind 7860 points
    Hi,

    Thanks for the reply. I am using CCS v5.1.0.08020 now, but don't recall the version prior to the update. It's possible that it was the same. While preparing to answer your questions, I compared the installation history from before the updates, to after, and found the differences listed below.

    component latest prior
    C6000 Compiler Tools 7.3.19 7.3.0
    CCStudio p2 Feature none 5.0.1.201109261201
    CCStudio p2 Tool Feature none 5.0.2.201109261201
    Compiler Tools On-line Documentation 1.1.4 1.0.0.0
    Eclipse IDE for C/C++ Developers 1.4.2.20120213-0813 1.4.1.20110909-1818
    REQUIRED CCS Update Installation Tool 5.2.0.201204111758 none

    The compiler 7.3.19 was installed, but I've specified the previous 7.3.0 for the project, via Compiler version in Project Properties->General. That's because the 7.3.19 compiler does not have rts6700.lib, which I need, and failed with multiple obscure errors when trying to build it. BIOS is set to 5.4.11.38.

    However, I also found some buffers I added just prior to the updates, which I believe the project had previously built and linked without issue. But I removed them, just to see what happened, and I was able to compile and link again. It's possible the updates left me with less memory to work with, so I had to remove some. I typically build without optimization, to easily see all variables during debugging. But if I turn on optimization, I can add those buffers back in.

    Robert
  • 0 in reply to Robert Wolfe
    TI__Guru**** 173310 points

    Robert38116 said:
    However, I also found some buffers I added just prior to the updates, which I believe the project had previously built and linked without issue. But I removed them, just to see what happened, and I was able to compile and link again. It's possible the updates left me with less memory to work with, so I had to remove some. I typically build without optimization, to easily see all variables during debugging. But if I turn on optimization, I can add those buffers back in.

    Robert,

    It sounds like the buffers you added pushed it over the memory limits of the device. The fact that removing the buffers or compiling with optimization removes the error confirms this theory. You could take a look at the link map file and see the sizes of the different sections generated by the compiler, and then try adjusting the memory allocation of the different sections (in the tcf file) to see if you can get things to fit even with the buffers added.