SWRA656C May 2020 – October 2022 AWR6843 , AWR6843AOP , IWR1642 , IWR1843 , IWR6443 , IWR6843 , IWR6843AOP
Table 2-2 lists the changes required to port existing xWR1642 application code to xWR1843.
The scope of the migration notes provided in this section is limited to migrating to MMWAVE-SDK 3.3.
When migrating existing xWR1843 applications to SDK releases beyond MMWAVE-SDK 3.3, you should follow the incremental migration instructions provided in the corresponding SDK release notes.
| No | Summary | Components Impacted | Required Changes |
|---|---|---|---|
| 1 | MMWAVE-SDK 3.2.1 or above required for xWR1843 NOTE: It is recommended to use SDK 3.3.0 or above to include the latest API updates. | Makefile OR CCS projects | Application code must be re-compiled with MMWAVE-SDK 3.3.0 or above to run on xWR1843 Makefile: No change required if you are using SDK makefiles, as this is automatically handled in the SDK 3.3 environment setup script: C:\ti\mmwave_sdk_03_03_xx_xx\packages\scripts\windows\setenv.bat OR CCS Projectspec: If the application is compiled using CCS projectspecs, you need to update the products property in DSS and MSS projectspecs as shown below. <property name="products" value="com.ti.rtsc.SYSBIOS:6.73.01.01;com.ti.MMWAVE_SDK:3.3.0.03;"/> Example: For reference CCS projects for xWR1843, see the 18xx – mmWave SDK Demo available in: MMWAVE Industrial Toolbox. |
| 2 | Change device type | Makefile OR CCS projects | Makefile: For SDK makefile based build, set MMWAVE_SDK_DEVICE=iwr18xx/awr18xx in setenv.bat. C:\ti\mmwave_sdk_03_03_xx_xx\packages\scripts\windows\setenv.bat OR CCS Projectspec: If the application is compiled using CCS projectspecs, change the define SOC_XWR16XX to SOC_XWR18XX in DSS and MSS projectspecs. Example: For reference CCS projects for xWR1843, see the 18xx – mmWave SDK Demo available in: MMWAVE Industrial Toolbox. |
| 3 | Update RadarSS firmware file path | Makefile OR CCS projects (mss) | Need to use xWR18xx_radarss_rprc.bin in the metaimage generation step. Makefile: No change required if you are using SDK makefiles, as this is automatically handled in the SDK 3.3 environment setup script based on the MMWAVE_SDK_DEVICE variable. OR CCS Projectspec: If the application is compiled using CCS projectspecs, replace xwr16xx_radarss_rprc.bin with xWR18xx_radarss_rprc.bin in the metaimage generation steps (postbuild steps) Example: For reference CCS projects for xWR1843, see the 18xx – mmWave SDK Demo available in: MMWAVE Industrial Toolbox. |
| 4 | Use xWR18xx platform linker command file | Makefile OR CCS projects | Makefile: No change required if you are using SDK makefiles, as this is automatically handled in the SDK 3.3 environment setup script based on the MMWAVE_SDK_DEVICE variable. OR CCS Projectspec: If the application is compiled using CCS projectspecs, update the include paths for r4f_linker.cmd and c674x_linker.cmd to: COM_TI_MMWAVE_SDK_INSTALL_DIR/packages/ti/platform/xwr18xx/r4f_linker.cmd and COM_TI_MMWAVE_SDK_INSTALL_DIR/packages/ti/platform/xwr18xx/c674x_linker.cmd, respectively. Example: For reference CCS projects for xWR1843, see the 18xx – mmWave SDK Demo available in: MMWAVE Industrial Toolbox. |
| 5 | Include xWR18xx driver and CLI libs | Makefile OR CCS projects | Makefile: No change required if you are using SDK makefiles, as this is automatically handled in the SDK 3.3 environment setup script based on the MMWAVE_SDK_DEVICE variable. OR CCS Projectspec: If the application is compiled using CCS projectspecs, update the linker include paths to select the *_xwr18xx.aer4f and *_xwr18xx.xe674 lib versions, for example: -llibsoc_xwr18xx.ae674, -llibsoc_xwr18xx.xe674, -llibcli_xwr18xx.aer4f |
| 6 | Update sensor front-end configuration parameters | CLI config file (.cfg) and/or source code | Update TX channel bitmap in chirpCfg CLI command and/or API to account for the 3rd TX. Example: For more information, see the sample config files in C:\ti\mmwave_sdk_03_03_xx_xx\packages\ti\demo\xwr18xx\mmw\profiles. |
| 7 | Replace 16xx SOC definitions with 18xx equivalents. | MSS/DSS source code | Replace SOC_XWR16XX_* definitions/macros in source code with corresponding SOC_XWR18XX_* definitions. For instance: Code Snapshot: see Section 5.7. |
| 8 | API update for MMWave_open SDK 3.3 requires new parameter to be passed to MMWave_open | MSS/DSS start-up code | MMWave_open: Application must set the value of calibMonTimeUnit parameter before calling MMWave_open as shown below. The image below shows reference code updates in the SDK 68xx mmw demo (same applies to 18xx mmw demo) File:mmwave_sdk_03_03_xx_xx\packages\ti\demo\xwr68xx\mmw\mss\mss_main.c Code Snapshot: see Section 5.1. |
| 9 | API update for ADCBuf_open SDK 3.3 requires new parameter to be passed to ADCBuf_open | MSS/DSS start-up code | ADCBUF_open: Application must set the value of socHandle in the ADCBufparams structure before calling ADCBUF_open as shown below. The image below shows reference code updates in the SDK 68xx mmw demo (same applies to 18xx mmw demo). File:mmwave_sdk_03_03_xx_xx\packages\ti\demo\utils\mmwdemo_adcconfig.c Code Snapshot: see Section 5.2. |
| 10 | API update for CANFD_init SDK 3.3 requires new parameter to be passed to CANFD_init | Drivers | CANDF_init: Applications using CANFD driver must pass instance ID to the CANFD_init API as shown below. Only a value of 0 is supported at this time. The image below shows reference code updates in the SDK CANFD driver test (same for 18xx). File:mmwave_sdk_03_03_xx_xx\packages\ti\drivers\canfd\test\xwr618xx\main.c Code Snapshot: see Section 5.3. |
| 11 | General note on CLI configuration file | Sensor Configuration | For applications that re-use the mmWave
demo framework, ensure that the configuration commands (profileCfg,
chirpCfg, frameCfg, and so forth) follow the format provided in the
sample configuration files provided in the mmw demo directory: C:\ti\mmwave_sdk_03_03_xx_xx\packages\ti\demo\xwr18xx\mmw\profiles. For more information, see the Configuration File Format section of the mmwwave SDK User's Guide. See Section 6. |