Maybe the debug info could be moved to a consistent location in the ROM class at this point as well? If the debug info being inlined or not is relevant (and so we don't want ROM classes that differ only in this respect to be equivalent to each other) then we either have to ...
I have an error that a symbol (e.g. bool or uint32_t) could not be resolved. What’s going on and what do I do about it? The odds are this is a false positive. Other symbols defined in the file are fine, but one shows up as an error. The code builds despite this error. T...
We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly Cancel Create saved search Sign in Sign up Reseting focus...
If any interrupt is a wake-up source, than this could be a timer interrupt or the the tick interrupt which is used as tick timer for the RTOS. On ARM cores the SysTick timer is typically used as the RTOS tick timer, but on other architectures any periodic interrupt timer can be used....
// \$t_{current} > t_{id} + ttl\$ // // MUST be set to a value > 0. uint32 ttl = 2; // The service consumer's access token as defined in // https://github.com/eclipse-uprotocol/up-spec/blob/main/basics/permissions.adoc[Permissions]. optional string token = 3; } // ...
This is a global variable COREDUMP_DRAM_ATTR uint8_t global_var; Now add these two lines just above the esp_restart() function global_var = 25; assert(0); The final file should be something like this: Build and flash the project and launch the serial monitor. On line number 45, we...
/* test class */ #include <esp_system.h> #ifndef CLASS_TestClass_H_ #define CLASS_TestClass_H_ class TestClass { private: TestClass(); uint8_t GPIO; public: TestClass(uint8_t pin); void testMethod(); }; #endif /* test class */ #include <freertos/FreeRTOS.h> #include <dr...
That might not be totally necessary. I'll have to double-check if a shared ROM class can ever have a mix of inline and out-of-line debug info, but even then we could skip stripping the debug info in that case and and worst suffer a cache miss as a result. If that sounds all ...
I'd have to look at the client-server messages in more detail to see what would be needed. I think the main things to deal with are: SCC offsets in AOT relocation metadata on the server side, which could be substituted with AOT cache IDs. This will also allow us to eventually get ...
* 11f5ed0007 - fix: web UI bug where invalid component could not be deleted. (#4310) (G_Ivo) * 1c3e365cef - build: Updated tycho version from 3.0.0 to 3.0.1 (#4307) (Salvatore Coppola) * d2176dd301 - chore(target-platform/libsocket-can-osgi): added gitignore for lib artifacts...