Migrate software examples from CC13x4 to CC26x4

This section provides the necessary steps to migrate an existing software example or project from a CC1354P10_x device to a CC26x4 device. This assumes you have imported a CC1354P10_x project into your CCS workspace.

  1. To avoid confusion, it is advised to rename the project before proceeding with the porting effort. To rename the project, right click on the imported project, select the rename option and provide a new name for the project in the pop up.

    ../_images/rename_project.png

  2. Go to Project properties, in the predefined symbols section, change DeviceFamily_CC13X4 to DeviceFamily_CC26X4.

    ../_images/predefined_symbol_cc26x4.png

  3. Make sure that the SysConfig product associated with the project is version 1.16.2 or later. This ensures that SysConfig has the metadata for your CC26x4 device.

    ../_images/sysconfig_version.png

  4. Open the device view of SysConfig and click on the Switch option.

    ../_images/switch_device.png

  5. Select the required target device and select the board as ‘None’. Ensure that you have left the Lock PinMux selection unchecked. This is necessary because we still need to edit the pin mapping to fit our custom board design.

    ../_images/board_device_selection.png

After clicking “Confirm”, SysConfig will perform best-effort device migration. Most settings will be correctly migrated, but sometimes (e.g. pin assignments to custom boards) SysConfig cannot select a good default for the new environment. In these cases, SysConfig will highlight settings that must be manually reviewed with warnings and/or errors. Some of these errors and warnings are illustrated below.

Caution

The following steps are provided for reference only. These are based on mounting a CC2674R10 device on a LP-CC2652R7 LaunchPad. You need to resolve the errors based on your own custom design.

If you are using either UART or Display

Make the UART PinMux selection as shown in the image.

../_images/uart_or_display.png
If you are using Buttons/Leds

If you are using BTN-1 or BTN-2 on the board, make the following selection.

../_images/btn_1_and_btn_2.png

If you are using the Red LED or the Green LED. make the following selection.

../_images/led_green_and_red.png

If you are using the Button/LED driver from the TI DRIVER APPS section on SysConfig, you should make the PinMux selection in the Button or LED sub module.

../_images/ti_driver_apps_btn_led.png
If you are using the NVS driver

The chip select pins must be configured as shown in the figure

../_images/nvs_migration.png
If you are using the SPI driver

The SPI pins must be configured as shown in the figure

../_images/spi_migration.png
If you are using MCUBoot and Bootloader Backdoor

Configure the bootloader backdoor and address of the flash vector table as shown in the picture.

../_images/mcuboot_migration.png
If you are using RF stacks/Proprietary RF

The RF Design and the XOSC configuration must have the following selections irrespective of the wireless stack or custom Phy used.

In the RF design module, you need to “accept” the changes by clicking on “accepting” in the error message. Select “Not used” for the Sub-1GHz Frequency Band, the CC2674x is a 2.4G only device.

../_images/RF_design_migration.png

It is also important to un-check the XOSC Cap Array Modification option in Device Configuration module. If you do not uncheck this, there is an unwanted offset added to the center frequency.

../_images/xosc_cap_array.png
If you are using a custom Phy (IEEE 802.15.4 Phy)

  1. Under Custom Phy selection, click on here in the messages to dismiss the errors. These error arise from migrating a dual band(2.4G and Sub1G device) to an exclusively 2.4GHz device. We will resolve the errors manually in the following steps.

    ../_images/custom_phy.png
    ../_images/code_export_proprf.png

  2. Manually update the RF Command Symbol generated for the CMD_RADIO_SETUP by adding the ieee154 suffix.

    ../_images/ieee_suffix.png
Regarding antenna switching

The CC1354P10_x device is a dual band device and also has an additional high PA path, while CC26x4R devices are single band devices (i.e. only have a single RF path at its output). Thus, it does not require an antenna switch. In the RF module of SysConfig, you need to reduce the number of antenna switch control pins to 0.

../_images/antenna_switching_disable.png

But please note that if you are migrating to a CC2674P10 device, due to the presence of an additional high PA RF path, you might need an antenna switch and you would have to implement an antenna switching callback to control this antenna switch at the application level.

For reference implementation, you can check the antenna switching callback found in ti_drivers_config.c in any prop_rf examples for LP_CC1354P10_x.

../_images/antenna_switching_cb.png