• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 201 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AWRL1432: decompression configuration

EVA LIN
Prodigy 30 points
Part Number: AWRL1432

hi,

I use the demo project release-vmax-extension _ v1.00, and the process includes 1DFFT->compression-> decompression->2DFFT->channel accumulation. According to the mag value after the output of 2DFFT, there is obvious error data in the output result. By outputting the decompressed 1DFFT, it is found that the decompressed 1DFFT has a lot of error data.

According to the data, the DMA input  cCount = rangebin, the decompression of HWA is triggered by DMA, and rangebin cycles are executed. The data after decompression in the first few cycles is correct, but after several cycles, the input value of HWA seems to be tampered.

1DFFT decompression data is 16 bit complex,data as follows,

mag data is 32bit complex,data as follows,

I didn't make any changes to this demo project. The demo uses BFP compression. I changed it to EGE compression, which has the same problem. Please help me to see what may cause the problem.Thanks.

  • 0
    TI__Expert 3755 points

    Hello, what do you mean by "the input value of HWA seems to be tampered." Can you explain the problem a bit more?

  • 0 in reply to Zorah Ahmad
    Prodigy 30 points

    From the data point of view, the data input by EDMA to HWA compress module does not seem to be the original value.It looks like the decompressed result of one of the loops overwrites the data in the EDMA input to the HWA source address.If I do not use the decompression module, directly use uncompressed data to do 2DFFT, EDMA transmission will not be a problem.

  • 0 in reply to EVA LIN
    TI__Expert 3755 points

    Where are you putting the breakpoint? What memory are you looking at it? Can you break the process down for me?

  • 0 in reply to Zorah Ahmad
    TI__Expert 3755 points

    If you continue to run this for longer do you still see this? What made you think the compression data was wrong and look into it?

  • 0 in reply to Zorah Ahmad
    Prodigy 30 points

    I find out what the problem is, when my frame time is set short and I put a breakpoint between 1DFFT and 2DFFT, it causes a memory conflict between EDMA and HWA, and I run until the end of 2DFFT, there is no problem.

    breakpoint as follows,

    breakpoint between 1DFFT and 2DFFT

    mag memory(32bit complex):

    Some of this data is obviously not 32bit.But if I don't add breakpoints after the 1DFFT ends, there's nothing wrong with the data.

    Is it necessary to ensure that the frame period must not time out? If the frame period exceeds the design value, will it cause data transmission problems between EDMA and HWA？

  • +1 in reply to EVA LIN
    TI__Expert 3755 points

    Hi Eva, 

    I think I understand your problem. You put a break point in CCS, the code has stopped but the radar has not, it is still running in the background and updating the HWA and EDMA. To get a clearer picture put your numOfFrames =1 in your cfg or set your breakpoint in such a way that the next frame does not start. Anything outside of that will cause discrepancies