AWR6843AOPEVM: using mmwaveboost board after reflasing out of box errors

ok i'm using debian 11 on an old (legacy) laptop so i cant install ubuntu .. anything current but i will try and make the ros driver .. from source and see if it helps

Hey Adrian,

Just a heads up, most of our engineers will be out until July 8th due to a United States holiday. If you have any updates or questions, please hold off on replying until next week when we can respond to you then.

Additionally, keep in mind that you might not need to build the ROS driver depending on your end application. I pointed to that user guide since it has relevant information for Linux distros. I might be able to provide better application specific resources if you have an idea in mind for your end application.

Regards,

Kristien

i just want to be able to run the same demo for fals detection as the video at the moment

Hi Adrian, Please allow us until next week to respond.

Regards,

Tim

i just want to know if the usb bus resetting whilts data is supposed to be streeming out to the python code is normal on linux systems ?

Hey Adrian,

The USB bus resetting while data is streaming is not normal. I didn't catch it earlier, but if you are using an MMWAVEICBOOST, this is likely causing issues with the USB connection when running in Linux. Unless you need to debug the device in CCS, I would recommend disconnecting the MMWAVEICBOOST and only connecting the AWR6843AOP to your PC by itself. The board should then be recognized as a ttyUSB device of some iteration.

The MMWAVEICBOOST may also explain why ttyACM0 and ttyACM1 appears twice in your grep, though that might just be from running multiple visualizer instances. Speaking of which, what comport visualizer are you referencing here?

Regards,

Kristien

its the python one in the radar toolbox main_gui.py  under aplication visualisers industrail visualisers

i've wasted 6 days chasing my tail i'm going to take the unit off the MMWAVEICBOOST board and try it later today if that fixes my problem .. and the damn gui works all good otherwise i might as well throw it in the bin i dont have time to play i need a working demo that someone who know what they are doing can do somthing with .. 

Hey Adrian,

I understand your frustration here regarding this issue, and I will try my best to resolve it, but please abide by the E2E guidelines and general forum etiquette - i.e., be courteous.

For the industrial visualizer from Radar Toolbox versions at or above 2.XX.XX.XX, you will need to specify the full path of the USB ports. Without the MMWAVEICBOOST, the ports should be: /dev/ttyUSB0 and /dev/ttyUSB1. For Radar Toolbox versions prior to 2.XX.XX.XX, specifying the port path was not possible as the visualizer only supported Windows OS. Note: we are working towards improving Linux support for our devices, but there will be issues, so posts like this help us understand what gaps exist. 

Additionally, if you are trying to connect multiple visualizer instances to one device, that will fail, as only one visualizer can hold the USB ports at a time. If you are trying to connect multiple visualizers to multiple devices, that should work, but they will likely slow down according to how many devices and visualizers you have running.

Regards,

Kristien

i appologise for my strong language im australian .. and my natual language does not translate well to polite folk who dont know me .. however /dev/ttyUSB0 and /ttyUSB1 which is what maps acordeinf to /dev/serial/devby-id ... to silicon labds dual .... does not send data to the main_gui.py app prthon 3 ahs lots of complaints .. about no data. perhaps my switches are now wrong as the mmwboost bourd is not in the equation

Hey Adrian,

Its all good! I'm glad you explained your situation. You are right about having to change the board settings when removing the MMWAVEICBOOST. You'll have to set the board switches as shown in the image below and also ensure the flashing switch on the back is set to OFF. If you ever need to check switch settings for flashing and functional modes, I would recommend checking out the EVM Setup Operational Modes guide from the Radar Toolbox. 

I also confirmed on my end that attempting to run the visualizer without changing the switches from the settings used for the MMWAVEICBOOST will cause the visualizer to complain about no data. Changing the switch settings to the above allowed me to get visualizer data.

Additionally, you can uncomment the print statement on line 107 of parseFrame.py found under <RTB_INSTALL_DIR>/tools/visualizers/Applications_Visualizer/common/ and then run the Python visualizer, gui_main.py, from source to see what TLVs the visualizer is receiving. 

Lastly, I just wanted to confirm again that you are not using a Radar Toolbox version below 2.00.00.06, correct? If you are, please download the latest Radar Toolbox version which does support Linux.

Regards,

Kristien

radar_toolbox_2_10_00_04

still crashing  ...  will uncomment line 107

python3 gui_main.py
QSocketNotifier: Can only be used with threads started with QThread
INFO [gui_parser.py:226] Connected
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
b''
Killed
abartlett@Latitude-E5520:~/ti/radar_toolbox_2_10_00_04/tools/visualizers/Applications_Visualizer/Industrial_Visualizer$

abartlett@Latitude-E5520:~/ti/radar_toolbox_2_10_00_04/tools/visualizers/Applications_Visualizer/Industrial_Visualizer$ python3 gui_main.py
QSocketNotifier: Can only be used with threads started with QThread
INFO [gui_parser.py:226] Connected
b'\tsensorStop\n'
b"'\tsensorStop' is not recognized as a CLI command\n"
b'\rmmwDemo:/>flushCfg\n'
b'Done\n'
b'\rmmwDemo:/>dfeDataOutputMode 1\n'
b'Done\n'
b'\rmmwDemo:/>channelCfg 15 7 0\n'
b'Done\n'
b'\rmmwDemo:/>adcCfg 2 1\n'
b'Done\n'
b'\rmmwDemo:/>adcbufCfg -1 0 1 1 1\n'
b'Done\n'
b'\rmmwDemo:/>lowPower 0 0\n'
b'Done\n'
b'\rmmwDemo:/>profileCfg 0 60.75 30.00 25.00 59.10 657930 0 54.71 1 96 2950.00 2 1 36 \n'
b'Done\n'
b'\rmmwDemo:/>chirpCfg 0 0 0 0 0 0 0 1\n'
b'Done\n'
b'\rmmwDemo:/>chirpCfg 1 1 0 0 0 0 0 2\n'
b'Done\n'
b'\rmmwDemo:/>chirpCfg 2 2 0 0 0 0 0 4\n'
b'Done\n'
b'\rmmwDemo:/>frameCfg 0 2 96 0 55.00 1 0\n'
b'Done\n'
b'\rmmwDemo:/>dynamicRACfarCfg -1 4 4 2 2 8 12 4 8 5.00 8.00 0.40 1 1\n'
b"'dynamicRACfarCfg' is not recognized as a CLI command\n"
b'\rmmwDemo:/>staticRACfarCfg -1 6 2 2 2 8 8 6 4 8.00 15.00 0.30 0 0\n'
b"'staticRACfarCfg' is not recognized as a CLI command\n"
b'\rmmwDemo:/>dynamicRangeAngleCfg -1 0.75 0.0010 1 0\n'
b"'dynamicRangeAngleCfg' is not recognized as a CLI command\n"
b'\rmmwDemo:/>dynamic2DAngleCfg -1 1.5 0.0300 1 0 1 0.30 0.85 8.00\n'
b"'dynamic2DAngleCfg' is not recognized as a CLI command\n"
b'\rmmwDemo:/>staticRangeAngleCfg -1 0 8 8\n'
b"'staticRangeAngleCfg' is not recognized as a CLI command\n"
b'\rmmwDemo:/>antGeometry0 0 -1 -2 -3 -2 -3 -4 -5 -4 -5 -6 -7\n'
b"'antGeometry0' is not recognized as a CLI command\n"
b'\rmmwDemo:/>antGeometry1 -1 -1 -1 -1 0 0 0 0 -1 -1 -1 -1\n'
b"'antGeometry1' is not recognized as a CLI command\n"
b'\rmmwDemo:/>antPhaseRot 1 1 1 1 1 1 1 1 1 1 1 1\n'
b"'antPhaseRot' is not recognized as a CLI command\n"
b'\rmmwDemo:/>fovCfg -1 70.0 20.0\n'
b"'fovCfg' is not recognized as a CLI command\n"
b'\rmmwDemo:/>compRangeBiasAndRxChanPhase 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0\n'
b'Done\n'
b'\rmmwDemo:/>staticBoundaryBox -3 3 2 6 0 3\n'
b"'staticBoundaryBox' is not recognized as a CLI command\n"
b'\rmmwDemo:/>boundaryBox -4 4 0.5 5.5 0 3\n'
b"'boundaryBox' is not recognized as a CLI command\n"
b'\rmmwDemo:/>sensorPosition 2 0 15\n'
b"'sensorPosition' is not recognized as a CLI command\n"
b'\rmmwDemo:/>gatingParam 3 2 2 2 4\n'
b"'gatingParam' is not recognized as a CLI command\n"
b'\rmmwDemo:/>stateParam 3 3 6 500 50 6000\n'
b"'stateParam' is not recognized as a CLI command\n"
b'\rmmwDemo:/>allocationParam 40 100 0.1 20 0.5 20\n'
b"'allocationParam' is not recognized as a CLI command\n"
b'\rmmwDemo:/>maxAcceleration 0.1 0.1 0.1\n'
b"'maxAcceleration' is not recognized as a CLI command\n"
b'\rmmwDemo:/>trackingCfg 1 2 800 30 46 96 55\n'
b"'trackingCfg' is not recognized as a CLI command\n"
b'\rmmwDemo:/>sensorStart\n'
b'Error: Full configuration must be provided before sensor can be started the first time\n'
ERROR [gui_parser.py:67] ERROR: No data detected on COM Port, read timed out
ERROR [gui_parser.py:68] Be sure that the device is in the proper mode, and that the cfg you are sending is valid
ERROR [gui_parser.py:67] ERROR: No data detected on COM Port, read timed out
ERROR [gui_parser.py:68] Be sure that the device is in the proper mode, and that the cfg you are sending is valid
ERROR [gui_parser.py:67] ERROR: No data detected on COM Port, read timed out
ERROR [gui_parser.py:68] Be sure that the device is in the proper mode, and that the cfg you are sending is valid
ERROR [gui_parser.py:67] ERROR: No data detected on COM Port, read timed out
ERROR [gui_parser.py:68] Be sure that the device is in the proper mode, and that the cfg you are sending is valid

Hey Adrian,

There are a few other CLI commands that are missing as mentioned in the error right before the data detection error. You will need the following CLI commands:

• guiMonitor
• cfarCfg (two commands: one for CFAR detection in range direction, one for CFAR in doppler direction)
• multiObjBeamForming
• calibDcRangeSig
• clutterRemoval
• measureRangeBiasAndRxChanPhase
• aoaFovCfg
• cfarFovCfg (two commands: one for point filter in range direction, one for point filtering in doppler direction)
• extendedMaxVelocity
• CQRxSatMonitor
• CQSigImgMonitor
• analogMonitor
• lvdsStreamCfg
• bpmCfg (NOTE: This is only mandatory for demos that use doppler DSP DPU such as the OOB demo for xwr16xx and xwr68xx. It will be ignored otherwise)
• calibData

You can also use the provided configuration below which is taken from the profiles folder of the MMWAVE SDK (<MMWAVE_SDK_INSTALL_DIR>/pacakges/ti/demo/xwr68xx/mmw/profiles/).

% Carrier frequency     GHz                          60
% Ramp Slope    MHz/us                               166
% Num ADC Samples                                    256
% ADC Sampling Rate Msps                             12.5
% ADC Collection Time   us                           20.48
% Extra ramp time required (start time) us           3
% Chirp time (end time - start time)    us           21
% Chirp duration (end time) us                       24
% Sweep BW (useful) MHz                              3399.68
% Total BW  MHz                                      3984
% Max beat freq (80% of ADC sampling rate)  MHz      10
% Max distance (80%)    m                            9.04
% Range resolution  m                                0.044
% Range resolution (meter per 1D-FFT bin)   m/bin    0.044
%                                                    
% Inter-chirp duration  us                           7
% Number of chirp intervals in frame    -            64
% Number of TX (TDM MIMO)                            2
% Number of Tx elevation antennas                    0
% Number of RX channels -                            4
% Max umambiguous relative velocity kmph             72.58
%   mileph                                           45.36
% Max extended relative velocity    kmph             145.16
%   mileph                                           90.73
% Frame time (total)    ms                           1.984
% Frame time (active)   ms                           1.536
% Range FFT size    -                                256
% Doppler FFT size  -                                32
% Radar data memory required    KB                   272
% Velocity resolution   m/s                          1.26
% Velocity resolution (m/s per 2D-FFT bin)  m/s/bin  1.26
% Velocity Maximum  m/s                              20.16
% Extended Maximum Velocity m/s                      40.32
% Maximum sweep accorss range bins  range bin        0.91
% 
sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 7 0
adcCfg 2 1
adcbufCfg -1 0 1 1 1
lowPower 0 0
profileCfg 0 60 7 3 24 0 0 166 1 256 12500 0 0 158
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 4
chirpCfg 2 2 0 0 0 0 0 2
frameCfg 0 2 32 0 100 1 0
guiMonitor -1 1 1 1 0 0 1
cfarCfg -1 0 2 8 4 3 0 15.0 0
cfarCfg -1 1 0 4 2 3 1 15.0 0
multiObjBeamForming -1 1 0.5
calibDcRangeSig -1 0 -5 8 256
clutterRemoval -1 0

compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
measureRangeBiasAndRxChanPhase 0 1. 0.2

aoaFovCfg -1 -90 90 -90 90
cfarFovCfg -1 0 0.25 9.0
cfarFovCfg -1 1 -20.16 20.16
extendedMaxVelocity -1 0

CQRxSatMonitor 0 3 4 63 0
CQSigImgMonitor 0 127 4
analogMonitor 0 0
lvdsStreamCfg -1 0 0 0
bpmCfg -1 0 0 0
calibData 0 0 0
sensorStart

0121.profile_3d.cfg

Regards,

Kristien

where do i get thes CLI commands from ?

Hey Adrian,

You can find all the CLI commands under Section 3.4 of the MMWAVE SDK User Guide (<MMWAVE_SDK_INSTALL_DIR>/docs/mmwave_sdk_user_guide.pdf). You can download the latest version of the MMWAVE SDK (03.06.02.00-LTS) from the link below.

https://www.ti.com/tool/download/MMWAVE-SDK

Mandatory commands are noted under the "Command details" column of the table CLI commands table.

Regards,

Kristien

abartlett@Latitude-E5520:~/Downloads$ sudo bash mmwave_sdk_03_06_02_00-LTS-Linux-x86-Install.bin
mmwave_sdk_03_06_02_00-LTS-Linux-x86-Install.bin: mmwave_sdk_03_06_02_00-LTS-Linux-x86-Install.bin: cannot execute binary file
abartlett@Latitude-E5520:~/Downloads$ su
Password:
su: Authentication failure
abartlett@Latitude-E5520:~/Downloads$ su
Password:
su: Authentication failure
abartlett@Latitude-E5520:~/Downloads$ sudo bash
root@Latitude-E5520:/home/abartlett/Downloads# bash ./mmwave_sdk_03_06_02_00-LTS-Linux-x86-Install.bin
./mmwave_sdk_03_06_02_00-LTS-Linux-x86-Install.bin: ./mmwave_sdk_03_06_02_00-LTS-Linux-x86-Install.bin: cannot execute binary file
root@Latitude-E5520:/home/abartlett/Downloads#

Hey Adrian,

You can execute the SDK installer by first executing the chmod command then bash.

chmod +x mmwave_sdk_03_06_02_00-LTS-Linux-x86-Install.bin 

./mmwave_sdk_03_06_02_00-LTS-Linux-x86-Install.bin 

Regards,

Kristien

yes i did that it will not run .. the md5 sum matches .. its not permissions ... if its a self extracting zip file then i need to jnow which application language is missing to unpack it  for example if it needs 7zip installed i'll have to install that first 

ubuntu server to get https://packages.ubuntu.com/focal/amd64/libtinfo5/download which is required to instal ccstudio is down so i'm stumped at the moment .. i presume i need to reflash my device if the terminal has no prompt