LC3 software codec profiling on nRF5340

[Chraebs]

Hi

I was wondering why there there seems to be no information about profiling of the LC3 codec by T2.

Only information I found is from Karl's answer here:

The rule of thumb is that the LC3 codec produces approximately ~15% CPU load when decoding and ~30% CPU load when encoding a 96 kbps stream, so you may indeed decode multiple incoming streams on your nRF5340 Audio DK.

From the nrfxlib documentation, there is only a link to the API documentation, but no further information regarding requirements (CPU, memory, other peripherals?).

Is there some more information available which can be considered when planning available resources for an application using Bluetooth LE Audio on nRF5340?

[ovrebekk]

Hi

When it comes to CPU performance the answer from Karl still stands, there haven't really been any changes there. 

We don't have accurate benchmarks for memory consumption, but when building in debug mode we see approximately 25% RAM consumption on the gateway side, and 21% RAM consumption on the headset side, in the application core. 

Flash consumption is about 52-54%. 

You could test this yourself by building the LE Audio sample. If you disable debug features such as logging you should be able to reduce the memory consumption a bit. 

Best regards
Torbjørn