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.

IWR1843BOOST: Out of Box Demo Build Configurations

Part Number: IWR1843BOOST

Tool/software:

I had been working with the MRR demo for the IWR1843BOOST EVM.  The demo includes Debug and Release configurations, which is expected and makes sense.  I have switched to the Out of Box demo which now shows AOP and ISK build configurations and not the expected Debug and Release configurations.  What are these configurations about and how do I get the expected Debug and Release configurations?

  • Hello, 

    In the case of the out of box demo for 1843, the 'AOP' and 'ISK' build configurations are used to specify the antenna type (being antenna on package or pcb based antenna). For each build configuration, a predefined symbol is added which determines the antenna processing code that is included at compile time. 

    You are correct that most of the examples provided include a 'Debug' and 'Release' build configuration. These configurations can be used to enable different compiler optimization levels or change other build settings for debugging purposes. If you wish to add a 'Debug' build configuration to 1843 OOB demo which disables compiler optimization you could do this with these steps.

    1. Open the out_of_box_1843_dss.projectspec and out_of_box_1843_mss.projectspec in a text editor (an editor which can interpret XML would be best). The files can be found at: {RADAR_TOOLBOX_INSTALL}\source\ti\examples\Out_Of_Box_Demo\src\xwr1843

    2. Under the project tag. edit the configurations field as below

            configurations="isk, aop, isk-debug, aop-debug"

    3. add a configuration tag for the new build configurations (just as is done for 'AOP' and 'ISK'). Example for DSS projectspec:

    		<!-- Device specific Configuration -->
            <configuration name="isk-debug"
            compilerBuildOptions="
            -Ooff"
            linkerBuildOptions="
            -I${COM_TI_MMWAVE_SDK_INSTALL_DIR}/packages/ti/datapath/dpc/dpu/aoaproc/lib 
            -llibaoaproc_hwa_xwr18xx.ae674
            "/>
            
    		<!-- Device specific Configuration -->
            <configuration name="aop-debug"  
            compilerBuildOptions="
            -DUSE_2D_AOA_DPU
            -DXWR18XX_AOP_ANTENNA_PATTERN
            -Ooff"
            linkerBuildOptions="
            -I${COM_TI_MMWAVE_SDK_INSTALL_DIR}/packages/ti/datapath/dpc/dpu/aoa2dproc/lib 		
            -llibaoa2dproc_hwa_xwr68xx.ae674
            "/> 

    4. Now upon importing the project to CCS you should have the new debug build configurations.

    Best regards,

    Josh

  • Thank you for the quick reply.  I know AOP stands for Antenna-On-Package.  What does ISK stand for?

  • Hello, 

    My apologies for the confusion. This thread discusses this question. In short 'ISK' originally stood for 'Industrial Starter Kit' but in general we use it to refer to the antenna design of the xWR6843ISK EVMs. 

    https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1051712/faq-awr6843isk-what-does-isk-stand-for 

    Regards,

    Josh