• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 29 subscribers
  • Views 455 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AWR1642BOOST-ODS: Issue Getting Obstacle Detection Demo GUI Working

Denis Nakazawa
Prodigy 100 points
Part Number: AWR1642BOOST-ODS
Other Parts Discussed in Thread: UNIFLASH, , AWR1642

Hello, 

I'm trying to run the obstacle detection demo on the AWR1642BOOST-ODS and first approached it by flashing the pre-existing binaries onto the board using UniFlash. I then started up the GUI using the executable and was brought to the main interface - so far so good. I disconnected the jumper on SOP2, power-cycled the board, then proceeded to put in the appropriate UART and DATA ports and connected to the GUI. I then selected the default config file for the obstacle detection demo. My problems begin when I hit the "Load" button. The terminal for the visualizer prints out the commands in the config file and then beings to spout error codes after the sensorStart command. See the transcription of the terminal text below:

Sending configuration from C:\ti\mmwave_automotive_toolbox_3_6_0\labs\lab0004_obstacle_detection\chirp_configs\ods_default_config.cfg file to IWR16xx ...
sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 3 0
adcCfg 2 1
adcbufCfg -1 0 0 1 1
profileCfg 0 77 7 7 58.0 0 0 67.978 1 256 5020 0 0 36
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
frameCfg 0 1 32 0 100 1 0
lowPower 0 1
guiMonitor 1 1 0 0
cfarCfg 1 4 12 4 2 8 2 350 30 2 0 5 20
dbscanCfg 4 4 13 20 3 256
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): The device does not recognize the command.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(2723): The device does not recognize the commandError 0x16 at ../src/termios.c(512): The device does not recognize the command.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(2723): The device does not recognize the commandError 0x16 at ../src/termios.c(512): The device does not recognize the command.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(2723): The device does not recognize the commandError 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): 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): The device does not recognize the command.Error 0x16 at ../src/termios.c(2723): The device does not rhttps://e2e.ti.com/tinymce//apis/embeddables/configure?typeId=dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2&id=undefined#

This error continues infinitely until I kill the GUI. 

Would anyone please be able to suggest what might be going (or I might be doing) wrong here?

Thanks in advance!

UPDATE:

I tried running the demo using the debug method and got it all the way up to the part where the guide tells you to start the GUI. The same problem occurs from when I used the pre-built binaries. However, this time there is a message in the CCS console that states that:

c674x_0: power failure on target cpu

c674x_0: failed to remove the debug state from the target before disconnecting. there may still be breakpoint op-codes embedded in program memory. it is recommended that you reset the emulator before you connect and reload your program before you continue debugging

This occurs at the same moment that I observe those error codes in the visualizer terminal. Another interesting thing is that the EVM seems to be getting the initial few commands from the GUI because there are messages in the console that report the sensor being stopped and then started. 

Hopefully, this may help shed some additional light on what may be going on.

  • 0 in reply to Cesar
    Prodigy 100 points

    Hi Cesar, 

    Thank you for your reply. 

    Unfortunately, I had already taken a look at this forum thread before posting my own topic. A lot of it isn't reproducible for me since I don't have the IWR EVM that they use and I've already tried running a few different labs on the AWR1642 I have on me. The OOB demo worked and multi-gesture demo worked. I tried the short range radar, but the GUI did not show that it was detecting any objects. 

    My original problem still persists. 

    Sincerely, 

    Denis

  • 0 in reply to Denis Nakazawa
    TI__Guru*** 149044 points

    Hi,

    Could you try the following:

    1) flash the pre-built binaries

    2) Start a serial emulator such as Tera Term

    3) Configure at the correct speed the User COM port

    4) Copy and past the commands from the cfg file to the serial terminal

    Let's see if this works

    Thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 100 points

    Hi Cesar, thanks for your reply. 

    I followed the steps you described and have the following terminal (I'm using PuTTY) output:

    ******************************************
xWR16xx MMW Demo 02.00.00.04
******************************************
mmwDemo:/>sensorStop
Done
mmwDemo:/>flushCfg
Done
mmwDemo:/>dfeDataOutputMode 1
Done
mmwDemo:/>channelCfg 15 3 0
Done
mmwDemo:/>adcCfg 2 1
Done
mmwDemo:/>adcbufCfg -1 0 0 1 1
Done
mmwDemo:/>profileCfg 0 77 7 7 58.0 0 0 67.978 1 256 5020 0 0 36
Done
mmwDemo:/>chirpCfg 0 0 0 0 0 0 0 1
Done
mmwDemo:/>chirpCfg 1 1 0 0 0 0 0 2
Done
mmwDemo:/>frameCfg 0 1 32 0 100 1 0
Done
mmwDemo:/>lowPower 0 1
Done
mmwDemo:/>guiMonitor 1 1 0 0
Done
mmwDemo:/>cfarCfg 1 4 12 4 2 8 2 350 30 2 0 5 20
Done
mmwDemo:/>dbscanCfg 4 4 13 20 3 256
Done
mmwDemo:/>sensorStart
Debug: Init Calibration Status = 0x7fe
Done
mmwDemo:/>

    However, right after I send the sensorStart command, I can hear the computer make the sound indicating the disconnect of a USB device and PuTTY throws an error stating that the serial device has been removed. There seems to be some sort of issue with starting up the sensor on the board. 

    Do you know what might cause this sort of problem? 

    Thanks in advance!

    - Denis

  • +1 in reply to Denis Nakazawa
    TI__Guru*** 149044 points

    I have seen sometimes problems when the power supply was not strong enough.

    Are you using a 3A power supply?

    thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 100 points

    Hi Cesar, 

    I apologize for the late reply. 

    This did the job for me. I suppose the evaluation board was sourcing more current than the power supply could handle. 

    Thank you for your help!