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.

CCS 3.3 upgrade error : -z invalid option in Linker command file



Hi,

I recently upgraded CCS 3.3 using SP 12.1 to CCS 3.3.82.13. Previously i was using 3.3.38 version. I was using the -z option in the linker command file to invoke the object files as follows.

-z "C:\Lyrtech\PADK\dsp\examples\analog loopback ori\AnalogLoopback1\Debug\Init.obj"

But now after upgrading, it shows it as invalid option and does not recognise the input files. Maybe the linker option is different but am unable to find what is the option to be used now.

DSP/BIOS not used.

C6727 dsp used.

code generation tools has also been upgraded.

Please help. urgent.

Anushree

  • Hello,

    anushree mahapatra said:
    code generation tools has also been upgraded.

    This is probably the change that impacted the build. Patching the IDE should not have any impact.

    What was the original code generation tool version and what version did you upgrade to?

    You may also want to switch back to the original it this is something urgent.

    Thanks

    ki

  • Hi,

    The original code gen tools was 6.0.2. And I have upgraded it to 6.1.21. I also suspect the change in code gen as the cause. 

    I have upgraded it for a reason as the previous  version of the IDE was causing problems cos of itsbugs. which were corrected in the recent service packs.

    anushree

  • Anushree,

    Could you please post the exact error message you are seeing? A screenshot would be good also.

    Thanks

    ki

  • Trouble Removing Breakpoint with the Action "Process CIO" at 0x100104a8:
    Error 0x80000008/-1060
    Fatal Error during: Break Point, 
    An unknown error prevented the emulator from accessing the processor
    in a timely fashion.
    It is recommended to RESET EMULATOR. This will disconnect each 
    target from the emulator. The targets should then be power cycled
    or hard reset followed by an emureset and reconnect to each target.


    Sequence ID: 8
    Error Code: -1060
    Error Class: 0x80000008

     

     

    The above error was obtained when I was using the oldest compiler 3.3.38.2 during the loading of the program on to the dsp. Thus i upgraded the compiler CCS to 3.3.83 and the code gen tools to 6.1.21 and while linking i got the following error.

    Error: -z an invalid option

    The linker command file has a statement as follows:

    -z "C:\...\...\..\examples\main.obj"

    due to which the error is shown and am unable to proceed with the build.

  • anushree mahapatra said:

    Error: -z an invalid option

    The linker command file has a statement as follows:

    -z "C:\...\...\..\examples\main.obj"

    due to which the error is shown and am unable to proceed with the build.

    -z is an option passed to the shell that tells it that all options following it are to be passed to the linker. It is typically passed on the command line during the linking step and is not specified in linker command files. Please remove the -z option from the linker command file and that should resolve the linker error.

  • Hi,

    I have previously mentioned that this error was not encountered when i was using Codegen tools 6.0.2 and I was sucssesfully able to include my .obj files in my linker command file using -z option. I had used -z option to inlcude my object files as by simply writing "Init.obj" at the beginning of my command file, I used to get an error saying it does not recognise the file in spite of including the file path in the build options. After upgrading my CodeGen to 6.1.2 it is not recognising -z option.

    Thus I have put up this query here. Removing -z option is giving the error as the file is not recognised - " no input file as Init.obj".

    Anushree

  • anushree mahapatra said:
    I have previously mentioned that this error was not encountered when i was using Codegen tools 6.0.2 and I was sucssesfully able to include my .obj files in my linker command file using -z option.

    That is odd. Can you copy and paste the full output of the CCS build window when using both versions of the compiler tools (which also shows the error generated with the newer version)?

    If the link command line shows something like "cl6x @Debug.lkf" then it means that Debug.lkf is the file that contains all the options and files passed to the linker. In that case, could you also attach the Debug.lkf files for both cases? This can help us compare the files to better understand what may be happening.