CC1352P7: Migration from CC1352P1

Deric Eldredge

Part Number: CC1352P7
Other Parts Discussed in Thread: CC1352P

I have a design that has over 10 years of software design. I am currently using the cc1352P1 and my environment and OS is base on the TI SDK simplelink_cc13x2_26x2_sdk_4_10_00_78 and GCC. We are not using CCS. We want to migrate to the CC1352P7 which is a direct cousin of the CC1352P1 as far as I can tell it only has more flash and ram. I can not currently port the SDK required for the new part because V6 is so different from V4. I would like to know how I can get the CC1352P7 to work with the V4 SDK. Or how else can we get our code to run because doing a port of our OS and application is a job we do not have the time and resource for.

over 2 years ago

0 Deric Eldredge over 2 years ago

Prodigy 70 points

Clarification: The title and body should be using CC1352P because CC1352P1 is one of the launchpad part numbers.

0 Sid over 2 years ago in reply to Deric Eldredge

TI__Mastermind 20407 points

Hi Deric,

As you mentioned, there are a lot of changes between these two version of the SDK.

The recommendation would still be to port to the new SDK with the support for the new device.

Having said that, you could try the changes suggested in the last response of this thread, to see if the application builds with the older SDK and driverlib for the newer device. And also use the linker cmd file for the cc1352p7 device to make sure the CCFG is placed correctly.

https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1135056/cc1352p7-cc1352p7-doesn-t-run-cc1352p1-binary

Regards,

Sid

0 Deric Eldredge over 2 years ago in reply to Sid

Prodigy 70 points

When I substitute the driverlib directory from V6 it has an error because it is missing the file driverlib_release.h

0 Deric Eldredge over 2 years ago in reply to Deric Eldredge

Prodigy 70 points

If I only replace the driver-lib binary I get lots of linker errors. The first one is undefined reference to `driverlib_release_0_54539'. That error comes from when the code tries to call NoRTOS_start()

0 Sid over 2 years ago in reply to Deric Eldredge

TI__Mastermind 20407 points

Hi Deric,

Unfortunately, like you mentioned there is no device support for that device on the SDK.

If the driver lib source did not compile with the path change, then you would need to use the new SDK which supports the CC1352P7 device. Sorry for the inconvenience.

Regards,

Sid

Sub-1 GHz

Sub-1 GHz forum

CC1352P7: Migration from CC1352P1