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.

AWR1642BOOST: frame rate

Part Number: AWR1642BOOST
Other Parts Discussed in Thread: AWR1642

when I enable streaming of all data (range and Doppler heat-maps) the data UART can't seem to handle higher frame rates and I'm forced to reduce the frame rate to 1 or 2 FPS which is very low for my application.

I wanted to know if there is a way to increase the frame rate while keeping sama data streaming configuration?

I was thinking of maybe applying some form of data compression before streaming inside the AWR1642 firmware project so I can maybe get 10 FPS?

I'm also considering buying TI DCA1000 to capture data, but my concern is that I will endup with raw ADC captures, and will have to repeat the processing on the captured data, which is not trivial task I guess.

any recommendations?

Thanks,

Ahmed

  • Hi Ahmed,

    There is no way you can compress the data and send over UART.

    If you are buying DCA100EVM, there you can send user data (any type of debug info) over it and capture the data at the PC.

    And with the existing setup there is small tweak you can do to send more UART data with same frame periodicity.

    First you need to understand the code flow-

    1. FrameStart Interrupt

    2. ChirpAvailable interrupt-> 1-D FFT for all the chirps.

    3. if all the chirps are over then do the 2-D and other processing during idle frame period.

    4. at this point DSS app is ready with object data that needs to send to MSS (send over UART further), so calling MmwDemo_dssSendProcessOutputToMSS function.

    5. MSS reads that data from HSRAM, based on mailbox interrupt 'MmwDemo_mboxReadTask: case MMWDEMO_DSS2MSS_DETOBJ_READY:' and send over UART.

    6. after MSS send all the data over UART then it message DSS 'MMWDEMO_MSS2DSS_DETOBJ_SHIPPED'.

    7. At DSS after recieving 'MMWDEMO_MSS2DSS_DETOBJ_SHIPPED' message in 'MmwDemo_mboxReadTask' function, it decrements 'gMmwDssMCB.dataPathContext.interFrameProcToken' and set gMmwDssMCB.loggingBufferAvailable to '1'.

    NOW, if you comment 'gMmwDssMCB.dataPathContext.interFrameProcToken' from dss_main.c:MmwDemo_mboxReadTask function and put that derement under 'MmwDemo_dssDataPathOutputLogging' first thing 'gMmwDssMCB.dataPathContext.interFrameProcToken--;'

    So, now DSS won't go into ASSERT by 'MmwDemo_dssFrameStartIntHandler' function at next framestart interrupt (when interFrameProcToken!=0 by MSS DETOBJ_SHIPPED message). You have now full frame period worth of time to send whole UART object data.

    Caution: This workaround is just based on my code overlook, is not being tested. And in worst case you may miss few frame worth of object data over UART. Please proceed further and help yourself to do this workaround based on code understanding.

    Regards,

    Jitendra