ChibiOS Free Embedded RTOS

Hi,
why is it worse using an overloaded new-operator which acts on a ChibiOS memory pool with chPoolAllocI() than using chPoolAllocI() directly in an interrupt-context?

Hi Giovanni,
thanks for the hints.
Unfortenately, if i would use this variables for checking the states, my code would only be able to run with debugging enabled, am i right?

Another problem is, that new() and delete() do not support any parameters, so it is not possible to provide the necessary ...

Hello,
I'm curious if it is possible to query the rtos' state, espacially the states "S-Locked" "I-Locked" and "Serving Regular Interrupt" are of interest.
Background of the question is, that I'm implementing a memory-pool based memoryhandling by overloading the operators new() and delete() in C ...

Are there any updates concerning this project?

Hi,

The threads stacks in the demo are automatic variables of the main() function so they are allocated in the process stack.

Ah, ok, i thought so already. The formulation "When the C++ wrapper is used the stacks of the various threads are allocated within the stack of the main() thread" sounded ...

Hi,

When the C++ wrapper is used the stacks of the various threads are allocated within the stack of the main() thread, increasing the threads stack sizes actually make them overflow the main() function stack.

Try to increase the size of __process_stack_size__ in the linker script, it must be ...

Hi mabl With Option "USE_FPU = no" the threaded debugging works. Thanks for your help. Apparently I was a bit hasty with this statement. I get all the threads running in ChibiOS, but it is not possible for me to debug them correctly. Hitting a breakpoint does not open the corresponding thread but it ...

With Option "USE_FPU = no" the threaded debugging works. Thanks for your help.

I do not intentially use FPU. The only switch i see is DDEFS += -DCORTEX_USE_FPU=TRUE in Makefile. This evening i will try a build with DDEFS += -DCORTEX_USE_FPU=FALSE.

Hi mabl,
I'm seeing this error also with the official release of openocd.exe. This error seems to be related with stack trace inside an exception handler ( Link ) What are the gdb-startup commands you use?

EDIT:
Removing "jump ResetHandler" in "Run Commands" helped a bit. Now I can see the threads ...