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.