MMWAVE-STUDIO: Cannot connect to IWR1642 using MMWAVE demo in Chrome

Hi Kevin,

To start, please try the following:

Flash the board with the out-of-box demo. After flashing, disconnect the board from power and let it sit for 1 minute. Switch your SOP jumpers (only SOP0 is ON and SOP2 is now OFF).

Without hitting the reset button, reconnect the board to power and attempt to connect to the Demo Visualizer.

Good luck,

Allison

Hi Allison,

Thank you for the information.  Some clarifications before I try your suggestions:

1.  In the Chrome out-of-box demo, where is the flash function?  I don't see how to flash the board from the UI.

2.  Currently (without changing the SOP pins), it is currently configured (shipped from factory) as [2:0] == 001 (open, open, closed) which according to the manual is normal operation.  Just to make sure I'm following your instructions, do I switch [2] and [0] such that it becomes 100?  From the manual, that doesn't look like a valid SOP state, so I want to make sure I understand.

Thank you,

Kevin

Hi Kevin,

1. There is no flash option in the Demo Visualizer - you'll have to use Uniflash (https://dev.ti.com/uniflash/).

TI provides an out-of-box demo with the SDK. For the xWR16xx, you should download SDK 2.1. You can download the SDK here: http://www.ti.com/tool/MMWAVE-SDK

You can then use Uniflash to flash the pre-built binary (C:\ti\mmwave_sdk_02_01_00_04\packages\ti\demo\xwr16xx\mmw\xwr16xx_mmw_demo.bin).

2. For flashing mode, jumpers SOP0 and SOP2 are both ON [101].

After you successfully flash the device with Uniflash, you will need to power off the device and put it in functional mode to connect to the Demo Visualizer.

For functional mode, you will remove the jumper from header SOP2. Now, SOP0 will be the only header that is ON [001].

Good luck,

Allison

Hi Allison,

I reflashed the device (with the 2.01 LTS SDK) successfully.  Turned off the power, and re-did SOP [2] back to open.

Turned the device back on, refreshed the Demo Visualizer, confirmed the comm ports, and the results are the same (seems to connect to target 1, but fails to connect to target 2).

Note: The exact line on the browser console is COM5:115200, COM4:921600 connecting to 2 of 2 targets.  IWR16xx non-secure ES 0.200

For what it's worth, the UI does not allow me to select any SDK other than 3.2, even though the platform says xWR16xx.  Is that an issue?  What else can we try?

Hi Kevin,

At the bottom of the Demo Visualizer page, you should see a line that says:
"(*) For SDK 2.1 LTS release, please use this link: https://dev.ti.com/gallery/view/mmwave/mmWave_Demo_Visualizer/ver/2.1.0/"

Navigate to this link, which is the version of the Demo Visualizer that supports SDK 2.1. Now you should be able to change the SDK version to match your device.

Good luck,

Allison