• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 17 subscribers
  • Views 285 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.

CC1352P: Upgrade from SIMPLELINK-CC13X2-26X2-SDK_5.20.00.52 to SIMPLELINK-CC13XX-CC26XX-SDK_5.40.00.40

Derrick
Intellectual 320 points
Part Number: CC1352P
Other Parts Discussed in Thread: SYSCONFIG

I'm attempting to update an existing project built using v5.20.00.52 to v5.40.00.40 and have run into multiple issues. I believe I was able to solve most of them, but this last one I cannot figure out where these references are supposed to come from. 

 undefined                  first referenced                                                                                                     
  symbol                        in file                                                                                                          
 ---------                  ----------------                                                                                                     
 ClockP_Params_init         C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<PowerCC26X2.om4f>   
 ClockP_construct           C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<PowerCC26X2.om4f>   
 ClockP_destruct            C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<UART2CC26X2.om4f>   
 ClockP_getCpuFreq          C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<Timer.om4f>         
 ClockP_getSystemTickPeriod C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<PowerCC26X2.om4f>   
 ClockP_setTimeout          C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<UART2.om4f>         
 ClockP_start               C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<UART2.om4f>         
 ClockP_stop                C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<UART2.om4f>         
 HwiP_Params_init           C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<GPIOCC26XX.om4f>    
 HwiP_clearInterrupt        C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<SPICC26X2DMA.om4f>  
 HwiP_construct             C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<GPIOCC26XX.om4f>    
 HwiP_destruct              C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<I2CCC26XX.om4f>     
 HwiP_disable               ./src/utils/watchdog.o                                                                                               
 HwiP_disableInterrupt      C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<I2C.om4f>           
 HwiP_enableInterrupt       C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<I2C.om4f>           
 HwiP_interruptsEnabled     C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<UART2.om4f>         
 HwiP_plug                  C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<WatchdogCC26XX.om4f>
 HwiP_restore               ./src/utils/watchdog.o                                                                                               
 SemaphoreP_constructBinary C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<I2CCC26XX.om4f>     
 SemaphoreP_createBinary    C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<NVSCC26XX.om4f>     
 SemaphoreP_delete          C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<NVSCC26XX.om4f>     
 SemaphoreP_destruct        C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<I2CCC26XX.om4f>     
 SemaphoreP_pend            C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<I2C.om4f>           
 SemaphoreP_post            C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<I2C.om4f>           
 SwiP_Params_init           C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<I2CCC26XX.om4f>     
 SwiP_construct             C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<I2CCC26XX.om4f>     
 SwiP_destruct              C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<I2CCC26XX.om4f>     
 SwiP_post                  C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc13x2.a<I2CCC26XX.om4f>     
 
error #10234-D: unresolved symbols remain
error #10010: errors encountered during linking; "our_project.out" not built
tiarmclang: error: tiarmlnk command failed with exit code 1 (use -v to see invocation)
gmake: *** [our_project.out] Error 1

I compared the project settings with the example project found under the simplelink_cc13xx_cc26xx_sdk_5_40_00_40\examples\rtos\CC1352P1_LAUNCHXL\demos\portable\tirtos\ticlang directory, but could not find any differences in the highlighted sections below. What are we missing?

  • 0
    TI__Guru* 79501 points

    Unfortunately I am not able to tell you what is wrong based on the information above. 

    How did you go about porting your application? The recommended way it to start with a fresh example from the SDK you are porting to, and then use that as a starting point and move over your application files, rather that trying to update your "old" example to a new SDK.

    BR

    Siri

  • 0 in reply to Siri
    Intellectual 320 points

    I will try that. On a related note, I figured out how to use the NOROM version of DriverLib and compile it myself. I'd like to do the same with TI-Drivers so that we can modify the source, but it's not clear to me how those are currently built/included in the example projects since it seems to involve SysConfig. Is there documentation describing how to do this?

  • 0 in reply to Derrick
    TI__Guru* 79501 points

    If you are going to make changes to our driver implementation, you can include the driver files manually in your project and make changes to them. When using sysConfig you can have sysCong generate the config files once and then manually include also them in your project, and disable sysConfig. 

    Please note that we do not have resources to support/debug modified drivers.

    BR

    Siri