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.

AWR2544LOPEVM: mmwDemo range compressed Ethernet output with additional frame header

Part Number: AWR2544LOPEVM
Other Parts Discussed in Thread: AWR2544

Tool/software:

Hi,

I'm using the mmw Demo of AWR2544 to transfer compressed FFT data over Ethernet.

That's working great, but now I also have to transfer some additional parameters every frame. Unfortunately, the network protocol in the demo doesn't provide a header or footer on frame level.

What's the best way to do this?
I thought it would be clever to modify the network layer as little as possible since it seems to be highly optimized and time critical.

So I tried to transfer 1 additional chirp in the network layer "ti\demo\awr2544\mmw\mmw_tsn\default_flow_cpsw.c"

I'm iterating L3 memory two times. So in "EnetApp_configEdma" I increased:
syncABCfg1.cCount by numPayloads (numPayloads == 2 in my configuration), and
syncABCfg4.cCount by numPayloads.

I would expect that this generates additional CPSW triggers and DMA transfers for exactly 1 additional chirp.
But this modification seems to destroy the DMA configuration because now I don't get any output at all. Same result when I reduce the DMA config by one chirp in the same way.

Any idea what I do wrong? I don't see how the exact number of compressed chirp data is related to this network flow.

thanks
Stefan