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.

AWR2944EVM: Setting the number of ADC samples in chirp

Part Number: AWR2944EVM
Other Parts Discussed in Thread: AWR2944, , UNIFLASH, SYSCONFIG

Tool/software:

Hi,

I'm trying to run DDM configuration for SDK 4.4 aiming to increase to the maximal extent the number of ADC samples in a chirp. The reason behind that is a maximum processing gain for a long range application.

I took a profile "profile_3d_3Azim_1ElevTx_DDMA_awr2944_highRange.cfg" and changed the following CML lines:

profileCfg 0 77 7 7 20.81 0 0 8.883 0 384 30000 0 0 164
chirpCfg 0 5 0 0 0 0 0 15
frameCfg 0 5 128 0 384 50 1 0

to:

profileCfg 0 77 10 10 200 0 0 2.8 1 512 4200 0 0 30
chirpCfg 0 5 0 0 0 0 0 15
frameCfg 0 5 128 0 512 200 1 0

This application works - I tested it using a visualizer.

However, if I increase the number of ADC samples by any number - the configuration doesn't function.

The visualizer prompts that loading is fine in both cases (with Nadc=512 and Nadc=520) in the "Console Message" window, but the configuration with 520 ADC samples for example doesn't operate (I tried several numbers - the same effect).

According to "Interface Control" document (look at PF_NUM_ADC_SAMPLES), the limit for 4 RX is 2048 samples, so I'm by far from the limit.

What is wrong and what should be changed to achieve the limit of 2048?

  • Hello,

    Is there a specific reason you are using SDK 4.4? If not could you download the latest SDK and try the same thing. I will be able to help more from there.

    Best,

    Gabriel

  • Yes, 

    there is a reason: at the end of a day, we want to take OOB application from Radar toolbox, compile it by ourself and load a configuration. Based on e2e threads, only the following combination of SDK, Compiler and Radar toolbox is able to work properly:

    * ccs 12.8.1

    * mmwave SDK 04_04_01_02.   (only this one can work)

    * radar tools box version is 2_20_00_05

    And indeed we checked this, and found it correct.

    So, I have to shift to 4.4. from 4.7.

  • Anyway, I have tested now the issue with SDK 4.7 and had the same result.

  • Hello,

    the OOB application is not from the radar toolbox. The only thing coming from the RTB is the projectspec. All the demo makefiles and code are from the SDK, so I am a little confused when you mean the "OOB application from Radar toolbox." Regarding the ADCbuf issue, many times in the SDK it is coded that only specific values are allowed for certain parameters, this very likely could be one. I will invvestigate further on this

    Best,

    Gabriel

  • Hi,

    to make things simpler, let's focus on SDK 4.7. So, I loaded FW into AWR2944EVM using UniFlash 9.1.0 tool from:

    For SBL: 

    C:\ti\mmwave_mcuplus_sdk_04_07_00_01\mmwave_mcuplus_sdk_04_07_00_01\tools\awr294x\sbl_qspi.release.tiimage

    For Appimage: 

    C:\ti\mmwave_mcuplus_sdk_04_07_00_01\mmwave_mcuplus_sdk_04_07_00_01\ti\demo\awr294x\mmw\awr2944_mmw_demoDDM.appimage

    I use mmWave Demo Visualizer (4.7.0)

    The effect it the same.

    If there are specific constraints, please explain me what they are.

    For me, it is critical to keep the same sampling rate and the same chirp slope as currently in the configuration.

    Generally, I aim to limit the number of users in DDM to 1 (I focused on this point in another e2e thread), but overall, if for rising Nadc samples, it is required for some reason to decrease the number of chirp types in the frame from 6 to 1 (still keeping DDM mode) - this is also a goal.

  • Hello,

    I will attempt to run the same thing so please give me a few days to investigate said issue. In the meantime is there no error that is returned from this to the console or something like that? Please share if so.

    Best,

    Gabriel

  • No errors. I guess that the problem comes from the maximal cube size permitted in AWR2944 which is 2M. May I be right?

  • Hello,

    So, I tested with a projectspec on my end for the same demo and I was able to get it working with your config changes. I will share the steps I took.

    1) I used the following projectspec files to build the r5 and c66 cores

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/1023/1200.awr294x_5F00_mmw_5F00_demo_5F00_dssDDM.projectspec

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/1023/1200.awr294x_5F00_mmw_5F00_demo_5F00_mssDDM.projectspec

    2) These projectspec files need CCS 12.8.1, SDK 4.7.0.1, and sysconfig 1.22.0. It also specifies in said projectspecs. Import these projects to CCS and from there you can load the cores. 

    3) I also made the config changes you said. Here is the file so you can double check

    profile_3d_3Azim_1ElevTx_DDMA_awr2944_highRange - Copy.cfg

    4) I was then able to use the visualizer just fine by loading the above config.

    If this still does not work, could you share step by step on what you are doing? 

    Best,

    Gabriel

  • Thank you.

    Where from did you take the projectspecs? Please send me a link 

  • Hello,

    These are projectspecs I have personally ported to SDK 4.7.0.1, which are not currently in the radar toolbox. They will be available in the next toolbox release which is scheduled for next week. If no other questions let's close this thread please.

    Best,

    Gabriel