• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 452 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.

CCS/TLC5510A: CCS 3.3 project imported to CCS 6.3 compiles but does not run correctly.

Ben L
Prodigy 90 points
Part Number: TLC5510A

Tool/software: Code Composer Studio

I'm in the process of converting a project for the c510a DSP from CCS 3.3 to 6.2. If managed to get past the initial round of issues and the project will compile under CCS 6.2. When I step through the converted project using JTAG however, it works initially then wanders off into un initialised memory and stops responding to JTAG. I think it's something to do with memory mapping though I'm not sure.

Anyone pointers from who's experienced similar issues would be greatly appreciated. 

Cheers.

  • 0
    TI__Guru**** 160200 points
    Ben,

    Moving from CCSv3.3 to CCSv6 or later is not going to be a trivial task.

    Does your project use DSP/BIOS?

    If you take the .out file generated by CCSv3.3 and load it in CCSv6.2 does that run correctly? If it does not then it could be a debugger configuration issue, maybe in the GEL files.

    Regards,
    John
  • 0 in reply to JohnS
    TI__Guru**** 428990 points

    Ben - I believe CCSv3.3 comes with an older version of the compiler than what comes with v6. In my CCSv3.3 installation, I see that the C55x compiler is version 4.2.3 while I believe v6 comes with 4.4.1. You may want to try using the same version of the compiler that you used in 3.3 just to rule out any impact of the difference in versions

    Note that you can point your CCSv6 installation to use the compiler that comes with CCSv3.3:

    Thanks

    ki

  • 0 in reply to JohnS
    Prodigy 90 points

    Hi John,

    Thanks for replying to my question. I have tried using the .out file generated in CCSv3.3 and it does work as expected. Any other ideas?

    Oh and yes, it does use dsp/bios.

    Cheers,

    Ben

  • 0 in reply to Ki
    Prodigy 90 points
    Hi Ki,

    Thanks for replying. I've tried rolling back the compiler to version 3.3.2 and version 4.1.2. The program won't link correctly with either of these compiler versions. I get the error:

    "program.cmd: error: system error, can't open file '/.obj' for input: No suchfile or directory"

    Quite strange. Any ideas?
  • 0 in reply to Ben L
    TI__Guru**** 428990 points
    I noticed that I am using a more recent version of CCSv3.3. The original release came with 3.2.2, which is a major version difference. I would be good to use that version of the compiler.

    As for your error, can you provide the full build output in the build console? Also provide the linker command file that generated the error

    Thanks
    ki
  • 0 in reply to Ki
    TI__Guru**** 428990 points
    Hello,
    I haven’t heard back from you, hence this issue is being closed. If you wish to continue the discussion, please post a reply with an update below (or create a new thread).

    Thanks,
    ki
  • 0 in reply to Ki
    Prodigy 90 points

    Hi there,

    FYI I solved the problem in the end. The newer version of the compiler seemed to use more stack space when using the LOG_printf function. This caused the main stack to spill into the sys stack, which corrupted a return address. I manually inserted a line into the .tcf file to increase the stack size a little and all is working.

    Thanks for your help.