• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 305 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.

MMWCAS-RF-EVM: StartFrame Timeout

Calvin Wagner
Prodigy 130 points
Part Number: MMWCAS-RF-EVM

I'm working through the portion of the cascade users guide and reached the part where I'm attempting to capture frames (7.3.3).

In the SensorConfig tab, after I click TDAxx ARM and step through the devices individually and click "Trigger Frame", the Framing Status never changes from "Not Framing".

There's a portion of the users guide that asks to set the 3 slave devices to Hardware Trigger and the Master device to a software trigger. I'm certain that is where I'm getting hung up. The manual doesn't really state as to whether or not this change needs to happen in the "Frame" container under the "SensorConfig" tab, or if it needs to happen under the "AdvFrameConfig" tab. I've tried both. Here is my output

[11:34:28] [RadarAPI]: ar1.AdvanceFrameConfig_mult(2, 1, 1536, 0, 0, 1, 128, 8000000, 0, 1, 1, 8000000, 0, 0, 1, 128, 8000000,0, 1, 1, 8000000, 0, 0, 1, 128, 8000000, 0, 1, 1, 8000000, 0, 0, 1,128, 8000000, 0, 1, 1, 8000000, 0, 2, 0, 1, 128, 0, 1, 128, 1, 1,128, 1, 1, 128, 1, 1)
[11:34:28] Status: Failed, Error Type: CHIRP USED IN THE FRAME IS NOT CONFIGURED BY AWR_CHIRP_CONF_SET_SB
[11:34:31] [RadarAPI]: ar1.DisableTestSource_mult(4,0)
[11:34:31] [RadarAPI]: Status: Passed
[11:34:31] [RadarAPI]: ar1.AdvanceFrameConfig_mult(4, 1, 1536, 0, 0, 1, 128, 8000000, 0, 1, 1, 8000000, 0, 0, 1, 128, 8000000,0, 1, 1, 8000000, 0, 0, 1, 128, 8000000, 0, 1, 1, 8000000, 0, 0, 1,128, 8000000, 0, 1, 1, 8000000, 0, 2, 0, 1, 128, 0, 1, 128, 1, 1,128, 1, 1, 128, 1, 1)
[11:34:31] Status: Failed, Error Type: CHIRP USED IN THE FRAME IS NOT CONFIGURED BY AWR_CHIRP_CONF_SET_SB
[11:34:33] [RadarAPI]: ar1.DisableTestSource_mult(8,0)
[11:34:33] [RadarAPI]: Status: Passed
[11:34:33] [RadarAPI]: ar1.AdvanceFrameConfig_mult(8, 1, 1536, 0, 0, 1, 128, 8000000, 0, 1, 1, 8000000, 0, 0, 1, 128, 8000000,0, 1, 1, 8000000, 0, 0, 1, 128, 8000000, 0, 1, 1, 8000000, 0, 0, 1,128, 8000000, 0, 1, 1, 8000000, 0, 2, 0, 1, 128, 0, 1, 128, 1, 1,128, 1, 1, 128, 1, 1)
[11:34:33] Status: Failed, Error Type: CHIRP USED IN THE FRAME IS NOT CONFIGURED BY AWR_CHIRP_CONF_SET_SB
[11:34:36] [RadarAPI]: ar1.DisableTestSource_mult(1,0)
[11:34:36] [RadarAPI]: Status: Passed
[11:34:36] [RadarAPI]: ar1.AdvanceFrameConfig_mult(1, 1, 1536, 0, 0, 1, 128, 8000000, 0, 1, 1, 8000000, 0, 0, 1, 128, 8000000,0, 1, 1, 8000000, 0, 0, 1, 128, 8000000, 0, 1, 1, 8000000, 0, 0, 1,128, 8000000, 0, 1, 1, 8000000, 0, 1, 0, 1, 128, 0, 1, 128, 1, 1,128, 1, 1, 128, 1, 1)
[11:34:36] Status: Failed, Error Type: CHIRP USED IN THE FRAME IS NOT CONFIGURED BY AWR_CHIRP_CONF_SET_SB
[11:34:55] [RadarAPI]: ar1.TDACaptureCard_StartRecord_mult(1, 0, 0, adc_data, 0)
[11:34:55] Device 0 - Configuring TDA with Width : 0 and Height : 0
[11:34:55] [RadarAPI]: Device 0 - setWidthAndHeight Status: Passed
[11:34:55] [RadarAPI]: Device 1 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[11:34:55] Device 1 - Configuring TDA with Width : 0 and Height : 0
[11:34:55] [RadarAPI]: Device 1 - setWidthAndHeight Status: Passed
[11:34:55] [RadarAPI]: Device 2 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[11:34:55] Device 2 - Configuring TDA with Width : 0 and Height : 0
[11:34:55] [RadarAPI]: Device 2 - setWidthAndHeight Status: Passed
[11:34:55] [RadarAPI]: Device 4 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[11:34:55] Device 3 - Configuring TDA with Width : 0 and Height : 0
[11:34:55] [RadarAPI]: Device 3 - setWidthAndHeight Status: Passed
[11:34:55] [RadarAPI]: Device 8 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[11:34:55] Sending Frame Periodicity of 0 to TDA..
[11:34:55] [RadarAPI]: Status: Passed. Frame Periodicity sent to TDA
[11:34:55] [RadarAPI]: Device 32 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[11:34:55] Sending Capture Directory with name /mnt/ssd/adc_data to TDA..
[11:34:55] [RadarAPI]: Status: Passed. Capture Directory sent to TDA
[11:34:55] [RadarAPI]: Device 32 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[11:34:55] Sending File Allocation of 0 files to TDA..
[11:34:55] [RadarAPI]: Status: Passed. File Allocation sent to TDA
[11:34:55] [RadarAPI]: Device 32 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[11:34:55] Sending Enable Data Packaging (0 - 16-bit; 1 - 12-bit) with value of 0 to TDA..
[11:34:55] [RadarAPI]: Status: Passed. Enable Data Packaging sent to TDA
[11:34:55] [RadarAPI]: Device 32 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[11:34:55] Sending Number of frames to capture with value of 0 to TDA..
[11:34:55] [RadarAPI]: Status: Passed. Number of frames to capture sent to TDA
[11:34:55] [RadarAPI]: Device 32 : CAPTURE_RESPONSE_ACK Async event recieved() with status 0
[11:34:55] [RadarAPI]: Status: Passed for notifying TDA about Creating Application
[11:35:05] Create Application Response from Capture Card timed out!!
[11:35:17] [RadarAPI]: ar1.StartFrame_mult(2)
[11:35:21] Status: Failed, Error Type: RESP TIMEOUT
[11:35:24] [RadarAPI]: ar1.StartFrame_mult(4)
[11:35:28] Status: Failed, Error Type: RESP TIMEOUT
[11:35:30] [RadarAPI]: ar1.StartFrame_mult(8)
[11:35:34] Status: Failed, Error Type: RESP TIMEOUT
[11:35:42] [RadarAPI]: ar1.StartFrame_mult(1)
[11:35:46] Status: Failed, Error Type: RESP TIMEOUT

  • 0
    TI__Mastermind 31680 points

    Hello Calvin,

    Thanks for reaching out. We would be happy to help you!

    From your output log, I see you've missed out on a couple of steps in between. 

    Please refer to the below message:

    Calvin Wagner said:
    [11:34:28] Status: Failed, Error Type: CHIRP USED IN THE FRAME IS NOT CONFIGURED BY AWR_CHIRP_CONF_SET_SB

    Let me clarify why you're getting this error.

    Either you're using Advance Frames or legacy frames, you need to configure the Profile and chirps in the "SensorConfig" Tab first. After that, if you want to use legacy frames (default frames), you can configure them in the "sensorConfig" tab or directly move to Advance Frame config for Advacnce frame configuration. You need not use Legacy frames (i.e. frame configuration on sensorconfig tab) in that case.

    Slaves can only be triggered in "Hardware mode" and master in "software mode", be it legacy frames or Advance frames.

    After the profile, chirp and frame configuration, you can then press TDA ARM button and trigger the frames for slaves first before doing it for master.

    I would request you try out the example scripts provided with the package. That has the correct sequence of operations that need to be followed. You can then take reference from those to program your own configuration.

    Furthermore, you can also refer to the mmWave DFP user guide.pdf (Chapter 11.1) to understand about programming the parameters in Advance Frame config.

    Regards,

    Ishita