Sorry, I see that J. Neuschäfer has already done this. I will abandon my
patch - sorry, I am on holidays and my brain is not quite working so well ;)

Thanks,
Jeremy

On Sun, 31 Mar 2024 at 15:06, Jeremy Herbert <jeremy....@gmail.com> wrote:

> Also, there appears to be an unrelated issue with the docs around the
> remote bitbang protocol:
> https://review.openocd.org/gitweb?p=openocd.git;f=doc/manual/jtag/drivers/remote_bitbang.txt;hb=a35e254c5383008cdacf7838a777f7f17af5eeb1#l48
>
> It says "The eight mandatory functions are encoded in ASCII by assigning a
> single character to each possible request." and then proceeds to list a lot
> more than 8 commands. Are they all mandatory (is blink really mandatory)?
> At least the "eight" should probably be updated to whatever number is
> actually mandatory.
>
> Thanks,
> Jeremy
>
> On Sun, 31 Mar 2024 at 14:56, Jeremy Herbert <jeremy....@gmail.com> wrote:
>
>> Hi Tommy (and all),
>>
>> My apologies, this fell off my radar. I have just pushed a fix now:
>> https://review.openocd.org/c/openocd/+/8195
>>
>> Thanks,
>> Jeremy
>>
>> On Sat, 30 Mar 2024 at 22:27, Tommy Murphy <tommy_mur...@hotmail.com>
>> wrote:
>>
>>> Just to clarify - I can't see any relevant patch here that addresses the
>>> 'd' packet duplication/clash:
>>>
>>> * https://review.openocd.org/q/bitbang+sleep
>>>
>>> I can see the patch that introduced the problem though:
>>>
>>> * https://review.openocd.org/c/openocd/+/7472
>>>
>>


Reply via email to