CC2652R: Porting Zigbee Application to New hardware

Hello Damon Stewart,

I hope you are doing well. In our SDK we have documented migration paths that you could take, TI Z-Stack Migration Guide. 

In this case we should be able to use syscfg to directly migrate the CC2652R project to the new board, here we want to bring up syscfg click on the upper right device icon, and then click the "switch" button to bring up the following menu, where you should be able to chose your new device and then migrate settings automatically.

Thanks,
Alex F

Assuming a project SysConfig is already configured for "Use Custom Board" then no board file is necessary

 * @cliArgs --device "CC2652R1FRGZ" --part "Default" --package "RGZ" --rtos "tirtos7" --product "simplelink_cc13xx_cc26xx_source_sdk@8.30.01.01"
 * @v2CliArgs --device "CC2652R" --package "VQFN (RGZ)" --rtos "tirtos7" --product "simplelink_cc13xx_cc26xx_source_sdk@8.30.01.01"

Make sure to modify your command linker file (.cmd) as well to suit CC2652R1 flash memory sizes.

Regards,
Ryan

Hi Alex and Ryan - thank you both for your quick responses.  Much appreciated!  I tried these suggestions but didn't get very far.

1. The Migration Guide reference has a section here on migrating to boards that don't have a Launchpad.  Unfortunately our CC2652R1 part is not mentioned, but I can try to use one of the listed parts as a reference.

2. I think I followed Alex's recommendation on using syscfg but ran into problems.  I am running Code Composer Studio 12.8.1.  I opened my .syscfg file (for the CC2652R7 Launchpad), clicked on the triple dot icon in the top right, selected "Preferences and Actions", and clicked on the "Switch" button in the "Switch Target" actions section.  This seems like the right screen to migrate to a new product.  The only option I can select for "Board" is "None" - all other boards are grayed out.  And similarly, there are no Devices that I can select - all devices are grayed out.  If I click on the arrow to bring up the list of device options - they are all grayed out (see below).  I tried typing "CC2652R" manually, but this creates an error icon that indicates this migration is not supported.  (See below.)

3. I tried Ryan's suggestion to remove the --board flag from my .syscfg file and to change the device as he indicated.  Now when I run syscfg, I get the following error:

TypeError: Cannot read properties of undefined (reading 'components')
at scriptFunc (C:\Development\WattIQ\firmware_4xx_8.30\workspace\dmm_zr_light_remote_display.syscfg:140:63)
at cb (C:\ti\sysconfig_1.21.1\dist\webpack:\sysconfig\src\pinmux\services\scripting\runScript.ts:113:7)
at withDeprecatedAccess (C:\ti\sysconfig_1.21.1\dist\webpack:\sysconfig\src\pinmux\services\deprecatedAccessGuard.ts:14:10)
at runAsUserScript (C:\ti\sysconfig_1.21.1\dist\webpack:\sysconfig\src\pinmux\services\scripting\scriptingGuard.ts:61:3)
at iteratee (C:\ti\sysconfig_1.21.1\dist\webpack:\sysconfig\src\pinmux\services\scripting\runScript.ts:111:5)
at baseEach (C:\ti\sysconfig_1.21.1\dist\webpack:\sysconfig\node_modules\lodash\lodash.js:530:11)
at Function.each (C:\ti\sysconfig_1.21.1\dist\webpack:\sysconfig\node_modules\lodash\lodash.js:9409:52)
at iteratee (C:\ti\sysconfig_1.21.1\dist\webpack:\sysconfig\src\pinmux\services\scripting\runScript.ts:109:6)
at baseEach (C:\ti\sysconfig_1.21.1\dist\webpack:\sysconfig\node_modules\lodash\lodash.js:530:11)
at Function.va (C:\ti\sysconfig_1.21.1\dist\webpack:\sysconfig\node_modules\lodash\lodash.js:9409:52)

I have no idea why this is failing or how to fix it.  Is there any option that can give me more verbose output to debug this?  I didn't see anything in the --help context that indicated a "verbose" option.

Damon

Thank you Ryan - I was able to get my project to compile using the .syscfg file you sent. I'll start testing with it and let you know if I have any more questions.

Here is the .syscfg file I was using FYI.

dmm_zr_light_remote_display_LP_cc2652r7.zip

Interesting, this line was in my .syscfg file and was not in yours.  When I add it into yours, I get the error I was originally reporting about not being able to read components.

NVS2.externalFlash.$hardware        = system.deviceData.board.components.MX25R8035F;

I'll leave it out since there doesn't seem to be a need for it.  Thanks again for your help!

That line implies a LaunchPad is being used which has the MX25 external flash memory, although this is no longer the case I've checked to ensure that all of the NVSEXTERNAL and SPI SysConfig settings are the exact same so that your OAD application is not affected.

Regards,
Ryan