I had a similar experience, though I was slowed down a little by fixing
some other small issues elsewhere in OpenOCD. Out of curiosity Armin, which
implementations did you use as an example?
On Thu, Mar 2, 2017 at 4:46 PM, Armin van der Togt <[email protected]>
wrote:
> I think it took me about three days. But I was completely unfamiliar with
> the openocd code, and I have not written the RTOS myself, so on both sides
> I had to do quite some digging to see how things are done.
> The code itself is pretty straight forward. There are about 5 functions
> that need to be implemented, and there are enough other implementations to
> take inspiration from. So... not too much work I would say, especially if
> you have written the RTOS yourself.
>
> Op do 2 mrt. 2017 23:21 schreef Freddie Chopin <[email protected]>:
>
>> Hello Armin!
>>
>> A small off-topic...
>>
>> I would like to ask you how long did it take you to add support for a
>> new RTOS to OpenOCD? I'm asking because I'm planning to add similar
>> support for my project - http://distortos.org/ (similar in some aspects
>> to what Liviu is doing) - and I was wondering how much work should I
>> anticipate.
>>
>> Thanks in advance!
>>
>> Regards,
>> FCh
>>
>
> ------------------------------------------------------------
> ------------------
> 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
>
>
------------------------------------------------------------------------------
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
