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.

LAUNCHXL-CC26X2R1: OAD IMG HDR has wrong prgEntry address

Part Number: LAUNCHXL-CC26X2R1

Hello TI Team,

The issue with the prgEntry address is still unsolved with simplelink_cc13x2_26x2_sdk_5_10_00_48

https://e2e.ti.com/support/wireless-connectivity/bluetooth/f/538/t/888554

The workaround changing the order of EntrySection works:

Why was it not adopted for SDK linker command files?

Best Regards,

Tobias

  • Hi Tobias,

    Thank you for posting in the E2E forums. I have assigned an expert to comment on this.

    Best,

    Nima Behmanesh

  • Hey Tobias,

    Looking at the prior thread, it looks like the ticket filed addresses a different issue than the one initially described in that thread. The default example does not seem to require this modification for functionality.

    Can you elaborate on your project (and how it differs from our example)? This way I can see why this modification is necessary in your project.

  • Hello Ammar,

    not sure what makes the difference but what happens if I use the default linker cmd file is that the EntrySection is placed at address 0xCC instead of 0x90:

    Best Regards,
    Tobias

  • Hey Tobias,

    Are you using an on chip or off chip OAD project when this occurs? Is security enabled or disabled? 

    I would like to try to recreate this on my end but am unable to using the default simple_peripheral_oad_offchip example.

  • Hi Ammar,

    the project is an off chip OAD project with security disabled.

  • Are you able to provide steps to help me reproduce this on my end? As mentioned, I am unable to reproduce this with the default example. Any instruction will help speed things up, so please let me know if this is possible on your end! 

  • Hello Ammar,

    Yes, I found out that it makes a difference if the linker command file is referenced in the Linker include paths or it resides in the local project configuration.
    So what I did is:
    1. Remove linker command file from linker file search path
    2. Copy the linker command file from example folder to the local project working copy

    Hope this helps to reproduce the issue.

    Best Regards,

    Tobias

  • Hey Tobias,

    Thanks for this, I will try to reproduce it shortly.

  • Hey Tobias,

    I've was able to reproduce this issue. I suspect the linker probably got confused in terms of the linker order. When it's changed in the project, the linker will follow the order of the files being included in this list, thus pushing around and/or defining symbols and memory regions that apparently are used by the subsequent files of this list.

    So, try the following:

    1. Remove the linker command file from the file search path.
    2. Copy the linker command file from the example folder to the local project
    3. Exclude the linker command file from the project (right click and select "Exclude from Build").
    4. Go back to the file search path and add the linker path selection from the workspace (in the same place the initial command file was).

    Then, rebuild the project. It should link correctly and you should be able to see the correct entry address without any modifications required to the files.

  • Hey Ammar,

    IMHO this is another workaround which is not straight forward.
    I would expect to select the linker cmd file in Properties->CCS Genaral->Linker command file. Similar to select the compiler version.

    I prefer to request a change in the linker command file template like suggested initially in this thread. Then the linker order does not matter.

    Best Regards,
    Tobias

  • Hey Tobias,

    I've filed a ticket internally to our dev team who will evaluate this issue and the proposed workaround(s). Thanks for your help investigating this issue and providing a workaround.