• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 179 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.

C6727 in PADK: boot from prallel flash

Anusha James
Prodigy 165 points

Hi,

I am trying to import AnalogLoopback Project to CCSv4 to flash in PADK. Although Lyrtech supports only CCv3 project,I noticed In TI forum that many people imported succesfully to CCSv4.

However while importing using Legacy,padk.cmd is automatically generated.To boot from flash memory,we need TIsecondaryPADk.cmd too.

When I exclude padk.cmd from building the project,and copy paste the linking of CSL files from padk.cmd  in TIsecondaryPadk.cmd,I am getting an error like 

"cannot find file ".\Debug\TISecondaryBootPadk.obj" AnalogLoopbac line 0"

Why is it so?

Please help.

Thanks,

Anusha

  • 0
    TI__Guru* 84110 points

    Anusha,

    Yes, many people have imported successfully from CCS 3.3 to CCSv4 and to CCSv5. There are sometimes problems that have to be dealt with, but the process offers as much help as possible. Most of the problems I have had to deal with have to do with missing or old paths to various folders for headers and libraries and such.

    "padk.cmd" sounds like an odd name to be automatically generated. Are you sure about that? If there are files in your CCS 3.3 project that are not found in the CCSv4 project, use Explorer to copy them into the CCSv4 project folder and they will automatically be included in the build process. You might need to update some folder paths if you copy a file like TIsecondaryPadk.cmd.

    Line 0 is a bit strange. That may mean the file was referenced outside of the cmd files. Look at your build arguments in the console window and see if this file is being referenced somewhere. If it should be referenced, then it should be built.

    It sounds like you have a case where the import process from CCS 3.3 to CCSv4 is not perfect. But all you have to do is to get a copy of all the source files and get them to build in the new project folder. I usually just try to be patient with the process and look through all the files being referenced in the CCS 3.3 project to make sure they are properly imported into the CCSv4 project.

    Sometimes, it is easier to just create a new CCSv4 project, copy in all the files you need, and set the build parameters to match what you needed. This can be error-prone and tedious, which is why we have tried to do as much of the work as possible in the import process.

    Regards,
    RandyP