IWR1642BOOST: Reading values from the Out of the Box Demo - "waiting for data..."

I forgot to mention that I also toggle the NRST after setting the Functional Mode.

Hello,

One thing that is happening, which might not be the root cause but you should change, is that you are using the visualizer for SDK 2.1 while the prebuilt binary in radar_toolbox_1_30_00_05 should be for SDK3.6. IWR1642 is the only device that is both on the very old SDK 2.1 as well as newer SDK 3.6. Please use the SDK 3.6 visualizer (https://dev.ti.com/gallery/view/mmwave/mmWave_Demo_Visualizer/ver/3.6.0/). I believe what is happening is the old visualizer is not sending a valid config as the device is expecting a newer format config, and thus the sensor never starts.

If this for whatever reason does not work, do a sanity check by downloading mmWave SDK 3.6, go to its demo folder and flash the binary as shown below. Set to functional , and then use a communications terminal program such as PuTTY or TeraTerm and see if you can send it cfg parameters (to COM5) such as the file profile_2d.cfg.

After sending it, you can connect to your data port (COM6) and see if you are getting any output.

Best Regards,

Pedrhom

Thank for your reply,

When I use the 3.6 Visualizer, I have additional information compare to the version 2.1, and now I can see it is connected on COM5 but it is not on COM6, it is waiting for data. (as shown on the picture) - Would you know why that is ?

I still don't have anything on the console or plots, and the readings on Wiresharks are the same as previously.

Regards,

Jason T.

I found the image "xwr16xx_mmw_demo" in the same directory, flashed it, put it back to functional mode, tried again on the Visualiser and the same thing happened...

Only COM5 is connected.

Regards,

Jason T.

Hello Jason,

Can you attempt to use the Industrial Visualizer within the Radar Toolbox's Tools folder in order to confirm if your device is functional? It most likely is and that the online browser visualizer is being finicky, but it would be good to confirm. Follow the user guide, run the visualizer from .exe or run from source via 'python gui_main.py'

https://dev.ti.com/tirex/explore/node?a=1AslXXD__1.30.00.05&node=A__AIlbDOGqFq4V48UOs4a93A__radar_toolbox__1AslXXD__1.30.00.05

Best Regards,

Pedrhom

I tried from the Industrial Visualizer provided in the link but it doesnt seem compatible with IWR1642 in the first place.

Also, there isn't any .cfg for the Out-of-Box Demo "C:\ti\radar_toolbox_1_30_00_05\source\ti\examples\Out_Of_Box_Demo"

I still tried to run it selecting the IWR1843 and IWR6843 which use 2 ports - and tried to upload aIWR1642 compatible demo from the list : "small obstacle detection".

I managed to get it connected but when I select the .cgf file in "C:\ti\radar_toolbox_1_30_00_05\source\ti\examples\Automotive_Body_Sensors\obstacle_detection\chirp_configs"

it says "No CFG file selected".... on the console.

Regards,

Jason T.

Hello Jason,

The lines in terminal that show "b''" usually means that the device is not properly set to functional mode after being flashed in flashing mode or in rarer cases a corrupted firmware. You have your device SOP switches set like the picture below after flashing, correct? 

You can also try using TeraTerm. From the Soft Reset Using CLI guide, follow only the steps involving TeraTerm in order to connect to the sensor and see if you can get "mmDemo:/>" to show up after connecting and hitting "enter" key a few times. This signifies the sensor is waiting for commands, such as the commands in a cfg file. In summary, does not matter what device and binary are used here, if a valid binary is flashed to a device and the device is set to functional then you SHOULD be able to at least confirm communicate with the device via this method.

https://dev.ti.com/tirex/explore/node?a=1AslXXD__1.30.00.05&node=A__ANH6D6HtFwFeTI77T-jkbA__radar_toolbox__1AslXXD__1.30.00.05

Best Regards,

Pedrhom

Hi Pedrhom,

I had indeed the board set to functional mode after being flashed like in the picture you sent. 

I tried using TeraTerm and I again don't get anything... 

What's in red is when i apply the new settings and what's in green is when i press the "enter" key. I pressed a couple of times and I still have anything on the TeraTerm Instance. 

I have been doing it under Functional Mode.

Best Regards,

Jason T.

Hello Jason,

The only other possible reason is due to an under powered or malfunctioning power supply. On TI.com we specify a bare minimum of 5V 2.5A but I suggest purchasing a 5V 3A just in case. What power supply are you using?

Best Regards,

Pedrhom

Hi Pedrhom,

I am currently using a 5V 2A power supply, I've ordered a 3A power supply and it should arrive by Monday.

Thanks,

Regards,

Jason T.

Hello Jason,

Understood, if you need more help feel free to respond here.

Best Regards,

Pedrhom

Hi Pedrhom,

Sorry for the delay, the Power supply took days to be delivered.

I have tested all the different methods you suggested with a 5V 3A Power supply without any success... except for the Industrial Visualiser where the results changed. (picture)

It is still not working but i get more messages. "No cfg file selected" is still mentioned.

When i click on "Start and Send Configuration" the radar is on Funtional Mode.

I still don't have anything on the TeraTerm instances or the cloud Visualiser 3.6 (only COM5 - User UART is indicated Connected).

I tried on different USB ports without any sucess.

Regards,

Jason T.

Hello Jason,

Can you take a picture of your 1642? And where did you get this EVM from? Was it the TI store? At this point you have done everything correctly. With it in functional mode you should be getting some communication. As stated before, in the Industrial Visualizer receieving a b'' is essentially no response and TeraTerm you should be able to get mmDemo:/> to show up.

The only last thing I can think of outside of a faulty EVM is having a very old ES1 version of 1642, if so you could try flashing the 1642 binary found in the MMWAVE 02_01_00_04 SDK. After installation youll find the .bin at C:\ti\mmwave_sdk_02_01_00_04\packages\ti\demo\xwr16xx\mmw

For your convenience that specific version SDK can be found here: https://www.ti.com/tool/download/MMWAVE-SDK/02.01.00.04

Best Regards,

Pedrhom

I didn't buy the radar myself but I believe it was bought from the TI Store.

Hello,

Looking up the markings on the EVM, this device is very old. It was made over 7 years ago and could be a leading reason to it not functioning. I would attempt using MMWAVE 02_01_00_04 SDK and if that does not work then I will deem this device as malfunctioning

Best Regards,

Pedrhom