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: Configuration problem with number of chirps

Part Number: AWR2243

We are using cascade imaging radar board with 4 AWR2243 chips on it. We have a problem with defining the number of chirps for some configurations.

In the pictures below you have our configuration parameters, mmwave studio ramp timing calculatorand also mmwave sensing estimator.

Our configuration doesn't work for more than 208 chirps which is really strange. If we drastically lower number of samples per chirp it sometimes successes but we can not figure out some timing and memory limitations. As I understood the documentation, it says that 2.4Gbits/s throughput is available per chirp of 4rx data (600Mbits/s per Lane meaning per RX) so I think our configuration is lower than 2.4Gbits/s. Also suggestions for adc_start_time, idle_time and ramp_end_not_sampled time are taken into consideration and chosen above limits defined like a precaution (idle 2.5 instead of 2, adc start time 3.84 more than 99% settling time, ramp_end_not_sampled 0.5 instead of 0.3 etc.).

So, can anyone explain why this configuration won't work? We are using 12V 5A for power supply. Could possibly frames with higher number of chirps need more current (I saw 8A max)?

Is there some memory limitation on number of chirps? Is there some problem with having number of samples NOT 2^n form? Could you check throughput of our configuration, we calculate it in a way that system works in ping/pong manner so time needed for transfer of one chirp data (4RX) is ramp_end_time + chirp_idle_time. Do we understand correctly throughput limitation?

A lot of smaller questions but simple one to summarize is why should this configuration with 210 chirps wouldn't work.

Regards, 

Predrag

  • Just to add, we tried this configuration with only ONE chip ON, but we have similar problem with all chips on.

  • Hi,

    Based on your description I think that you have reached some system limitations. It could be

    • memory limitation is defined by SSD size. this should be defined in the documentation
    • bandwidth limitation

    What is your bandwidth requirement?

    Thank you

    Cesar

  • Hi Cesar,

    1) We are sending only 8 frames of data 8 x ~2.7MB = ~21.6MB, so SSD size shouldn't be a problem I think (or am I wrong?)

    2) Regarding bandwidth limitation, if you mean on chirp bandwidth 0.43 GHz is far below 4GHz limit, if you think on throughput bandwidth limit of 2.4 Gbits/s, that is definitely ok also

    Is there any chance that size of whole data in a one frame needs to be divisible by some fixed size number of bits? Is there some limit of that kind on the transfer side to the SSD?

    Regards,

    Predrag

  • Any thoughts on this topic?

    Regards,

    Predrag

  • Hi,

    Sorry for the delay.

    We have seen issues when there are too many samples to be transmitted through CSI,

    In your configuration, there are 210 chirps, each chirp has 504 samples. It is possible that there is too much data to be transferred during the active frame time.

    Did you try to see if it works with N_adc=256 for example

    thank you

    Cesar

  • Hi Cesar,

    The same configuration with 212 chirps works correctly, so you think that there is nothing related to that the whole number of samples in a frame needs to be product of some fixed number?

    I can try to use 256 samples and it will work but that doesn't mean much to me, because if we rely on 2^n samples condition, we really narrow the number of possible configurations for desired system input parameters. And in this case the big portion of chirp would remain not sampled which means I need to change a lot other parameters to optimize configuration.

    Regards,

    Predrag

  • Hi,

    Sorry for the delay.

    In the first post it was mentioned that the configuration does not work for more than 208 chirps.

    In the last post it was mentioned that the configuration works for 212 chirps.

    So, is this summary correct:

    • works for 208 chirps
    • does not work for 210 chirps
    • works for 212 chirps

    Thank you

    Cesar

  • Hi,

    yes that is correct, we tried later to increase number of chirps and got working config. So yes, it works with 208 and 212 but it is not working with 210 chirps.

    Regards,

    Predrag

  • Thank you,

    If it works with 212 chirps, this is not related to the CSI bandwidth.

    I don't have an answer why this is not working.

    I will check with our extended team and will let you know if there is additional feedback

    thank you

    Cesar