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.

IWR1642BOOST: Sensors forum

Part Number: IWR1642BOOST
Other Parts Discussed in Thread: IWR1843BOOST, UNIFLASH, SYSBIOS

When I use IWR1642BOOST for level detection, the case I use is High Accuracy Range Measurement Lab(dev.ti.com/.../node
I put the radar board above the level, and during the level rise and fall, the radar board does not detect the level change,What is the cause and how should I fix it?

  • Hi Shiyu, 

    Have you run the Out of Box Demo successfully?  This will help me to rule out any hardware issues.

    Regards,

    Brennan

  • Hi Brennan Hartigan,

    I tried to run X, but it failed. Here is the problem I am having:

    1.About IWR1843BOOST:

    I am using uniflash(7.1.0) to burn the program and the port cannot be connected. The port is normal in the device manager on my computer, but it shows com4. How can I fix it?

    [2022/2/12 下午7:31:37] [INFO] Cortex_R4_0: Initialization complete.
    [2022/2/12 下午7:31:37] [INFO] Cortex_R4_0: Flashing process starting...
    [2022/2/12 下午7:31:37] [INFO] Cortex_R4_0: Connecting to COM Port COM4...
    [2022/2/12 下午7:31:37] [INFO] Cortex_R4_0: Reset connection to device
    [2022/2/12 下午7:31:37] [INFO] Cortex_R4_0: Set break signal
    [2022/2/12 下午7:31:57] [ERROR] Cortex_R4_0: Initial response from the device was not received. Please power cycle device before re-flashing.
    [2022/2/12 下午7:31:57] [ERROR] Cortex_R4_0: Not able to connect to serial port. Recheck COM port selected and/or permissions.
    [2022/2/12 下午7:31:57] [INFO] Cortex_R4_0: Flashing instance clean-up initiated...
    [2022/2/12 下午7:31:57] [INFO] Cortex_R4_0: Instance deinitialized!

    2.About IWR1642BOOST   

    I did not find the file(C:\ti\mmwave_industrial_toolbox_4_10_1\labs\Out_Of_Box_Demo\prebuilt_binaries) corresponding to IWR1642BOOST when I followed the instruction steps to burn the file, which file should I use instead?

    3.About uniflash(7.1.0)

    When I was using uniflash for file burning, I found that the software runs unstable, he sometimes can recognize the port to work, and sometimes it shows that it can't recognize the port, with some chance. Is it a problem with the configuration of my computer environment or a problem with the hardware device?

  • Shiyu, 

    1) You need to set the SOP switches on the IWR1843BOOST for flashing mode, as follows:

    Please refer to the EVM Setup Operational Modes page to ensure your device is configured for the correct step of the demo process.

    2) You can find the 16xx Out of Box Demo in Industrial Toolbox 4.9.0.  In the TI Resource Explorer, follow these steps:

    Click the three dots next to "Industrial Toolbox - 4.10.1" and then click "Manage Versions."

    Check the box next to the 4.9.0 version.

    Then download 4.9.0.  You will find the out of box demo for 16xx at:

    C:\ti\mmwave_industrial_toolbox_4_9_0\labs\out_of_box_demo\16xx_mmwave_sdk

    Follow the mmw_16xx_user_guide, as the steps to run this version of the demo are different than other EVMs.

    3) Ensure you are pressing the NRST button on the EVM before flashing or making any device configuration changes.

    Regards,

    Brennan

  • I have run the program according to the manual. I am using CCS version 7.4, and I get an error during the run, as shown in the picture, showing that there is no file, as shown in the picture, how should I solve it?

    **** Build of configuration Debug for project mmw_dss_16xx ****

    "C:\\ti\\ccsv7\\utils\\bin\\gmake" -k -j 4 all -O

    rm -f C:/ti/mmw_dss_16xx/xwr16xx_mmw_dss.bin
    makefile:193: recipe for target 'pre-build' failed
    process_begin: CreateProcess(NULL, rm -f C:/ti/mmw_dss_16xx/xwr16xx_mmw_dss.bin, ...) failed.
    make (e=2): 系统找不到指定的文件。

    gmake[1]: [pre-build] Error 2 (ignored)

    'Building file: "../dss_mmw.cfg"'
    'Invoking: XDCtools'
    "C:/ti/xdctools_3_50_04_43_core/xs" --xdcpath="C:/ti/bios_6_53_02_00/packages;C:/ti/ccsv7/ccs_base;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C674 -p ti.platforms.c6x:IWR16XX:false:600 -r release -c "C:/ti/ti-cgt-c6000_8.1.3" "../dss_mmw.cfg"
    making package.mak (because of package.bld) ...
    generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
    configuring dss_mmw.xe674 from package/cfg/dss_mmw_pe674.cfg ...
    generating custom ti.sysbios library makefile ...
    Starting build of library sources ...
    making C:/ti/mmw_dss_16xx/src/sysbios/sysbios.ae674 ...
    gmake[1]: Entering directory `C:/ti/mmw_dss_16xx/src/sysbios'
    cle674 C:/ti/bios_6_53_02_00/packages/ti/sysbios/BIOS.c ...
    asme674 C:/ti/bios_6_53_02_00/packages/ti/sysbios/family/c64p/Exception_asm.s64P ...
    asme674 C:/ti/bios_6_53_02_00/packages/ti/sysbios/family/c64p/Hwi_asm.s62 ...
    asme674 C:/ti/bios_6_53_02_00/packages/ti/sysbios/family/c64p/Hwi_asm_switch.s62 ...
    asme674 C:/ti/bios_6_53_02_00/packages/ti/sysbios/family/c64p/Hwi_disp_always.s64P ...
    asme674 C:/ti/bios_6_53_02_00/packages/ti/sysbios/rts/ti/tls_get_tp.asm ...
    asme674 C:/ti/bios_6_53_02_00/packages/ti/sysbios/family/c62/TaskSupport_asm.s62 ...
    are674 BIOS.obj c64p_Exception_asm.obj c64p_Hwi_asm.obj c64p_Hwi_asm_switch.obj c64p_Hwi_disp_always.obj ti_tls_get_tp.obj c62_TaskSupport_asm.obj ...
    gmake[1]: Leaving directory `C:/ti/mmw_dss_16xx/src/sysbios'
    Build of libraries done.
    cle674 package/cfg/dss_mmw_pe674.c ...
    'Finished building: "../dss_mmw.cfg"'

    'Building file: "../dss_data_

  • Shiyu, 

    1. If the error you are referring to is:  , this can be ignored.  This is not an issue.
    2. Ensure you have SDK 2.0.0.4 downloaded
    3. Always build DSS before MSS, which it looks like you have been doing.

    Please refer to the following thread on a similar issue if you have additional questions:

    https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1080367/iwr1642boost-trouble-in-demo-run

    Regards,

    Brennan