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

CC2642R: Hex File issue

Shrikant Koli
Prodigy 110 points
Part Number: CC2642R
Other Parts Discussed in Thread: SIMPLELINK-CC13XX-CC26XX-SDK

Dear Team,

I have copied my one project into the another directory.

if i compiled the copied project, then generated hex file is not match with existing hex file.

due to this my another functionality does not work.

Regards,

Shrikant K

  • 0
    TI__Guru**** 202266 points

    Hi Shrikant,

    Can you please explain exactly how/where you are copying your project and whether compiler/linker build settings are retained?  What parts of memory are changed in the hex file?  Have you tried this with out-of-box SIMPLELINK-CC13XX-CC26XX-SDK examples, and what SDK version and example are being used?  Can you specify which function breaks after copying the project?

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 110 points

    Hi Ryan ,

    Thanks for your support.

    problem is resolved. but now i am facing different issue.

    whichever related to board_key.c file. 

    for example if i change board_key.c into the simple peripheral code.

    then whenever i am try to open simple central code , so in that code board_key.c is change.(That should not happen)

    why this will happen if both code has different scope.

    is their any setting into the code composer studio.

    NOTE : SDK version is : simplelink_cc13x2_26x2_sdk_5_20_00_52

    Regards,

    Shrikant Koli

  • 0 in reply to Shrikant Koli
    TI__Guru**** 202266 points

    You are likely using a linked file (check the file properties) which resolves to <sdk directory>\source\ti\ble5stack\common\cc26xx\board_key.c.  You should replace this linked resource with a local copy so that changes do not propagate to other projects as well.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 110 points

    Hello ,

    Can you provide the picture, where i can change the linked file path with my local file.

    That is really helpful for me.

    Regards,

    Shrikant Koli

  • 0 in reply to Shrikant Koli
    TI__Guru**** 202266 points

    Here is what I typically do to replace linked files.  Red is delete and blue is copy/paste.  Choose the "Copy files" option when prompted.

    Regards,
    Ryan