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.

AWR2243: When using Advanced Framing and Advanced Chirp on mmWaveLink_Cascade_Example, the capture files are too small by 1-subframe of bytes

Part Number: AWR2243

The following question is related to:
C:\ti\mmwave_dfp_02_02_03_01\ti\example\mmWaveLink_Cascade_Example

When running an Advanced Chirp / Advanced Frame test, the captured data file(s) are smaller by the exactly the size of one subframe.
All 4 files (master_0000_data, slave1_0000_data, slave2, slave3) are exactly the same size and all are short 1 sub-frame bytes

parameter settings are:

IDLE TIME = 2uS,
RAMP_END_TIME = 23US,  
   (Chirp cycle time = 25us)

#TOTAL CHIRPS = 12
#BURSTS = 5
BURST PERIOD = (25us *12) + 110us + 25us extra

OUTER_LOOPS = 2
#SUBRAMES = 4
SUBFRFAME PERIOD = (#BURSTS * OUTER_LOOPS) * BURST_PERIOD + 345uS + 400us extra 

#FRAMES 1 to 20

If I run 1 FRAME, the capture files are the size of 3 Subframes (not 4), with one missing

If I run 20 FRAMEs, the capture files are the size of 79 Subframes (not 80), with one missing

I don't know which SF (first, last, other) was dropped from the capture files

Any ideas what could be causing this:?

Regards
Eddie