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.

MMWCAS-RF-EVM: mmWaveLink_Cascade_Example mmWave Device Power on failed error

Part Number: MMWCAS-RF-EVM
Other Parts Discussed in Thread: AWR2243, MMWAVE-STUDIO, MMWAVE-DFP, , MMWCAS-DSP-EVM

Hello everyone
I recently used MMWCAS-RF-EVM and MMWCAS-DSP-EVM to implement automated radar measurements. In order to shorten the time of acquiring data each time, I used the AWR2243_spi_to_flash tool to write the xwr22xx_metaImage.bin file into the flash on the radar chip. Next, I need to complete data acquisition work without using MMWAVE-STUDIO and lua scripts. When using MMWAVE-STUDIO to collect data, everything is displayed correctly, but when I use mmWaveLink_Cascade_Example in the MMWAVE-DFP package to obtain data, there are some problems, which causes the data acquisition to fail. According to the printed information, the problem occurred during the power on process of the millimeter wave device. According to the source code, failure to receive an asynchronous message from the radar device within the specified time will cause this error, as shown in the following figure:

[15:42:11:948]: # INFO: Network: Connecting to the server 192.168.33.180:5001 ...
[15:42:12:040]: # NETWORK: Connected to Server (192.168.33.180:5001)!!!
[15:42:12:041]: [GN]0xC8 0xA5 0x12 0x00 0x00 0x00 0x0C 0x00 0x20 0x10 0x00 0x00 0x00 0x00 0xA6 0x95
[15:42:12:041]: # INFO: Sending trace file name : Trace_TDA_[14_10_2020_15.42].txt , Length : 32
[15:42:12:041]: [GN]0xC8 0xA5 0x16 0x00 0x00 0x00 0x2C 0x00 0x20 0x01 0x00 0x00 0x00 0x00 0x54 0x72 0x61 0x63 0x65 0x5F 0x54 0x44 0x41 0x5F 0x5B 0x31 0x34 0x5F 0x31 0x30 0x5F 0x32 0x30 0x32 0x30 0x5F 0x31 0x35 0x2E 0x34 0x32 0x5D 0x2E 0x74 0x78 0x74 0x26 0xA9
[15:42:12:043]: [GN]0xC8 0xA5 0x13 0x00 0x00 0x00 0x0C 0x00 0x20 0x01 0x00 0x00 0x00 0x00 0xD8 0x38
[15:42:12:044]: # INFO: Received CAPTURE_RESPONSE_VERSION_INFO command with TDA Binary Version : REL_VISION_SDK_03_07_01_00 Aug 5 2019 15:04:45
[15:42:12:045]: # INFO: Sending Device Map of 15
[15:42:12:045]: [GN]0xC8 0xA5 0x1A 0x00 0x00 0x00 0x14 0x00 0x20 0x10 0x00 0x00 0x00 0x00 0x01 0x01 0x01 0x01 0x04 0x00 0x00 0x00 0x25 0xB9
[15:42:12:095]: [GN]0xC8 0xA5 0x10 0x00 0x00 0x00 0x0C 0x00 0x01 0x01 0x00 0x00 0x00 0x00 0xEF 0x4D
[15:42:13:700]: Device [0] [GN]0xC8 0xA5 0x21 0x00 0x00 0x00 0x10 0x00 0x01 0x01 0x00 0x00 0x00 0x00 0x04 0x00 0x00 0x00 0xFD 0xFD
[15:42:13:700]: Device [0] [GN]0xC8 0xA5 0x20 0x00 0x00 0x00 0x0C 0x00 0x01 0x01 0x00 0x00 0x00 0x00 0x1F 0x14
[15:42:15:705]: Device [0] [WR]0xA5C8 0x0023 0x0000 0x002C 0x1001 0x0000 0x0000 0x1234 0x4321 0x8305 0x001C 0x0400 0x0000 0x0001 0x78DD 0x4180 0x000C 0xFF0C 0xFFFF 0x00AD 0x0000 0x195C 0xF7F6 0xBDC9
[15:42:16:705]: Device [0] [WR]0xA5C8 0x0023 0x0000 0x002C 0x1001 0x0000 0x0000 0x1234 0x4321 0x8305 0x001C 0x0403 0x0000 0x0001 0x78DA 0x4180 0x000C 0xFF0C 0xFFFF 0x00AD 0x0000 0xFE56 0x3D92 0xE6FB
[15:42:17:705]: Device [0] [WR]0xA5C8 0x0023 0x0000 0x002C 0x1001 0x0000 0x0000 0x1234 0x4321 0x8305 0x001C 0x0403 0x0000 0x0001 0x78DA 0x4180 0x000C 0xFF0C 0xFFFF 0x00AD 0x0000 0xFE56 0x3D92 0xE6FB
[15:42:18:705]: Device [0] [WR]0xA5C8 0x0023 0x0000 0x002C 0x1001 0x0000 0x0000 0x1234 0x4321 0x8305 0x001C 0x0403 0x0000 0x0001 0x78DA 0x4180 0x000C 0xFF0C 0xFFFF 0x00AD 0x0000 0xFE56 0x3D92 0xE6FB
[15:42:19:705]: Device [0] [WR]0xA5C8 0x0023 0x0000 0x002C 0x1001 0x0000 0x0000 0x1234 0x4321 0x8305 0x001C 0x0400 0x0000 0x0001 0x78DD 0x4180 0x000C 0xFF20 0xFFFF 0xAD00 0x00AD 0xA30A 0x2C27 0xA26A
[15:42:20:706]: Device [0] [WR]0xA5C8 0x0023 0x0000 0x002C 0x1001 0x0000 0x0000 0x1234 0x4321 0x8305 0x001C 0x0403 0x0000 0x0001 0x78DA 0x4180 0x000C 0xFF20 0xFFFF 0xAD00 0x00AD 0x4400 0xE643 0xF958
[15:42:21:707]: Device [0] [WR]0xA5C8 0x0023 0x0000 0x002C 0x1001 0x0000 0x0000 0x1234 0x4321 0x8305 0x001C 0x0403 0x0000 0x0001 0x78DA 0x4180 0x000C 0xFF20 0xFFFF 0xAD00 0x00AD 0x4400 0xE643 0xF958
[15:42:22:707]: Device [0] [WR]0xA5C8 0x0023 0x0000 0x002C 0x1001 0x0000 0x0000 0x1234 0x4321 0x8305 0x001C 0x0403 0x0000 0x0001 0x78DA 0x4180 0x000C 0xFF20 0xFFFF 0xAD00 0x00AD 0x4400 0xE643 0xF958
[15:42:23:707]: Device [0] [WR]0xA5C8 0x0023 0x0000 0x002C 0x1001 0x0000 0x0000 0x1234 0x4321 0x8305 0x001C 0x040C 0x0000 0x0001 0x78D1 0x4180 0x000C 0xFF04 0xFFFF 0x00AD 0x0000 0xAE2F 0xDDD0 0x5832
[15:42:25:937]: # ERROR: Invalid Callback from mmWaveLink
[15:42:25:937]: Device [1] [GN]0xC8 0xA5 0x21 0x00 0x00 0x00 0x10 0x00 0x02 0x01 0x00 0x00 0x00 0x00 0x04 0x00 0x00 0x00 0x32 0x4C
[15:42:25:940]: Device [1] [GN]0xC8 0xA5 0x20 0x00 0x00 0x00 0x0C 0x00 0x02 0x01 0x00 0x00 0x00 0x00 0xFF 0xDA
[15:42:25:946]: Device [2] [GN]0xC8 0xA5 0x21 0x00 0x00 0x00 0x10 0x00 0x04 0x01 0x00 0x00 0x00 0x00 0x04 0x00 0x00 0x00 0x8D 0x3F
[15:42:25:948]: Device [2] [GN]0xC8 0xA5 0x20 0x00 0x00 0x00 0x0C 0x00 0x04 0x01 0x00 0x00 0x00 0x00 0x1E 0x57
[15:42:25:952]: Device [3] [GN]0xC8 0xA5 0x21 0x00 0x00 0x00 0x10 0x00 0x08 0x01 0x00 0x00 0x00 0x00 0x04 0x00 0x00 0x00 0xF3 0xD8
[15:42:25:954]: Device [3] [GN]0xC8 0xA5 0x20 0x00 0x00 0x00 0x0C 0x00 0x08 0x01 0x00 0x00 0x00 0x00 0xFD 0x5C
[15:42:25:989]: [GN]0xC8 0xA5 0x14 0x00 0x00 0x00 0x14 0x00 0x01 0x01 0x00 0x00 0x00 0x00 0x00 0x08 0x00 0x00 0x0C 0x00 0x00 0x00 0x62 0x0A
[15:42:25:990]: [GN]0xC8 0xA5 0x14 0x00 0x00 0x00 0x14 0x00 0x02 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x5E 0x5B
[15:42:25:991]: [GN]0xC8 0xA5 0x14 0x00 0x00 0x00 0x14 0x00 0x04 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x39 0x50
[15:42:25:992]: [GN]0xC8 0xA5 0x14 0x00 0x00 0x00 0x14 0x00 0x08 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xF7 0x46
[15:42:25:993]: [GN]0xC8 0xA5 0x35 0x00 0x00 0x00 0x10 0x00 0x20 0x10 0x00 0x00 0x00 0x00 0x4B 0x00 0x00 0x00 0xC2 0x0A
[15:42:33:452]: [GN]0xC8 0xA5 0x11 0x00 0x00 0x00 0x0C 0x00 0x01 0x10 0x00 0x00 0x00 0x00 0x91 0xE0
[15:42:33:452]: [GN]0xC8 0xA5 0x17 0x00 0x00 0x00 0x0C 0x00 0x20 0x01 0x00 0x00 0x00 0x00 0x0C 0x35
[15:42:34:452]: # INFO: Rx thread about to die

The strange thing is that this kind of problem does not occur every time the device is turned on. The occurrence of this problem is somewhat random. The output under normal conditions is shown in the figure below:

The AWR2243 I currently use is ES1.0 version, mmwave_dfp is version 02_02_00_03, and mmwave_studio is version 03_00_00_07. I want to know what conditions may cause this error and why this has never happened with mmwave_studio. I need to avoid this error as much as possible.

  • Hello,

    For the next iteration of the application run, you need to power cycle the board to avoid any kind of error.

    Did you power cycle the board for the above repeated experiment?

    Regards,

    Jitendra

  • Hello there
    After many comparative tests, I believe that the occurrence of the device Power on failed error is indeed random, and the power is cut off and restarted between each test. If I use the MMWAVE-STUDIO tool, everything is normal. It can normally receive asynchronous messages from the device and can run stably for a period of time. In addition, during the test, Master Device Power on success but Slave Device Power on failed, as shown in the following figure:

  • Hello,

    Are you trying to run using default example exe or compiling from Visual Studio?

    Make sure that you re-build in release mode in the Visual Studio.

    This application is provided as a reference to showcase that from PC you can control the cascade but still recommendation is to use mmwave studio for cascade-related test.

    Regards,

    Jitendra

  • Hello,

    My previous experiment has compiled the source code with Visual Studio and released mmwavelink_example.exe. Because I store firmware in the flash on chip, I need to modify some source code accordingly to ensure the stability of program. I will do this work in the next time. Please close this query, thanks.