On Thu, Mar 23, 2017 at 11:56 AM, Freddie Chopin <[email protected]>
wrote:
> Yes, that would be another issue with implementing such RTOS support.
> It gets pretty hard when you have to modify both the RTOS and OpenOCD,
> while _NOT_ being the developer of that RTOS.
>
> I forgot about that, as I have the "luxury" of being the developer of
> my own RTOS ( http://distortos.org/ ), so it's not a problem for me to
> add any support for such integration with OpenOCD and/or GDB.
> Especially because I see that as a thing of great importance!
>
Why do you need to modify your RTOS? If this is a case where you need
additional information at runtime, take a look under contrib at the RTOS
helpers for FreeRTOS and uC/OS-III. This should give you an idea of how you
can supplement the image under test with information you need for transient
information like struct offsets. You have unfettered access to memory, so
there's nothing holding you back or requires you to alter the RTOS source
code.
(FWIW, I'm the author of uC/OS-III RTOS support)
Steve
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
