WARNING: invalid linker option --retain=*(.selfcopy) (ignored)

The version 4.5.0 compiler supports the --retain option, so this doesn't make a lot of sense.  Are you sure you are using the 4.5.0 tools?  Please make sure you installed the compiler according to this wiki article.

Thanks and regards,

-George

Hi George,

I have installed the following package:-

TMS470CodeGenerationTools4.5.0

And yes, I also installed according to that wiki article.

Then I need to reproduce your problem somehow.  When you link CCS issues this command to the compiler ...

cl470 -@"BOOT_NAND.lkf"

Please attach the file BOOT_NAND.lkf to your next post.  You might need to change the file extension.

Thanks and regards,

-George

--abi=ti_arm9_abi -z -q -f0xFF -m"E:/RTC/UBL/IPNC_RDK_V5_15apr/flash_utils_dm36x/DM36x/CCS/UBL/NAND/UBL_DM36x_NAND_IPNC.map" -o"E:/RTC/UBL/IPNC_RDK_V5_15apr/flash_utils_dm36x/DM36x/CCS/UBL/NAND/UBL_DM36x_NAND_IPNC.out" -x -i"C:/CCStudio_v3.3/tms470/lib" -i"C:/CCStudio_v3.3/TMS470/cgtools/lib" -l"rtsv4_T_le_eabi.lib" --retain="*(.selfcopy)"
"E:\RTC\UBL\IPNC_RDK_V5_15apr\flash_utils_dm36x\DM36x\CCS\UBL\NAND\boot.obj"
"E:\RTC\UBL\IPNC_RDK_V5_15apr\flash_utils_dm36x\DM36x\CCS\UBL\NAND\debug.obj"
"E:\RTC\UBL\IPNC_RDK_V5_15apr\flash_utils_dm36x\DM36x\CCS\UBL\NAND\device.obj"
"E:\RTC\UBL\IPNC_RDK_V5_15apr\flash_utils_dm36x\DM36x\CCS\UBL\NAND\device_nand.obj"
"E:\RTC\UBL\IPNC_RDK_V5_15apr\flash_utils_dm36x\DM36x\CCS\UBL\NAND\nand.obj"
"E:\RTC\UBL\IPNC_RDK_V5_15apr\flash_utils_dm36x\DM36x\CCS\UBL\NAND\nandboot.obj"
"E:\RTC\UBL\IPNC_RDK_V5_15apr\flash_utils_dm36x\DM36x\CCS\UBL\NAND\selfcopy.obj"
"E:\RTC\UBL\IPNC_RDK_V5_15apr\flash_utils_dm36x\DM36x\CCS\UBL\NAND\uart.obj"
"E:\RTC\UBL\IPNC_RDK_V5_15apr\flash_utils_dm36x\DM36x\CCS\UBL\NAND\uartboot.obj"
"E:\RTC\UBL\IPNC_RDK_V5_15apr\flash_utils_dm36x\DM36x\CCS\UBL\NAND\ubl.obj"
"E:\RTC\UBL\IPNC_RDK_V5_15apr\flash_utils_dm36x\DM36x\CCS\UBL\NAND\util.obj"
"E:\RTC\UBL\IPNC_RDK_V5_15apr\flash_utils_dm36x\DM36x\CCS\UBL\UBL.cmd"

Hi George, 

File is attached with extension changed, as requested.

I cannot reproduce that linker diagnostic involving --retain.  But I do see some inconsistencies.  

The option --retain only works for EABI builds.  But you use the option --abi=ti_arm9_abi.  And you use the RTS library rtsv4_T_le_eabi.lib.  At least one of these is wrong, but I don't know which one.

Thanks and regards,

-George

The inconsistency is due to obsolete version of code generation tools linked to my system. I have installed TMS470 code generation tools 4.5.0. Yet the CCS v3.3 continues to use v4.1.4. (See image)

I want to upgrade to 4.5.0.But i am unable to do so. The installation of Code gen tools seems to go fine..But the linking with the CCS v3.3 is not happening. What to do?

This wiki article describes how to change the compiler version used by CCS 3.3.

CCS 3.3 is very old.  We just released CCS 6.0.  Are you sure you don't want to upgrade?

Thanks and regards,

-George

Hi George, 

We already have a 5.3.0. But all the bootloader, u-boot and FS flashing has to be done using 3.3 version is what is recommended by our vendor-Appro. 

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/100/p/8000/32300.aspx

This link also validates that Code Gen tools are required so that the build options can be modified. Please help me install.

Sai Kamat said:

Please help me install.

I presume you are going through the steps listed here.  Which step is not working?  Exactly what is happening?

Thanks and regards,

-George

The follw step doesn't work.

"Another option that does not require an up-to-date CCS license is to download the tools from here. Note that ARM code generation tools are not available on this page but they are available through the Update Advisor."

I anyways have setup of code gen tools:-\

which I install.Though the installation goes fine...there's some linking with the CCS v3.3 that I am missing. 

Sai - where did you get that 4.5.0 CGT installer?

Hi Ki-Soo Lee, 

The CGT installer was given to us by the product vendor Approho.

Point to be noted is that, this same setup has worked on my colleague's PC, i.e. his CCSv3.3 has CGT upgraded to 4.5.0. But he too has not understood what the problem is.

I also contacted the vendor. Here's the conversation.

Sai Kamat said:

Point to be noted is that, this same setup has worked on my colleague's PC, i.e. his CCSv3.3 has CGT upgraded to 4.5.0. But he too has not understood what the problem is.

I suspect you have a registry access problem. It looks like you are using Windows 7. Note that CCSv3.3 is not supported on Windows 7. There are various issues when using Windows 7, a lot of it due to permissions issues. Did you install CCSv3.3 and the new CGT 4.5.0 under and account with administrator access and also trying to run with administrator access?

Hi Ki-Soo Lee,

Yes I installed under administrator access and also ran with administrator access. It did not help. It seems particularly weird after all this, that the afore-mentioned colleague's PC also has a Windows 7.

But considering that Win 7 has various issues particularly with registry access problem, I think this problem goes beyond the purview of e2e enthusiasts & falls into Microsoft registry domain...

I henceforth assume that the newer versions of CCS (5.3.0 for e.g) support everything that 3.3 does & should not create much of a problem in compiling my UBL codes, in what otherwise so far, seemed like a walk in the park task...

thank you.

yeah, v3.3 on Windows Vista and higher is a bit of a crapshoot. Some get it to work fine, many others have all sorts of issues. Those with issues tend to use XP VMs to avoid all the hassle.

Newer versions of CCS certainly plays much nicer with the latest Windows versions. You can also use the older compiler version that came with v3.3 or ones that came after it with CCSv4/5/6. I certainly recommend moving to the latest versions. The only issues is that the environment is so drastically different that there will be an initial learning curve.

ki