ESP32-C2: Doesn't receive disconnect event after several connect / disconnect cycles

[bjoernQ]

I was hoping this could be fixed by having a timeout and disconnect from the peripheral side but that doesn't work since starting the advertising will return an error.

Maybe it's running out of some memory buffers but it seems unlikely since it reports lots of available buffers in that situation.
It's somewhat related to the amount of commands processed during a session (so it might be related to memory buffers?)

[MabezDev]

One thing maybe to check is the stack size variable in the linker scripts. Whilst debugging the S2 issue I found at some points in the program the stack depth exceeded the value set in the linker script. Bumping the number didn't fix the s2 issue sadly but we should probably increase them anyways as most are very small (s2 stack is 8K), with heavy inlining this can cause issues.

[bjoernQ]

There is definitely something quite wrong here. e.g. it used to depend on the opt-level if BLE worked or not and now that we changed the task-switching frequency even that doesn't work anymore - that definitely shows there is something wrong

This should get resolved before trying to support ESP32-C6 and later