On Thu, Mar 22, 2018 at 02:20:22PM +0300, Vlad Ivanov wrote:
> I was looking for a way to add a target to OpenOCD FreeRTOS support and
> noticed
> that targets are defined in code and any changes to stack layout and/or target
> list require recompilation. I think having a mechanism to maintain a list of
> targets and layouts in some other format would certainly be an improvement
> in the following cases:
>
> — when the target RTOS port is under development and undergoes
> changes over time;
> — when the target description can't be commited upstream because
> some ASIC isn't publicly available.
>
> Having a way to read that from a config file would be nice, and eventually
> other RTOS could use such mechanism too. Now, openocd uses TCL a lot and
> it seems that it would meak sense to read it from a TCL file too.
> I was thinking syntax like this:
>
> rtos add_target freertos [ dict create \
> { target_name } { AA2883XLPQ } \
> { thread_count_width } { 4 } \
> { pointer_width } { 4 } \
> ... \
> ]
>
> Thoughts?
I personally wonder why this wasn't done straight from the start... Now
all that's missing is patches.
--
Richard Braun
------------------------------------------------------------------------------
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
