dumb question from a hardware chip design guy. The error seems to be a very strange stack overflow problem, does the MePo code do any type of setjmp/longjmp actions to jump out on N-level deep function calls to some top level code to return to a high level routine and skip doing a bunch of normal returns? Any way the return/restart stack state gets messed up?
When I googled "Exception code: 0xe053534f", a lot of the web links said this type of stack fault is a messy problem to debug/fix.
When I googled "Exception code: 0xe053534f", a lot of the web links said this type of stack fault is a messy problem to debug/fix.