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.

CC1352P7: CC1352P7 doesn't run CC1352P1 binary

Part Number: CC1352P7

I'm not able to find a software migration guide. Going through the TRMs, I don't see what would cause the issue.

I'm using a modified version of a BSL-based flasher (https://github.com/jadonk/cc2538-bsl/tree/add-bcf-and-zephyr-west-support) and the checksum looks good. The binary is produced using Zephyr and works fine on a CC1352P1.

What is different between these devices that could cause an image not to execute properly?

  • Hi Jason,

    The difference between these devices is the RAM and Flash size. 

    https://dev.ti.com/tirex/explore/node?node=AJfRVHzN2M6THppeeBnGiA__BSEc4rl__LATEST. So when building the project, starting with an appropriate example for the correct device and then porting the application over.

    Regards,
    Sid

  • ...but I'm using the subset of RAM/flash size, so shouldn't it just work?

    I'm not starting from an example, I'm starting from an application that runs on the CC1352P1. Starting with a new example is an unreasonable expectation.

  • The main difference would be the CCFG placement in flash.

    I checked the difference between the Code Composer Studio example projects for the CC1352P1 and CC1352P7. It is mainly the linker command file with the updated flash and ram sizes and also the driverlib.lib that is linked. 

    So while building the project for the 1352P7, replace the linker file used for 1352P1 with one for 1352P7 ( or just update the flash size and Ram size definitions). 

    Also, update the path to link to  ti\devices\cc13x2x7_cc26x2x7\driverlib\bin\ticlang\driverlib.lib instead of  ti\devices\cc13x2_cc26x2\driverlib\bin\ticlang\driverlib.lib

    Regards,

    Sid