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/CC1352R: Platform import shows empty list

Part Number: CC1352R
Other Parts Discussed in Thread: BLE-STACK

Tool/software: Code Composer Studio

Hi,

Currently I am trying to create a custom platform based on the CC1352R1F3 platform. However, when I go to Project -> RTSC Tools -> Platform -> New and use the wizard to create a new platform, the Import list is empty. However, I can compile for the target and platform without any problems, so the problem seems to be with the platform wizard.

I have tried the suggested solution from this thread, but it does not work.

How do I solve this so I can create a custom platform based on the currently working one?

Thanks in advance!

  • Hi,

    For the BLE-Stack, we recommend taking one of the example projects as a starting point. Please see the BLE-Stack User's Guide:

  • Hi Marie,

    Thank you for your response.

    Actually I already have quite a big project working, indeed based on one of your examples. It already runs on my custom board.
    However, now I would like to customize the memory map for example. If I am correct, I need to create a custom platform for this, which is what is going wrong.

    When creating a new platform via the Platform Wizard (located at Project -> RTSC Tools -> Platform -> New), I get the option to click Import in the screen to configure the memory locations. However, the list in the import window is empty.

    I need that list to show the platform I am already using, as I need those settings as a starting point.

  • Hi,

    If you want to change the memory layout I would recommend just making the changes in the linker command file (cmd file) directly.

    I will send this thread to the CCS support team in case they can help. (But for the record, I would still recommend you to use the example projects as the starting points.)

  • This thread seems to be a duplicate of https://e2e.ti.com/support/tools/ccs/f/81/p/850624/3146305

    The problem was solved in the original thread.