Re: Character conflict in the remote-bitbnag protocol

2024-01-15 Thread Tommy Murphy 
How about:

Z - Sleep for 1 millisecond
z - Sleep for 1 microsecond

as in "Zz" for sleeping/snoring? :⁠-⁠)

https://www.grammarly.com/blog/zzz-meaning/

Re: Character conflict in the remote-bitbnag protocol

2024-01-14 Thread Antonio Borneo 
I don't think there is any preference.
You are the first to implement this remote delay, so any character
currently unused can do the job

Thanks
Antonio

On Sun, Jan 14, 2024 at 12:00 AM Jeremy Herbert  wrote:
>
> Hi all,
>
> No problems, happy to change to whatever you think is best.
>
> Thanks,
> Jeremy
>
> On Sun, 14 Jan 2024 at 4:58 am, Tommy Murphy  wrote:
>>
>> > Tommy, thanks for the alert.
>>
>> Just to clarify, it was Marek who flagged the issue.
>> I just linked to the documentation for the conflicting 'd' requests to give 
>> some additional context. :⁠-⁠)

Re: Character conflict in the remote-bitbnag protocol

2024-01-13 Thread Tommy Murphy 
> Tommy, thanks for the alert.

Just to clarify, it was Marek who flagged the issue.
I just linked to the documentation for the conflicting 'd' requests to give 
some additional context. :⁠-⁠)

Re: Character conflict in the remote-bitbnag protocol

2024-01-13 Thread Antonio Borneo 
Jeremy,
your patch to OpenOCD
https://review.openocd.org/c/openocd/+/7472
that introduced the remote delay for remote_bitbang driver uses the
'd' character that is already used for SWD.
Do you think it's possible to move the remote delay functionality to
another character?

Tommy,
thanks for the alert.

Regards,
Antonio

On Fri, Jan 12, 2024 at 10:26 AM Tommy Murphy  wrote:
>
> Just for context - the description of the two 'd' remote bitbang "packets":
>
> * SWD write 0 0: 
> https://github.com/openocd-org/openocd/blob/44e02e1f49cc09703cb3b4088d0c1c4f9e2d9c87/doc/manual/jtag/drivers/remote_bitbang.txt#L70
> * Sleep for 1 microsecond: 
> https://github.com/openocd-org/openocd/blob/44e02e1f49cc09703cb3b4088d0c1c4f9e2d9c87/doc/manual/jtag/drivers/remote_bitbang.txt#L81

Re: Character conflict in the remote-bitbnag protocol

2024-01-12 Thread Tommy Murphy 
Just for context - the description of the two 'd' remote bitbang "packets":

* SWD write 0 0: 
https://github.com/openocd-org/openocd/blob/44e02e1f49cc09703cb3b4088d0c1c4f9e2d9c87/doc/manual/jtag/drivers/remote_bitbang.txt#L70
* Sleep for 1 microsecond: 
https://github.com/openocd-org/openocd/blob/44e02e1f49cc09703cb3b4088d0c1c4f9e2d9c87/doc/manual/jtag/drivers/remote_bitbang.txt#L81

Character conflict in the remote-bitbnag protocol

2024-01-12 Thread Marek Vrbka 

Hello, I noticed that there is a conflict in the remote bitbang protocol.

Consider the commands "SWD write 0 0" and "Sleep for 1 microsecond". 
Both use the 'd' character. I am pretty sure this is an error, question 
is, what should we replace it with?


Marek Vrbka