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.

MMWAVE-STUDIO: Infinite framing mode at MMWCAS-RF-EVM and MMWCAS-DSP-EVM

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

Hi TI-team,

I am planning to measure occupied bandwidth of the TX output of AWR2243 x 4 cascade board, "MMWCAS-RF-EVM and MMWCAS-DSP-EVM. 

I want to obtain continuous chirp signal to measure the FMCW spectrum in an analyzer.

My question is whether if we can get "infinite framing mode" from TX in the cascade configuration.

I don't need to capture any data in this case. 

According to the mmWave Studio GUI user manual, it seems that we can get infinite frames by 

- setting the number of frames, "0"

-  clicking "Trigger frame" to start continuous chirp signal and "Stop Frame" to stop chirp output

at the SensorConfig.

 I tried a couple of times, but the framing status couldn't continue.

Once I could get the framing (I don't know why), I couldn't stop framing. In this case the the DC current was increased by approx. 200-300 mA.

SPI connections were made by using Cascade_Configuration_TestSource.lua 

 This is an example GUI I got:

Your advice is greatly appreciated.

  • Hello User,

    Since you're not interested in capturing data, just skip the "TDA ARM" button on the SensorConfig tab in mmWave Studio. Pressing that button prepares/configures the TDA for data capture and since the SSD on TDA has a limited storage, it will limit the maximum amount of data that can be captured. Enabling infinite frames in that case would not work.

    Do your profile, chirp, frame configuration normally (with 0 frames configured) and then just press "Trigger Frames". You will have to follow the sequence there i.e. triggering frames for slaves first and then finally for the master. This will trigger the frames for infinite time for all 4 devices.

    Now when you want to stop the framing, you can do so either for all the devices together or for Master (in this case, you won't get frame stop async events for slaves and they will be in a "waiting for trigger" state. 

    I've tried out this sequence on my end and it works fine. Let me know in case you have any issues.

    Regards,

    Ishita

  • Dear Ishita,

    Sorry to take a time before the reply, and thank you very much for the explanation.

    Actually, by selecting the "software trigger", your explanation was becoming to make a sense clearly.

    Again, thank you.

    Regards,

    Masayuki Nakajima