EasyLink Configuration

In the following, rfWsnNode is used as the example, but the instructions are valid for any EasyLink example.

Note

SysConfig will only make changes to selected files, listed in the Generated Files view. Any required changes to your application files you must do on your own.

Open An Example Project

Open the stand-alone SysConfig tool or a SysConfig-enabled example project (found in the {SDK_INSTALL_DIR}/examples/syscfg_preview folder).

Open the .syscfg file.

Adding RF Settings

You can add and configure a set of RF Settings in the RF Stacks->EasyLink->RF Settings view. Alternatively, you can use SmartRF Studio to generate RF Settings.

During initialization the EasyLink stack will default to a specific PHY. This default can be selected from the Default PHY drop-down menu (see Figure 57.). If your application needs to support more than one PHY, the Additional Supported PHYs drop-down provides the ability to select PHYs that can be switched to at run-time.

When selecting a PHY, you can choose from a pre-configured option or build your own custom solution. The custom solution is designated as “Custom” in the Default PHY and Additional Supported PHYs drop-downs.

Figure 57. Configure RF Settings by choosing a default PHY.

Note that if you add additional sets of RF settings in either the “Radio Configuration” view or the “TI DRIVERS” view, these will not automatically be supported by your EasyLink application. You will have to add them to your project manually.

EasyLink Settings

In the RF STACKS->EasyLink view you can configure EasyLink stack parameters. Parameters are explained in the tooltip that appears when you hover over it, and a more detailed explanation is given when clicking the question mark next to a parameters name. EasyLink stack settings are stored in easylink_config.c/h.

Basic Configuration

The basic EasyLink stack configuration includes address filtering, address size, and max data length. When these parameters are configured via SysConfig, they will take effect when the EasyLink_init() API is called.

Clear Channel Assessment (CCA) Configuration

The CCA configuration parameters are used when checking if a channel is clear of traffic before transmitting. The combination of RSSI threshold and channel idle time define what is considered a “clear” channel. The max and min backoff window, backoff time units, and random number generation function define the behavior when the channel is sniffed and found to be busy. The CCA configuration parameters take effect when using the EasyLink_transmitCcaAsync() API.

Advanced Configuration

The advanced configuration parameters require in-depth knowledge of the EasyLink APIs. When the advanced configuration parameters are configured via SysConfig, they take effect when the EasyLink_init() API is called with the exception of the Asynchronous Rx Timeout (ms) and the Test Mode Whitening parameters. These require the use of the EasyLink_receiveAsync() and EasyLink_setCtrl() APIs respectively.

Adjust Your Application

When you have finished adjusting the parameters, save the .syscfg file and generate the files.

You can see the generated files by clicking the <> symbol. In this example, board.c/h was generated by the “TI DRIVERS” view, easylink/easylink.c/h was generated by the EasyLink view and smartrf_settings/smartrf_settings.c/h was generated by the “Radio Configuration” view.

If you are using the System Configuration stand-alone tool, you will have to import every generated file to your IDE.

If you are using the SysConfig CCS plug-in, you can generate all the files by building your project. After the build has completed, you will find the generated files in the output folder of your project. In this example, it’s the folder called “Debug” of the rfWsnNode example.

Attention

Whenever you re-build the project, SysConfig will re-generate the files. Because of this, any changes made directly in the files (easylink/easylink.c/h) will be overwritten.

Most parameters configured in the EasyLink view of SysConfig will result in a #define in easylink_config.h. The file easylink_config.c contains a table of all supported PHYs.

Several EasyLink stack parameters configured in SysConfig require the application to use specific EasyLink APIs to take effect. The following table shows which parameters that require the use of these APIs in the application.

Configuration Parameter(s)	EasyLink API needed to take Effect
All parameters	EasyLink_init()
Clear Channel Assessment Parameters	EasyLink_transmitCcaAsync()
Asynchronous Rx Timeout (ms)	EasyLink_receiveAsync()
Test Mode Whitening	EasyLink_setCtrl()