CCS/IWR6843ISK: Error in running the people counting demos for IWR6843

Hi Amin,

This error appears when there is an issue with the java module that is used to open the COM Ports in Matlab.  This usually appears when something has the port in a bugged state.  Usually a power cycle can fix this issue.

Regards,

Justin

Hi Justin,

Thanks for your suggestion. I rebooted my laptop and power cycled IWR6843ISK. I flashed the firmware for lab15 again.

and removed the SOP2 and reset the board again. However, when I run  pplcount_gui.exe I am getting the same error, It is interesting that I do not get this error with .exe of lab11 for IWR1642? what is the difference? They are both MATLAB compiled exe, isn't it? what is the difference?

I am not sure if you know I had a physical problem with my board that I connected wrong power supply initially and as part of that the zener diode 1 on the carrier board was gone.

Charles suggested me to connect the 5V power supply to pin1 of P3, which helped me to switch on the board and flash the firmware.

Having said that for IWR6843 when I flashed the firmware today, for the first time, the laoding image process in Uniflash was stuck and then I cancelled it and redo it again.

Do you think it is HW or SW issue? Any suggestion for more investigation?

Undefined variable "matlab" or class "matlab.webcam.internal.Utility.enumerateWebcams".

Error in webcamlist (line 25)

Error in setup>popupWebcam_CreateFcn (line 612)

Error in gui_mainfcn (line 95)

Error in setup (line 42)

Error in matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)setup('popupWebcam_CreateFcn',hObject,eventdata,guidata(hObject))

hObject =

UIControl (editUART) with properties:

Style: 'edit'
String: 'COM8'
BackgroundColor: [1 1 1]
Callback: [function_handle]
Value: 0
Position: [0.3046 0.7262 0.2831 0.2857]
Units: 'normalized'

Use GET to show all properties

Opening configuration file mmw_pplcount_demo_default.cfg ...
trackingCfg specifies -6.981317e-01.
GUI specifies 0. 90 will be used for azimuth in cfg.
Sending configuration from mmw_pplcount_demo_default.cfg file to IWR16xx ...

Serial Port Object : Serial-COM8

Communication Settings
Port: COM8
BaudRate: 115200
Terminator: 'LF'

Communication State
Status: open
RecordStatus: off

Read/Write State
TransferStatus: idle
BytesAvailable: 0
ValuesReceived: 0
ValuesSent: 0

flushCfg
dfeDataOutputMode 1
channelCfg 15 5 0
adcCfg 2 1
adcbufCfg 0 1 1 1
profileCfg 0 60.6 30 10 62 0 0 53 1 128 2500 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 4
frameCfg 0 1 128 0 50 1 0
lowPower 0 1
guiMonitor 1 1 0 0
cfarCfg 6 4 4 4 4 16 16 4 4 50 62 0
doaCfg 600 1875 30 1 1 0
SceneryParam -6 6 0.5 6
GatingParam 4 3 2 0
StateParam 10 5 100 100 5
AllocationParam 250 250 0.25 10 1 2
AccelerationParam 1 1 1
trackingCfg 1 2 250 20 52 82 50 90
sensorStart
Error 0x16 at ../src/termios.c(512): The device does not recognize the command.Error 0x16 at ../src/termios.c(2723): The device does not recognize the commandError 0x16 at ../src/termios.c(512):

Hi Amin,

To ensure that there are no hardware issues, can you flash the device with the OOB demo? This will remove the possibility of issues with the People Counting lab.

Regards,
Justin

Hi Justin,

Thanks for your support. Based on your suggestion I run the OOB the demo.
I put the screenshot in the other thread I have with Charles:
e2e.ti.com/.../2894011
Could you please have a look and see if it the board is OK and not faulty?
I can send the screenshots to you directly or capture a video from desktop if it helps?

Many thanks
Amin

Hi Amin,

From the screenshot, it appears that the OOB demo is working.   We have seen this issue before in a similar thread.  The user had to try different power supplies to get the device to run properly. 

Are you using a 5v 3 A power supply?  Often we see issues with users who are using a 5V 2.5A power supply.

Regards,

Justin

Hi Justin,

Thanks for your help.

Yes, I am using a power supply which I can adjust the voltage to 5V and the power supply shows both the current and voltage reading. It is interesting that the board only takes 300mA from power supply?!

What do you think? Regarding the Java related problem in MATLAB which you were suggesting that it would cause problem for com port, is it only related to demo for IWR6843 or it is also related to IWR1642?

Thanks

Amin

Hi Amin,

The board should draw about 300 mA before it is configured.

I think your hardware may be damaged, as it appears that the Matlab Serial Port reader is not understanding the data that is sent back from the device on the MSS LOGGER UART (Control UART seems to be fine). I am pulling in a hardware expert.

Regards,
Justin

Hi Justin,

Today, I checked my JRE installation and noticed that it was broken. I fixed it by adding a reginstry key in windows. After that I tested the demo for people counting and it was not throwing that error "Error 0x16 at ../src/termios.c(512): The device does not recognize the command."

I also noticed the cuurent consumption on power supply and it was only 300 mA.

Therefore, in order to test the demo if actually track people, I get longer power cable and mount on 2m tripod mount as I was using for IWR1642.

Surprisingly, after powering up, the problem "Error 0x16 at ../src/termios.c(512): The device does not recognize the command." occured again.

I put the OOB demo again and everything was fine and then I put the firmware back on again, the problem was there.

I rebooted my laptop and power cycled the board but the problem with com port is there.

I do not think the board is damaged as I saw the demo running once this morning and OOB was running?!

Is the GUI of people counting demo for IWR1642 different from that of on IWR6843 in terms of usage of comport ?
What do you think about the whole the situation?

Thanks
Amin

Hi Amin,

The visualizer for the 1642 and 6843 People Counting demos are the same.

You saw that the demo was working with the short power cable connected directly to the supply. when the power cable is lengthened, the device does not work. Did you change the micro-usb cable as well?

Can you check and see if the above is reproducable? I.e., will the device always work with the shorter power cable and always fail with the longer power cable?

Regards,
Justin

Hi Justin,

I tested the board with short power cable and micro usb cable to see if it is working, but it is throwing the same error "Error 0x16 at ../src/termios.c(512): The device does not recognize the command."

I then flashed the OOB SDK demo and it works. When I move my hand toward the antenna the heatmaps are changing.

Attached is the recording from visualizer demo.

Please let me know about your thoughts

Thanks

Amin

Also it only takes 300mA current. Thanks

Hi Amin,

With the OOB demo flashed, please try to run lab0021 - this is a different visualizer for the OOB demo that is based in Matlab. Since there is an issue with the interaction between the Matlab serial port function in People Counting and your board, it should appear in this visualizer as well.

Regards,
Justin

Hi Justin,

Thanks for suggetsing the demo. Per you sugguestion, I first tried this GUI of lab21 with OOB demo firmware flashed already and it connected to board but obviously no points detected.

Then I flashed the firmware of lab21 

C:\ti\mmwave_industrial_toolbox_3_1_1\labs\lab0021_area_scanner_68xx\prebuilt_binaries\area_scanner_68xx_lab.bin

and I ran the GUI of lab21 area scanner and it seems to be working as shown in the attached video to this reply. BTW, it is only taking 360 mA from power supply.

 What is your thought?

Thanks

Amin

Hi Amin,

I need another day on this. When running people counting, does the device send back any data after sensor start? You can connect tera term to the data COM Port to determine if anything is coming back.

To answer your question about current draw - 360 mA * 5 V is 1.8 W, which is about the power draw we expect with the device. If you monitor the current at a higher resolution time scale, you will see that there are point of high current draw when the device is actively chirping, and points of very low current draw when the device is mostly idle.

Regards,
Justin

Hi Justin,

I flashed the firmware for lab 15, removed the jumper SO2 and reset board.

Then I ran the GUI pplcount_gui.exe, after it is connected I started the application. As expected in the command line behind the GUI, I was receiving the error and after a few seconds due to this error the GUI crashes and it always happens when this error occurs. Then I opened the Teram tem on com port  for data port and baudrate 65536 as it is mentioned in MATLAB code.

But I do not receive anything in tera term. I am not able to open tera term before the GUI crashes as it cashes very quickly. and if I open tera before that GUI can not open the port.

Please let me know if this was the experiment you meant me to do?

Thanks

Amin

Hi Amin,

Please ensure that you have installed the latest update for the Matlab runtime.

Please ensure that the GUI .exe file you have is 1214 KB.

Regards,

Justin

Hi Justin,

I have installed MATLAB run time 9.2 and I installed the update for run time.

I also checked the size of GUI in people counting lab 15 and lab 19:

The size of both are 943893 bytes

C:\ti\mmwave_industrial_toolbox_3_1_1\labs\lab0015_pplcount_68xx\quickstart

pplcount_gui.exe

943,893 bytes

C:\ti\mmwave_industrial_toolbox_3_1_1\labs\lab0019_pplcount_long_range_68xx\quickstart

pplcount_gui.exe
943,893 bytes

is this what you meant and is correct?

Thanks

Amin

HI Justin,

I did a comparison between lab11 people counting for IWR1642 and lab 15 and lab 19 people counting IWR6843.

C:\ti\mmwave_industrial_toolbox_3_1_1\labs\lab0011-pplcount\lab0011_pplcount_gui

C:\ti\mmwave_industrial_toolbox_3_1_1\labs\lab0015_pplcount_68xx\gui

C:\ti\mmwave_industrial_toolbox_3_1_1\labs\lab0019_pplcount_long_range_68xx\gui

It seems that there is no difference between MATLAB source code for the GUI of people counting of these demos? is that correct?

Thanks,

Amin