Other Parts Discussed in Thread: IWR1443,
Dears：
Many thanks for your suggestions, and I tested it according your requirement.
You can see the below information and it could not test OK, and the other board(IWR1443) is OK.
And the customer just got the IWR1642BOOST, could we confirm the board have some HW issues?
1. the first picture
2. Then there are some Num on the GUI, however, the Num is not changed if there is other people.
3. After a long time there will happen the below picture:
Then I copied the Log as follows:
QT version = 5.9.1 QMetaObject::connectSlotsByName: No matching signal for on_buttonBox_accepted() Serial Port Found Data Port Number is "COM4" User Port Number is "COM3" Data port succesfully Open User port succesfully Open QWindowsWindow::setGeometry: Unable to set geometry 1485x999+8+31 on QWidgetWindow/'MainWindowWindow'. Resulting geometry: 1370x749+8+31 (frame: 8, 31, 8, 8, custom margin: 0, 0, 0, 0, minimum size: 1347x720, maximum size: 16777215x16777215). Configuration File Name Read from the GUI is %s/n "xwr1642_profile_VitalSigns_20fps_Back.cfg" QMetaObject::connectSlotsByName: No matching signal for on_buttonBox_accepted() "COM3" Configuration File Path is %s/n "D:/03. TI/mmWave/mmwave_automotive_toolbox_2_4_3/labs/lab0001-driver-vital-signs/vitalSigns_host/profiles/xwr1642_profile_VitalSigns_20fps_Front.cfg" "sensorStop" "flushCfg" "dfeDataOutputMode 1" "channelCfg 15 3 0" "adcCfg 2 1" "adcbufCfg -1 0 0 1 0" "profileCfg 0 77 7 6 57 0 0 70 1 200 4000 0 0 48" "chirpCfg 0 0 0 0 0 0 0 1" "frameCfg 0 0 2 0 50 1 0" "lowPower 0 1" "guiMonitor 0 0 0 0 1" "calibDcRangeSig -1 0 0 0 0" "vitalSignsCfg 0.3 0.9 256 512 4 0.1 0.05 100000 300000" "motionDetection 1 20 2.0 0" "sensorStart" "" "sensorStop" "flushCfg" "dfeDataOutputMode 1" "channelCfg 15 3 0" "adcCfg 2 1" "adcbufCfg -1 0 0 1 0" "profileCfg 0 77 7 6 57 0 0 70 1 200 4000 0 0 48" "chirpCfg 0 0 0 0 0 0 0 1" "frameCfg 0 0 2 0 50 1 0" "lowPower 0 1" "guiMonitor 0 0 0 0 1" "calibDcRangeSig -1 0 0 0 0" "vitalSignsCfg 0.3 0.9 256 512 4 0.1 0.05 100000 300000" 0.3 0.9 4 "motionDetection 1 20 2.0 0" "sensorStart" "" Chirp Duration in us is : 50 Chirp Bandwidth in kHz is : 3500 Maximum Range in Meters is : 8.57143 Range-FFT size is : 256 Range-Bin size is : 0.0334821 Range-Bin Start Index is : 8 Range-Bin End Index is : 26 Total Payload size from the UART is : 260 Padding Factor is : 9 Total Payload size from the UART is : 288 Frame Number is 1 Frame Number is 2 Frame Number is 3 Frame Number is 4 Frame Number is 5 Frame Number is 6 Frame Number is 7 Frame Number is 8 Frame Number is 9 Frame Number is 10 Frame Number is 11 Frame Number is 12 Frame Number is 13 Frame Number is 14 Frame Number is 15 Frame Number is 16 Frame Number is 17 Frame Number is 18 Frame Number is 19 Frame Number is 20 Frame Number is 21 Frame Number is 22 Frame Number is 23 Frame Number is 24 Frame Number is 25 Frame Number is 26 Frame Number is 27 Frame Number is 28 Frame Number is 29 Frame Number is 30 Frame Number is 31 Frame Number is 32 Frame Number is 33 Frame Number is 34 Frame Number is 35 Frame Number is 36 Frame Number is 37 Frame Number is 38 Frame Number is 39 Frame Number is 40 Frame Number is 41 Frame Number is 42 Frame Number is 43 Frame Number is 44 Frame Number is 45 Frame Number is 46 Frame Number is 47 Data size is not OK --- local Count: 27 DataBufferSize 0 258 Frame Number is 50 Frame Number is 51 Frame Number is 52 Frame Number is 53 Frame Number is 54 Frame Number is 55 Frame Number is 56 Frame Number is 57 Frame Number is 58 Frame Number is 59 Frame Number is 60
From these information, could we confirm the board have HW issues?
Or you can give me new Demo and I can test it again.
