PSRAM Usage

[caco3]

The Screenshots in this thread where made with the PSRAM Usage Visualizer.

The memory allocation are in detail shown in #2215 and #2200
The timely order of the allocation is visible here:

[caco3]

Colors:

• White: Unused
• Red: Alloc
• green: free
• light red: in use

[caco3]

v15.1.1

dig-cont_0611_s3.tflite (1.1 MB) and ana-cont_1105_s2_q.tflite (52 kB)

=> OK

psram_15.1.1.log

[caco3]

v15.0.1

dig-cont_0611_s3.tflite (1.1 MB) and ana-cont_1105_s2_q.tflite (52 kB)

=> OK

[caco3]

v15.1.0

dig-cont_0611_s3.tflite (1.1 MB) and ana-cont_1105_s2_q.tflite (52 kB)

=> OK but shows some fragmentation's:

[caco3]

v15.1.1

dig-cont_0611_s3.tflite (1.1 MB) and ana-cont_1105_s2_q.tflite (52 kB)

=> OK

[caco3]

Branch shared-psram-objects 3e752fd

dig-cont_0611_s3.tflite (1.1 MB) and ana-cont_1105_s2_q.tflite (52 kB)

=> malloc failed due to fragmentation:

I (24932) C IMG BASIS: Image (zwImage) loaded from memory: 0, 0, 0
E (24932) C IMG BASIS: Image with size 0 loaded --> reboot to be done! Check that your camera module is working and connected properly.

shared-psram-objects_3e752fde7.log

[Slider0007]

Would it work to move the task stacks in general to PSRAM? That would be static as well.

https://docs.espressif.com/projects/esp-idf/en/release-v3.1/api-reference/kconfig.html#envvar-CONFIG_SPIRAM_ALLOW_STACK_EXTERNAL_MEMORY

This is what we discussed already some weeks ago.I did some tests and failed because you have to be careful what functions you can call from PSRAM stack. Also for rev. 1 boards it's most likely not useable because of PSRAM bug...

[caco3]

malloc uses PSRAM for larger allocations than 16kB. There all? / most relevant of the STBI stuff is already in PSRAM.

You mean CONFIG_SPIRAM_MALLOC_ALWAYSINTERNAL, right?
But it then looks like as if it does not work correctly, because then we should not have that much small allocations in PSRAM, right? (Except what we put there by ourself, eg. MQTT outbox)

[Slider0007]

malloc uses PSRAM for larger allocations than 16kB. There all? / most relevant of the STBI stuff is already in PSRAM.

You mean CONFIG_SPIRAM_MALLOC_ALWAYSINTERNAL, right? But it then looks like as if it does not work correctly, because then we should not have that much small allocations in PSRAM, right? (Except what we put there by ourself, eg. MQTT outbox)

Yes. But I'm not aware which other rules for the malloc selection are exisitng. Maybe the libs are not included 100% in this setting. Whenver you switch off the wifi stack you do not have fragmentation. This means most of allocations seems to respect this setting but not wifi stack allocations. Otherwise you also would have fragmentation before experimenting with wifi stack.

[caco3]

I was not aware that it is mainly the wifi stack, but it does not surprise me.

Looking on https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/kconfig.html#config-esp-wifi-static-rx-buffer-num

It seems we can screw between static and dynamic buffers:

Maybe we should have a look there.

[Slider0007]

I also played already with these settings. but without any luck. Maybe you have more luck...

I was not aware that it is mainly the wifi stack, but it does not surprise me.

Looking on https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/kconfig.html#config-esp-wifi-static-rx-buffer-num

It seems we can screw between static and dynamic buffers:

Maybe we should have a look there.

I also played already with these settings, but without any luck. Maybe you have more luck.