• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 29 subscribers
  • Views 604 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.

AWR2243: AWR2243+AM2732 profile.cfg parameter configuration and frame interval time restriction

Kun Wang
Prodigy 120 points
Part Number: AWR2243
Other Parts Discussed in Thread: AM2732

Hello experts

Are there any specific restrictions on the parameter configuration and frame interval time of the current AWR2243+AM2732 Demo project? Downloading the default profile_2/3d_am273x.cfg configuration through Visualizer can  run normally and display the target.

When I change the profile parameter and frame interval time to the following  configuration, there have been some problems with the parameter download and operation on the Visualizer, as shown in the following figure:

% ***************************************************************
% Created for SDK ver:04.01
% Created using Visualizer ver:4.1.0.0
% Frequency:77
% Platform:AM273X
% CFG TYPE: 3D
% ***************************************************************
sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 7 0
adcCfg 2 1
adcbufCfg -1 0 1 1 1
lowPower 0 1
dataPathClkCfg 1 1
profileCfg 0 77 5 6 35 0 0 13.5 1 512 20000 0 0 30
dataPathConfig 0 1 0 2 64 64 64 0
hsiClockConfig 9 0
hsiLaneConfig 15 1 0 2 0 4 0 5 0 3 0 0
dataFormatConfig 1 1
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 4
chirpCfg 2 2 0 0 0 0 0 2
frameCfg 0 2 128 0 512 50 1 0
guiMonitor -1 1 1 0 0 0 1
cfarCfg -1 0 2 8 4 3 0 15 1
cfarCfg -1 1 0 4 2 3 1 15 1
multiObjBeamForming -1 0 0.5
calibDcRangeSig -1 0 -5 8 256
clutterRemoval -1 0
compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
measureRangeBiasAndRxChanPhase 0 1.5 0.2
aoaFovCfg -1 -90 90 -90 90
cfarFovCfg -1 0 0 8.92
cfarFovCfg -1 1 -1 1.00
extendedMaxVelocity -1 0
calibData 0 0 0
sensorStart

Then, I reduced the number of chirps and lengthened the frame interval. As follows, the parameter configuration can be downloaded normally. Although there is no obvious target information, it can run normally. Is the above parameter configuration data too large ?  Are there any restrictions here? How can we configure the parameters reasonably?

% ***************************************************************
% Created for SDK ver:04.01
% Created using Visualizer ver:4.1.0.0
% Frequency:77
% Platform:AM273X
% CFG TYPE: 3D
% ***************************************************************
sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 7 0
adcCfg 2 1
adcbufCfg -1 0 1 1 1
lowPower 0 1
dataPathClkCfg 1 1
profileCfg 0 77 5 6 35 0 0 13.5 1 512 20000 0 0 30
dataPathConfig 0 1 0 2 64 64 64 0
hsiClockConfig 9 0
hsiLaneConfig 15 1 0 2 0 4 0 5 0 3 0 0
dataFormatConfig 1 1
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 4
chirpCfg 2 2 0 0 0 0 0 2
frameCfg 0 2 32 0 512 500 1 0
guiMonitor -1 1 1 0 0 0 1
cfarCfg -1 0 2 8 4 3 0 15 1
cfarCfg -1 1 0 4 2 3 1 15 1
multiObjBeamForming -1 0 0.5
calibDcRangeSig -1 0 -5 8 256
clutterRemoval -1 0
compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
measureRangeBiasAndRxChanPhase 0 1.5 0.2
aoaFovCfg -1 -90 90 -90 90
cfarFovCfg -1 0 0 8.92
cfarFovCfg -1 1 -1 1.00
extendedMaxVelocity -1 0
calibData 0 0 0
sensorStart

In addition, when the number of ADC samples and the number of chirps are modified to less than 256*64, the profile parameters can be downloaded normally. Are there any restrictions on the parameter configuration in the demo project?

Is there anything I need to pay attention to when configuring the profile parameters?

Thanks.

  • 0
    Prodigy 120 points

    In addition, I modified different ADC samples * chirp numbers based on profile_3d_am273x.cfg, only if ADC samples * chirp numbers is less than 16384, that is 256*64 or 512*32,

    Visualizer can download profile_xx_.cfg parameter configuration normally, as follows, are there any restrictions on this in the Demo project, and what are the requirements for the  number of samples, chirp numbers and frame period?

    Thanks.

    1）ADC samples * chirp numbers(based on profile_3d_am273x.cfg):256*128 ——  abnormal

    2）ADC samples * chirp numbers(based on profile_3d_am273x.cfg):256*64 ——  seems ok

    3）ADC samples * chirp numbers(based on profile_3d_am273x.cfg):256*32 ——  seems ok

    4）ADC samples * chirp numbers(based on profile_3d_am273x.cfg):512*128 —— abnormal

    5）ADC samples * chirp numbers(based on profile_3d_am273x.cfg):512*64 —— abnormal

               

    6）ADC samples * chirp numbers(based on profile_3d_am273x.cfg):512*32 ——  seems ok

    7）ADC samples * chirp numbers(based on profile_3d_am273x.cfg):512*16 ——  seems ok

               

  • 0 in reply to Kun Wang
    TI__Guru*** 147994 points

    Hi,

    There are several levels of limitation that must be considered:

    1) There are limitations related to the configuration of the RF front end of the device. These limitations are INDEPENDENT of the demo. For example, there is a max for the paramter "number of ADC samples"

    Usually, an incorrect RF configuration is signaled as follows: There is no "Done" after startFrame. For example, in your tests 4) 5) the RF configuration is incorrect.

    These limitations are documented in the Radar Interface Control document provided in the DFP release

    C:\ti\mmwave_dfp_02_04_00_01\docs\mmWave-Radar-Interface-Control.pdf

    2) There are limitations related to the demo implementation. For example, this could be a limitation in demo available memory. It may happen that even if a RF configuration is correct, there is not sufficient memory to support it. In this case, the demo will issue an error message.

    Thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 120 points

    Hi 

    For 1) There are limitations related to the configuration of the RF front end of the device,

    I think the pure RF parameter configuration should be right. The theoretically ADC samples in the DFP file can reach 1024, Chirps can support 512, but I don't understand why there is no “Done” after some parameter configuration.

    I just modified ADC Samples and Chirps on the basis of Profile_3D_AM273X.CFG, and we have verified 512*128 on AWR2243+DCA1000, so I think the possibility of the second reason is greater.

    For 2) There are limitations related to the demo implementation

    I think there may be restrictions on DEMO software. From the parameter configuration as follows, it can be seen that this limit is not just limited to ADC samples*chirps, but it may also be related to frame cycle time, algorithm processing and data transmission.

    Due to  the unfamiliar with AWR2243+AM2732 Demo software, please help to see what restrictions are required for parameter configuration, memory allocation, data transmission, etc. in the software engineering, and how to reasonably configure allocation?

    （1）profileCfg 0 77 5 6 35 0 0 13.5 1 512 20000 0 0 30

              frameCfg 0 2 128 0 512 50 1 0

    （2）profileCfg 0 77 5 6 35 0 0 13.5 1 512 20000 0 0 30

             frameCfg 0 2 32 0 512 500 1 0

    Thanks.

  • 0 in reply to Kun Wang
    TI__Guru*** 147994 points

    Hi,

    Unfortunately there are several possible factors that make a configuration not correct for the demo. The combination of these factors is very high and it is not possible to document.

    Usually, based on experience, limiting factors are memory and processing speed.

    So, high number of ADC samples, high number of chirps will increase the memory required

    Low frame periodicity will also not work because at some point there will be not sufficient time to process the samples.

    I hope this helps

    thank you

    Cesar