Thanks. I'm good now. I removed all the stub files and implemented a variant of delete but I now have an active object responding to events published by another task (after your asserts pointed out a couple of errors I made with public signals and initializing the event pools). I really like the framework. Used it very extensively on a biotech project a few years ago. Looking forward to using it again.
Thanks. I'm using my startup code which I spent some time cleaning/organizing but I'm open to modifying it. I removed mini_cpp.cpp but left no_sbrk.cpp, no_sys.cpp, and no_heap.cpp. I removed -nostdlib but left -no-rtti and -no-exceptions. I don't use the heap nor do I do any static allocation--I use a "root" object and placement new to acheive compile time allocation but control when the object is instantiated. Now I'm getting the errors about operator delete. Is this error related to ~QHsm() being...
Hi, I'm running in to the linker errors associated with mini_cpp.cpp. I'm using Segger Embedded Studio which is using GCC (with so-called managed linker scripts) and I've tried a couple of things resolve the issue to no avail. For example I selected the option to not link against the standard libraries but then sprintf is missing. At the moment, I'd rather make progress towards my deadline than worry about the extra flash used. Can you tell me what I need to have this link against the standard libraries?...
Hi Jay, I have the same question. Have you learned anything since you posted? Ke...
This is a duplicate. I forgot to add a subject to my email. Hi Everyone, I am working...
Hi Everyone, I am working on a new C++ design for an embedded system. It uses an...
Thanks Miro, How is this variable used if the RTOS is performing the scheduling?...
When using an underlying RTOS what is the purpose of m_prio? It seems that the priority...